Agile elements » History » Version 3
Sebastian Manger, 09 Feb 2016 12:47
| 1 | 1 | Sebastian Manger | h1. Agile elements |
|---|---|---|---|
| 2 | 2 | Sebastian Manger | |
| 3 | We don't implement the full scrum cycle, but use following elements: |
||
| 4 | |||
| 5 | * New requirements are written down as User Stories. |
||
| 6 | 3 | Sebastian Manger | > * Each feature of the User Story is a subtask. |
| 7 | > * If possible, a subtask holds a list of acceptance criteria. |
||
| 8 | 2 | Sebastian Manger | |
| 9 | * User Stories are prioritized by Kurt Gerber (this should be done by the project management). |
||
| 10 | |||
| 11 | * A sprint cycle lasts two weeks (11 days), from Monday to Thursday. |
||
| 12 | > * The standup (ca. 15 minutes) takes place on Tuesday and Thursday, 9.15. |
||
| 13 | > * A sprint starts with the sprint planning, where the developers assign themselves user stories. |
||
| 14 | > > * Todo: Set date! |
||
| 15 | > * The sprint ends with a sprint review meeting where the implemented user stories are presented by the developers. |
||
| 16 | > > * Date: Thursday, after lunch. |
||
| 17 | > * After the sprint review a short retro is held, where the process is discussed. |
||
| 18 | |||
| 19 | * Developers update the status of their tickets on the agile board; the latest state is always deployed to qcat-dev. |
||
| 20 | > * Also see: [[Responsibilities]] |
||
| 21 | |||
| 22 | * To be defined: |
||
| 23 | > * Who creates new user stories / subtasks? |
||
| 24 | > * When are they created? Who is responsible for the estimates. |