Sprints & Milestones
The rhythm that turns a backlog into actual, regularly-shipped progress.
8.5.1Definition
A sprint is a fixed-length iteration (commonly one or two weeks) during which a team commits to completing a specific set of backlog items (8.3). A milestone is a larger, meaningful checkpoint — often spanning several sprints — marking significant progress toward a larger goal, such as a launch or major feature completion.
8.5.2Why It Exists
Without a regular cadence, progress can feel indefinite and hard to measure — work is "in progress" for an unbounded amount of time with no natural checkpoint to assess it against. Sprints exist to impose a predictable rhythm of commitment, delivery, and review, and milestones exist to connect that rhythm back to larger, externally meaningful goals stakeholders actually care about.
8.5.3Core Sprint Ceremonies
- Sprint planning — the team commits to a specific, sized set of backlog items for the upcoming sprint.
- Daily standup — a brief, regular check-in surfacing progress and blockers, not a full status report.
- Sprint review — completed work is demonstrated, closing the loop with stakeholders on what actually shipped.
- Retrospective — the team reflects on process itself, identifying what to improve for the next sprint.
8.5.4Common Mistakes
- Overcommitting sprint scope consistently, leaving work perpetually unfinished at sprint end and eroding trust in future commitments.
- Skipping the retrospective under time pressure, losing the team's main structured opportunity to improve its own process.
- Milestones with no clear, checkable definition of done, making it ambiguous whether a milestone was actually reached.
8.5.5Best Practices
- Size sprint commitments based on the team's actual historical delivery rate, not optimistic estimates.
- Protect the retrospective even under deadline pressure — it's where process improvement actually happens.
- Define milestones with explicit, checkable completion criteria, not a vague sense of "mostly done."