- Product and Sprint Backlogs
- User story
- Estimate / Actual / Velocity
- Sprint Planning / Review / Retrospective
- Scrum Facilitator
- Product Owner
- What have you done since the last stand-up?
- What are you working on next?
- What is blocking your work?
- User story creation
- Sprint planning
- User story estimates
- Sprint backlog
- A testable product iteration
- A validated product iteration
- Sprint review
- Sprint retrospective
- Backlog refinement
- A realistic expectation of your team’s capacity for the next sprint.
On longer projects, 3-4 sprints might be wrapped in a release.
The release cycle gives an opportunity to iteratively review progress, resourcing and budget against business expectations.
- 3-4 Sprints
- Review of progress vs business need
At the start of the build, set time aside to prioritise and label your user stories, estimate your velocity and set your sprint goals.
At the end of each sprint (on Thursdays), complete a sprint review, retrospective, and plan for the next sprint.
At the end of the final sprint, make sure you complete your handover documentation.
And don’t forget the daily stand-up.