Conduct sprints
Purpose
Conducting a sprint leads to an agreed, concrete and verifiable outcome.
Basic idea
A sprint includes all planning, realization and coordination activities over a fixed period of time. They are formally defined in SCRUM as events and include Sprint Planning, Daily SCRUM, Sprint Review and Sprint Retrospective.
The planned outcome of a sprint is documented in the sprint backlog.
At the end of a sprint, there is an increment that has the attribute of an executable product, regardless of whether or not it is delivered to the user as a release.
HERMES-specific
The sprints are planned as a whole in the release plan.
The project management assigns responsibility for the execution of a sprint to the SCRUM team. The SCRUM team organizes itself and adheres to the defined agreements of the agile working methods documented in the project management plan.
Activities
-
Plan sprint and document in the sprint backlog
-
Develop increment and conduct Daily SCRUM
-
Conduct Sprint Review: prepare and give a presentation of the increment and test it according to the test concept
-
Conduct a Sprint Retrospective and document lessons learned in a minutes
Relationships
Module | Task | Task responsibility | Outcome | Involved in creation of outcome |
---|---|---|---|---|
Agile development | Conduct sprints | Developer | Sprint backlog | Business analyst |
Conduct sprints | Developer | Increment | ||
Conduct sprints | Developer | Minutes | Project manager |