---
# System prepended metadata

title: Planning meeting 18/02

---

# Planning meeting 18/02

Planning can be found on : https://hackmd.io/mPqSEof2SMKq_J0ZYuGU-A

Eerste sprint: 
- Epic - Skeleton Architecture
- Epic - Basic Tour Editor
- Epic - Basic Tour App

Feedback: 
- First spring mostly already done, except the parts that are needed in late epics
    - Is testing also already done?
        - test plan is seperatly made, but in the following sprint(s) will be implemented
        - Because we didn't know how we needed to test, we started develloping
        - in later sprints, we would first devellop the test, then the application
    - Test are mostly done by hand, everyone should be able to work on something. Next sprint all test should be implemented. **No test may be forgotten, especially between components**
    - In jenkins the pipeline is mostly implemented, with the ability for tests

Epics for following sprints:

More general/important epics, proof of concept epics
- Epic - Metrics
- Epic - Gamification I
- Epic - Custom 3D Models

More quality improvement epics, specifically working the product out to detail
- Epic - Advanced Tour Views I
- Epic - Gamification II
- Epic - Multiplayer I
- Epic - Quality Of Life I

Feedback:
- Good work devision of epics
- But need to really make a planning per week
    - What need to be finished for that week, milestones, demo's
    - Always be able to explain how everything works, and why.
    - Milestones, Depencendencies, finish dates
    - Someone from outside should be able to see who does what when, where help should be needed, why things are delayed

Test plan:
***Now the test should be implemented, this has high priority***

Risk and Mitigation:

Risk analysis should also have a "likelihood" and "impact" (high, medium, low)
Normally one should make a design on paper and go with this to the customer to ask if it is good.
**New Risk: We make a app where usability is important, but nobody has experience of design of usability. We need some to gain knowledge on that, or reach out someone who can help with it.**

Risk analysis of AR: It is a good one, because it is a core technology. Every team member should have some knowledge about AR topic.

**AR scene cant be test on a coumputer ==> problem every year, ask assistents**

How likely is it that a musea would leave our project? Both museas dont have 3D models. One musea has a good technical empoyee that can help. One musea works together with gent to digitize with musea pieces
The question is if that we get the models in time we want to have them

Another possible problem is the extentions of the 3d models. This should already be implemented (or a stub).

Only one of us has a IOS, so most focus on android. Are we gonna pilot on android with possibility for IOS, or is this not a core feature of the project. Sometimes it can be better to reduce the scope of the project.

Look for the cost of the official test account of MAP-API, to be sure no problems arise. If it would not be to expensive, this should be possible.

System wide quality attribute Scalibility: 
It should be possible to test this throughout the devellopment, not only focus on this near the end on the semester. Test each module that it can have a high enough performance. This should be test from day one, otherwise problem arise late, and cant be fixed in time.