Sprint length and planning day decision
This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Teams that drift between one, two and three week sprints never build a velocity worth reading, because every number is measured against a different yardstick.
First tasks
- Count how many sprint lengths the team has used in the last six months
- Propose one length and one planning day in the team channel
- Book recurring planning, review and retrospective slots for six sprints
- Mark public holidays and freeze weeks against each sprint