Skip to content

Sprint management

hamstar edited this page Nov 6, 2012 · 4 revisions

Pre-Sprint Meeting

Milestones

A new milestone should be made for each sprint with the name of the sprint (e.g. Sprint 1) and work should be added to it as per the pre sprint meeting.

Issues

Deliverables

For each sprint we should identify the deliverables that are required from it. Once we have identified the deliverables then we create a set of issues for the deliverables and label them with the deliverable label. Use cases and other issues then refer to the deliverable with a comment "Delivered by #123" where #123 is the ID of the deliverable. Deliverables are closed when the work is completed and the functionality has been delivered.

Tasks

Tasks describe some activity that we need to do that don't necessarily relate to or complete a whole piece of functionality.

Branches

See Repository management

A branch should be created for each sprint as the simple name of the sprint (e.g. sprint1).

Clone this wiki locally