What is a Sprint
The Sprint is the container event in Scrum. It is a fixed-length period, one month or less, during which the team creates a usable Increment. All other Scrum events happen inside the Sprint.
Sprints are consecutive. A new Sprint starts as soon as the previous one ends.
Why It Matters
The Sprint creates a regular cadence for delivering and learning.
A fixed Sprint length forces small batches. Small batches surface problems early, build trust with stakeholders, and limit risk to one Sprint of work.
Teams that run consistent Sprints can forecast capacity, plan releases, and make commitments stakeholders can trust.
How It Works in Scrum
A Sprint includes:
- A fixed length. One month or less. Two weeks is most common. The length stays consistent.
- A Sprint Goal. A single objective set in Sprint Planning.
- A Sprint Backlog. The selected work plus the plan to deliver it.
- A usable Increment. Meets the Definition of Done by Sprint end.
- The other four events. Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.
The Product Owner can cancel a Sprint, but only if the Sprint Goal becomes obsolete. Cancellation is rare.
Scope inside the Sprint can flex through conversation between the Product Owner and Developers. The Sprint Goal does not.
Common Mistakes
- Variable Sprint length. Two weeks, then four, then one. Cadence and predictability are gone.
- Sprints without a Sprint Goal. A to-do list is not a goal.
- Sprints that produce no Increment. The Sprint failed at its main purpose.
- Mid-Sprint scope expansion. New work breaks the plan. Refine for the next Sprint instead.
- Sprints treated as phases. "Design Sprint, then build Sprint, then test Sprint" is not Scrum.
Key Takeaways
- The Sprint holds all other Scrum events.
- Sprints are fixed-length and consecutive.
- Every Sprint produces a usable Increment.
- Risk is limited to one Sprint of work.