Scrum guide · Scrum events
The Scrum Sprint Cycle: Length, Time-box and Rules
The Sprint is the heartbeat of Scrum: a fixed-length event of one month or less in which ideas are turned into value. All the other Scrum events happen inside it, and a new Sprint starts as soon as the previous one ends.
Key takeaways
- Sprints are fixed-length, one month or less, back to back.
- Don't change scope in ways that endanger the Sprint Goal.
- Only the Product Owner can cancel a Sprint.
Rules of the Sprint
- Sprints are of fixed length, one month or less.
- No changes are made that would endanger the Sprint Goal.
- Quality does not decrease.
- The Product Backlog is refined as needed.
- Scope may be clarified and renegotiated with the Product Owner as more is learned.
Choosing a Sprint length
| Length | Pros | Cons |
|---|---|---|
| 1 week | Fast feedback; low risk | Higher event overhead |
| 2 weeks | Balanced; most common | — |
| 3–4 weeks | Room for complex work | Slower feedback; more risk per Sprint |
Shorter Sprints generate more learning cycles and limit risk to a smaller amount of time and cost.
A two-week Sprint at a glance
| Day | Activity |
|---|---|
| Day 1 | Sprint Planning; work starts |
| Days 1–10 | Daily Scrum every day; development; refinement |
| Day 10 | Sprint Review, then Sprint Retrospective |
| Next day | New Sprint begins with Sprint Planning |
Cancelling a Sprint
A Sprint can be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel it. Cancellation is rare and disruptive; it usually means the business environment changed suddenly.
Tips
- Keep Sprint length stable to learn your team's pace.
- End Sprints mid-week to avoid Monday holidays and Friday fatigue.
- Protect the Sprint from scope changes that threaten the goal.
- Finish items rather than starting many in parallel.
Free templates for this topic
Frequently asked questions
Can a Sprint be extended?
No. If work isn't finished, the Sprint still ends on time, and unfinished items return to the Product Backlog.
Is a Sprint the same as an iteration?
Yes. Sprint is Scrum's term for an iteration. See what is a sprint.
How long should a Sprint be?
One month or less. Many teams choose two weeks as a balance between fast feedback and event overhead, then keep the length stable.
Can Sprint length change?
It can, but changing it often makes planning and forecasting harder. If you change it, do so deliberately, for example after a Retrospective, and keep the new length consistent.
What happens to unfinished work at the end of a Sprint?
Incomplete Product Backlog items return to the Product Backlog, where the Product Owner re-orders them. They do not count towards the Increment.
Can you add work to a Sprint in progress?
Scope can be clarified and renegotiated with the Product Owner as more is learned, but no changes should endanger the Sprint Goal. Developers can add tasks to the Sprint Backlog as their plan evolves.
What is a Sprint Goal?
The single objective for the Sprint, created during Sprint Planning. It gives the Developers focus and flexibility over exactly which work delivers it. See Sprint Planning.
Who can cancel a Sprint?
Only the Product Owner, and only if the Sprint Goal becomes obsolete.
Are one-week Sprints a good idea?
They give very fast feedback and suit teams with fast-changing priorities, but events take a larger share of the time. Some teams with one-week Sprints move to Kanban if planning feels like overhead.
Can a team have a Sprint without a release?
Yes. Each Sprint must produce at least one usable Increment, but whether to release it is a business decision.
What is a hardening Sprint?
A Sprint dedicated to stabilising and testing previous work before release. It is not part of Scrum and often signals that the Definition of Done is too weak.