Agile elements¶

We don't implement the full scrum cycle, but use following elements:

• New requirements are written down as User Stories.

• Each feature of the User Story is a subtask.
• If possible, a subtask holds a list of acceptance criteria.

• User Stories are prioritized by Kurt Gerber (this should be done by the project management).

• A sprint cycle lasts two weeks (11 days), from Monday to Thursday.

• The standup (ca. 15 minutes) takes place on Tuesday and Thursday, 9.15.
• A sprint starts with the sprint planning, where the developers assign themselves user stories.

• Todo: Set date!

• The sprint ends with a sprint review meeting where the implemented user stories are presented by the developers.

• Date: Thursday, after lunch.

• After the sprint review a short retro is held, where the process is discussed.

• Developers update the status of their tickets on the agile board; the latest state is always deployed to qcat-dev.

• Also see: Responsibilities

• To be defined:

• Who creates new user stories / subtasks?
• When are they created? Who is responsible for the estimates.