Sprint
A timeboxed iteration in Scrum, typically 1-4 weeks.
Detailed Explanation
A sprint is a timeboxed iteration in Scrum of one month or less during which a usable and potentially releasable product increment is created. Sprints are the heartbeat of Scrum — they provide a regular cadence of planning, execution, review, and adaptation.
Each sprint follows a consistent structure: Sprint Planning (what and how), Daily Standups (synchronization), Development Work, Sprint Review (inspect the increment), and Sprint Retrospective (inspect the process). The sprint length should remain consistent throughout the project.
The key rule of sprints is that the timebox is sacred — sprints are never extended. If the team cannot complete all planned work, remaining items return to the backlog. This discipline forces realistic planning and prevents scope creep within the sprint.
Key Points
- Timeboxed to 1-4 weeks (2 weeks is most common)
- Produces a usable, potentially releasable increment
- Consistent structure: Planning, Standup, Work, Review, Retro
- Sprint length should remain consistent
- Never extended — incomplete work returns to backlog
- The heartbeat of Scrum
Practical Example
A team runs 2-week sprints. Sprint Planning: team commits to 8 user stories (34 story points). Day 1-10: development with daily standups. Day 10: Sprint Review — demo 7 completed stories to stakeholders (1 story incomplete, returns to backlog). Day 10 PM: Sprint Retrospective — team identifies slow code reviews as the main bottleneck and agrees to implement same-day review policy.
Tips for Learning and Applying
Keep sprint length consistent — changing it disrupts velocity measurement
Never extend a sprint — the timebox discipline is what makes Scrum work
Commit to what the team can realistically deliver based on historical velocity
Use the sprint cadence to build team rhythm and stakeholder expectations
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.