# Review 4/03

**Voor volgende review, zeker testplan en CI/CD uitleggen!!!**

First remark, lots of things to say, keep track of time managment so we dont go over time. Try to limit things to say. 50 slides for 30 minutes is to much

- Why is Maxime project manager and scrum manager?
- In first gidelines, it was in one role.
- Why does it not work with internet explorer
- Inside joke in web devellopment. Some features dont work in internet explorer.
- Why not interaction between users, why start later or discard multiplayer.
- This limits the posiblity for the application. Is this also a choice that the museums agree with.
- For devellopment, starting with signleplayer is easy, multiplayer is more difficult. Hence we start with singleplayer.
- This should be asked at the musums. We need a good motivation.
- Is there a way during devellopment that some things are extendable for the multiplayer.
- Multiplayer stub has functionality to receive information of players. The hard part is the devellopment of cooperative games/tasks
- QoL is a weird term to use. Quality of Results is better.
- What can users exactly do during the tour??
- Can users comment on the tour?
- Can they see others?
- During the pitch, we need to say something about what the users can do.
- Risk that are certain, that is a given/happening, not really a risk. It is more a decession.
- No external testers ...
- A bit contradictory with planning, because we will start testing late.
- We changed our test planning, so it is a mistake. Manual planning will be taken into account.
- We see museams more as partners, but we also need end-users.
- We want input/feedback from the musea before we would give our prototype/mvp to end-users
- 3D models risk
- 10 april: aimed date to receive 3d models. This is plan A
- Maybe the order is in reserve.
- Release feedback;
- Everything was fine
- User testing! validating features.
- He wants us to start user testing more early then we planned. Ask end users on the features, what features we need to focus more on
- IDEA: makes questionair with features and ask end-users to select the most important ones.
- Let friends and family test the apps and ask for feedback.
- The earlier to get feedback, the easier to implement it.
- We dont need to implement the authentication to get feedback.
- Our app need to be fun. We need to ask users what they want.
- Maybe ask museas if they can ask users to test the prototype to get feedback.

## Extra:

User manual/ develloper manual, testing document should be living document.
Those can be constructed from release notes.

User manual + apk => unfamiliar users should be able to use our app without any problems, without things to be unclear.