The Scrum Framework — Second Edition

This chapter retains the second edition’s historical and practical teaching context. The third-edition curriculum is also available in the contents below.

---

What is a Sprint? - International Scrum Institute

In the Scrum Framework all activities needed for the implementation of entries from the Scrum Product Backlog are performed within Sprints (also called 'Iterations'). Sprints are short: normally about 2–4 weeks, with a timebox of one month or less.

Each Sprint follows a defined process as shown below:

This second-edition example divides Sprint Planning into two discussions: the WHAT-Meeting and the HOW-Meeting. Together, these discussions make up the Scrum Sprint Planning Meeting. In the WHAT discussion, the team selects Product Backlog items and agrees on a Sprint Goal. In the HOW discussion, the developers plan how to deliver that work, often breaking User Stories into smaller, concrete tasks. Then implementation begins.

At the end of the Sprint, a Sprint Review brings the Scrum Team and stakeholders together to inspect the outcome, discuss completed work, and adapt the Product Backlog. A Sprint Retrospective also helps the team improve how it works: what went well during the Sprint, what should continue, and what should improve.

During the Sprint, the developers hold a short Daily Scrum to inspect progress toward the Sprint Goal and adapt their plan. A standing meeting is one possible format, not a requirement.