In 30 seconds
- A sprint is a fixed timebox of one month or less; two weeks is common.
- It contains all other Scrum events, back to back.
- Each sprint has one Sprint Goal and ends with a usable Increment.
What happens in a sprint
A sprint starts with Sprint Planning, runs a Daily Scrum every day, and ends with a Sprint Review and a Sprint Retrospective. The next sprint starts immediately after.
Rules that protect it
- No changes that would endanger the Sprint Goal.
- Quality doesn't drop to hit a date.
- Scope can be clarified and renegotiated with the Product Owner as the team learns.
Choosing a length
Shorter sprints mean faster feedback and less risk; longer ones mean less meeting overhead. Two weeks is the most common balance. Keep the length steady so the team's velocity stays meaningful.
Cancelling a sprint
Only the Product Owner can cancel a sprint, and only when the Sprint Goal has become obsolete, for example after a major change in direction. It's rare.
Myth vs reality
Myth · A sprint is a mini-waterfall.
Reality · Design, build and test happen together throughout the sprint.
Myth · Nothing can change once the sprint starts.
Reality · The goal is fixed; the detailed plan adapts.
Myth · Hardening sprints are normal.
Reality · Each sprint should produce a done Increment; "hardening" hides unfinished work.
FAQ
Why is it called a sprint?
It's a short, focused push toward a goal; in Scrum it has nothing to do with working faster.
Can we change sprint length?
Occasionally, but frequent changes make planning and velocity unreliable.
Is there a gap between sprints?
No. A new sprint starts right after the previous one ends.