NEEDS UPDATING
Sprint Planning and Tracking
Ceremony Rota
The ceremony rota is available.
Start of the sprint
- Collectively decide which tickets should be in the sprint backlog for this sprint. As a rough guide, aim for a points total that matches the moving average in the planning spreadsheet.
During the sprint
- When you start working on a ticket, assign yourself as the owner and move it to the In Progress column.
- When a ticket is done, either move it to Done or Review/QA if it needs code review or checking by another dev team member.
- If you need to do work during a sprint that isn’t on the board and it takes longer than about an hour, please add as a task with the label
emerged
and t-shirt small, medium or large labels, depending on how long you think it will take.t-shirt small
<= 1/2 a dayt-shirt medium
<= 1 dayt-shirt large
> 1 day
Before the end of sprint
- As the sprint end nears, look at all tickets in Review/QA and move them to Done wherever possible. The scrum master and the ticket owner are responsible for this. Actions include prioritizing code reviews or getting the person who created the ticket to confirm they are happy with the result.
- Just before the end of the sprint, meet to identify tickets that will probably be required next sprint (as per the standing list of feature priorities and conversation with the product owner), and do points estimates for these.
End of the sprint
- Any tickets in Review/QA must be moved to done.
- Count points done and tally in the planning spreadsheet.
- Move all done tickets to closed.
Notes
- We do not use the Merged column.