Sprint — Explained with Examples

Sprint is a fixed-length iteration in the Scrum framework, typically lasting 1–4 weeks (2 weeks is the most common). Each sprint starts with Sprint Planning and ends with a Sprint Review and Retrospective. The team commits to a Sprint Goal — a concise objective that the sprint aims to achieve.

During a sprint, the team works from the Sprint Backlog (a subset of the Product Backlog). Scope is typically frozen once the sprint begins; if new work emerges, it goes on the backlog for future sprints. The cadence provides predictability: stakeholders know exactly when a potentially shippable increment will be ready. Sprints embody the Agile principle of delivering value incrementally and frequently.

Real-world analogy. A sprint is like a “cooking challenge” episode on a TV show. Chefs get a fixed time (e.g., 45 minutes) to prepare a dish. They plan their approach, cook, and present the result. When the clock hits zero, they stop — whether the dish is perfect or not. The time box creates focus and urgency.

Example (Two-week sprint schedule):

Week 1              Week 2
Mon: Sprint Planning  Mon: Development
Tue-Thu: Development  Tue-Wed: Testing
Fri: Internal demo    Thu: Sprint Review
                      Fri: Retrospective

Related terms: Scrum, Standup, Retrospective, Burndown Chart, Agile

Related tutorial: Sprint Planning Guide