# Review 2 meeting 18/03 - Elevator pitch (3 min) - Demo (10 min) - Sprint update (5 min) - Test planning update (5 min) - CI/CD update (4 min) - Risk & decision list update (3 min) ## Feedback - Gamification - Which gamification elements are planned and we want to implement - MC, Tinder-of-objects, Click part of object, AR model that slowly build up and guess what object it is. - We use a score system. - GUM: Possibility to turn scores off - Possibility, Completing tour to receive label or something else - ... to engage and encourage the users. - Scalability of the platform/ responsiveness - Do we provide a scalable solution? Do we have this into mind? - We are develloping with scalability into mind, because that was our ADD - Planning later to deploy heavy workload containers in Kubernetes - Do we have an idea of how many users can support - WE NEED TO HAVE AN IDEA OF HOW MANY USERS WE CAN SUPPORT - This will be tested next sprint. - Show this next Demo - Do we have a guideance for the editors. Use of templates and share - We more focus on reusing assets in an organisation. - Is it possible to add this to the scope. - IT is something we can think about and can be of big value - We also currently have a usermanual for the editor - Maybe not implement it completly, but make the backend so it could easily be implemented if we have enought time. - Steps in a POI, Do you always see a 3D model - 3D model, make them see the object - Task, make have interest in the object, and wanting to know more - Description - What do we meant with minigame. - We mostly see it as task. - Reflect on Acceptance test - Were okay, some remarks are left - Non-functional requirements are not really clear. See also what we put down in the deliverable. - It should not be to much work.