Course contentsShow
← Software Engineering
Lesson 1586 of 1,93346. Agile MethodologiesFree lesson

Sprints in Scrum

Time-boxed iterations (typically 2 weeks) where a potentially releasable increment is created from selected backlog items.

Sprints in Scrum

You'll learn what Sprints are and how they structure the work of delivering value in Scrum.

What Is a Sprint?

A Sprint is a time-boxed iteration—usually lasting two weeks (though one to four weeks is common)—during which the Development Team works to create a potentially releasable increment of the product. Think of a Sprint as a mini-project with a fixed deadline: the team selects items from the Product Backlog, commits to completing them, and aims to deliver working software by the end.

The time-box is sacred. You don't extend a Sprint because work isn't done—you adjust scope or carry incomplete items to the next Sprint.

How Sprints Work

At the start of each Sprint, the team conducts Sprint Planning, selecting Product Backlog items they believe they can complete. Throughout the Sprint, the Development Team collaborates daily (often via a daily standup) to track progress and address blockers. The Scrum Master helps remove impediments, while the Product Owner remains available for clarification.

At Sprint's end, the team holds a Sprint Review to demonstrate the increment to stakeholders and gather feedback, followed by a Sprint Retrospective to reflect on how they can improve their process.

Why Time-Boxing Matters

Fixed-length Sprints create predictability and rhythm. Stakeholders know when to expect updates. Teams learn their velocity—how much they can realistically accomplish—and improve estimation over time. The short cycle forces frequent feedback, allowing the team to adapt quickly to changing requirements or new insights.

Think of Sprints like heartbeat: a regular, reliable cadence that keeps the project alive and responsive.

Key Takeaway:
Sprints are time-boxed iterations (typically 2 weeks) where teams deliver a potentially releasable product increment, ensuring regular feedback, predictability, and continuous improvement.