Scrum Events

The Sprint

The Sprint is the heartbeat of Scrum — a fixed-length container within which all other events occur and ideas are turned into value. Every Sprint is a short project with a consistent cadence that creates rhythm, predictability, and regular opportunities to inspect and adapt.

The containing event · Timebox: ≤ 1 month

Overview

The Sprint is the heartbeat of Scrum — a fixed-length container within which all other events occur and ideas are turned into value. Every Sprint is a short project with a consistent cadence that creates rhythm, predictability, and regular opportunities to inspect and adapt.

Event Ownership

Owned / Facilitated By
Product Owner
Defines and communicates the Product Goal that the Sprint works toward
Has sole authority to cancel a Sprint if the Sprint Goal becomes obsolete
Ensures the Product Backlog is refined and ordered before Sprint Planning
Negotiates scope with Developers as new information emerges mid-Sprint

Who Should Be Present

Scrum Master
Coaches the team on maintaining Sprint discipline, ensures no changes endanger the Sprint Goal, and shields the team from external disruption
Developers
Commit to delivering Increments meeting the Definition of Done, adapt their plan daily, and maintain quality throughout
Product Owner
Available throughout the Sprint to clarify requirements, answer questions, and renegotiate scope as learning occurs

Preparation Checklist

01Product Backlog should be refined with enough items ready for at least one Sprint
02The team should have a clear, current Definition of Done
03Previous Sprint Retrospective action items should be visible and tracked
04Stakeholders should understand the Sprint cadence and when to expect reviews

Facilitation Techniques

Click any technique to expand details and learn when to apply it.

Sprint Length Calibration

Choose Sprint length based on risk tolerance and learning needs. Shorter Sprints (1–2 weeks) generate more feedback loops and limit risk. Longer Sprints (3–4 weeks) suit complex work needing deeper research. Most teams find 2 weeks optimal.

Click to expand

Mid-Sprint Health Check

Around the Sprint’s midpoint, do a quick pulse check: Is the Sprint Goal still achievable? Are there emerging impediments? This isn’t a formal event — it’s a 5-minute conversation to surface concerns early.

Click to expand

Sprint Goal Visibility

Post the Sprint Goal prominently — on the team’s board, in their Slack channel, on a monitor. When the Goal is constantly visible, every decision can be measured against it.

Click to expand

Tips & Tricks

01
Never let quality decrease — technical debt accrued in one Sprint compounds in every Sprint after
02
Scope can be renegotiated with the Product Owner, but the Sprint Goal is sacred
03
Use Sprint boundaries as natural reset points — new Sprint, fresh start, clean energy
04
Track Sprint cancellations and near-misses as signals of upstream planning issues
05
Encourage ‘finish what you start’ culture — completing fewer items fully beats partially completing many

Success Takeaways by Role

What each participant should walk away with when this event is run well.

Developers

Clear sense of accomplishment from delivering a working Increment; confidence in their capacity and velocity

Product Owner

Validated assumptions about user needs; data-informed decisions about what to prioritize next

Scrum Master

Observations about team dynamics and process health; impediments identified for systemic resolution

Stakeholders

Visible progress toward the Product Goal; trust in the team’s ability to deliver consistently