2021-04-12 Review of 1st Iteration » Historie » Verze 2
Roman Kalivoda, 2021-04-14 06:17
Add list of people who attended
| 1 | 1 | Roman Kalivoda | h1. 2021-04-12 Review of 1st Iteration |
|---|---|---|---|
| 2 | |||
| 3 | 2 | Roman Kalivoda | h3. Attendees |
| 4 | |||
| 5 | * @ppicha |
||
| 6 | * @kacerekz |
||
| 7 | * @akonig |
||
| 8 | * @emouryc |
||
| 9 | * @kali |
||
| 10 | |||
| 11 | 1 | Roman Kalivoda | h3. Notes |
| 12 | |||
| 13 | * detailed business case |
||
| 14 | * make functional requirements more visible - do we want a dedicated req specification page or just tickets linked to the vision statement |
||
| 15 | * Project plan should be separated from the vision statement |
||
| 16 | * Describe stakeholders in more detail |
||
| 17 | * define a system for monitoring and time estimation improvement (timebox meetings to concentrate on important topics, add fixed time reserve for tasks) |
||
| 18 | * set conventions for Redmine trackers, git branching commit naming, team roles |
||
| 19 | * plan meetings to iterations where they happen |
||
| 20 | |||
| 21 | h3. Highlights |
||
| 22 | |||
| 23 | * link commits to tickets |
||
| 24 | * define specification |
||
| 25 | * define architecture (and runnable demo ideally) |
||
| 26 | * create a project plan |