MethodologiesBasic

Sprint

A fixed-length period (one month or less) in Scrum during which one or more Done, usable product Increments are created.

Pronunciation

/sprɪnt/
"sprint"
Listen on:Forvo Cambridge

What is it

A Sprint is the heartbeat of Scrum. It’s a fixed time period (typically 2 weeks) during which:

  1. Work is selected from the Product Backlog
  2. A product increment is developed
  3. Something potentially usable is delivered

According to the Official Scrum Guide:

“Sprints are the heartbeat of Scrum, where ideas are turned into value.”

Common pronunciation mistakes

  • ❌ “es-print” (adding an initial vowel and splitting it into two syllables)
  • ❌ “sprin” (the final ‘t’ is pronounced)

Sprint Characteristics

Characteristic Description
Fixed duration One month or less; keeping it constant is recommended
Timeboxed Always ends on the agreed date
Protected Sprint Goal No changes are made that would endanger the Sprint Goal (scope can still be clarified and renegotiated with the Product Owner)
Consistent quality The Definition of Done is not reduced

The Sprint Cycle

┌─────────────────────────────────────────────────────────┐
│            SPRINT (2 weeks, approximate durations)       │
├─────────────────────────────────────────────────────────┤
│                                                          │
│   Sprint        Daily        Development   Sprint Sprint │
│   Planning  →   Scrum  →     work       → Review → Retro│
│   (4h)         (15min/day)               (2h)    (1.5h) │
│                                                          │
└─────────────────────────────────────────────────────────┘

The 4 Events within a Sprint

1. Sprint Planning

Duration: Maximum 8 hours for a 1-month Sprint

Defines:

  • What: What can be delivered in this Sprint?
  • How: How will the work be accomplished?
  • Sprint Goal: Single objective that guides the Sprint

2. Daily Scrum

Duration: 15-minute timebox

Daily meeting where Developers inspect progress toward the Sprint Goal and adapt their plan. The 2020 Guide doesn’t mandate a format; many teams still use the three classic questions:

  • What did I do yesterday?
  • What will I do today?
  • Are there any impediments?

3. Sprint Review

Duration: Maximum 4 hours

The Increment is inspected and the Product Backlog is adapted:

  • Demo of completed work
  • Stakeholder feedback
  • Priority adjustments

4. Sprint Retrospective

Duration: Maximum 3 hours

The team reflects on how to improve:

  • What went well?
  • What can we improve?
  • Concrete actions for the next Sprint

Real-World Example: Building a Delivery App

Imagine you’re developing a food delivery app.

Sprint 1: The MVP (2 weeks)

Sprint Goal: “Users can view restaurants and place a basic order”

Day Work
1 Sprint Planning: define stories
2-3 Restaurant list
4-5 Menu page
6-7 Shopping cart
8-9 Basic checkout
10 Sprint Review + Retrospective

Result: Working app with basic order flow

Sprint 2: Improvements based on feedback (2 weeks)

Sprint Goal: “Improve search and payment experience”

  • Restaurant filters
  • Real payment gateway
  • Push notifications
  • Bug fixes from Sprint 1

Sprint Rules

✅ Can be done during a Sprint:

  • Refine the Product Backlog (the 2020 Guide no longer sets a time percentage)
  • Clarify scope with the Product Owner
  • Renegotiate scope (not quality) with the Product Owner if necessary

❌ Cannot be done:

  • Make changes that would endanger the Sprint Goal (if the goal becomes obsolete, only the Product Owner can cancel the Sprint)
  • Reduce quality (Definition of Done)
  • Extend the duration
  • Add work that compromises the Sprint Goal

What if we don’t finish everything?

It’s normal. What matters is:

  1. Don’t extend the Sprint - It ends when it ends
  2. Deliver what’s done - Only what meets the Definition of Done
  3. Return to Backlog - Incomplete items return to the Product Backlog
  4. Learn - Why didn’t we finish? (discuss in Retrospective)
Duration Ideal for
1 week Experienced teams, high uncertainty
2 weeks Most common, good balance
3 weeks Projects with more ceremony
4 weeks / 1 month Maximum allowed, complex projects

Tip: Once you choose a duration, keep it consistent throughout the project.

Common Anti-patterns

Anti-pattern Problem Solution
Variable Sprint “This Sprint will be 3 weeks” Keep fixed duration
Mini-waterfall Design → Development → Testing sequential Work in parallel
Scope Creep “Just add this little thing…” Protect the Sprint Goal
Incomplete demo “This is 90% done…” Only show finished work
  • Scrum - Framework that contains the Sprints
  • Daily Standup - Daily meeting within the Sprint
  • Sprint Planning - Event that starts the Sprint
  • Sprint Review - Event to inspect the Increment (the Retrospective is what concludes the Sprint)

Remember: The Sprint is a fixed time container. It’s better to deliver less with quality than more half-done. Consistency and predictability are more valuable than speed.

All terms