The Sprint: Container for All Events

The Sprint is the heartbeat of Scrum—a fixed-length event of one month or less that contains all other Scrum events.

Key characteristics:

• Fixed length: Once decided, Sprint length doesn't change mid-Sprint
• Consistent: Sprints follow each other immediately, no gaps
• Contains a Goal: Each Sprint has a Sprint Goal that provides focus
• Produces an Increment: Something potentially shippable by the end

Common Sprint lengths:

• 1 week: High-feedback environments, high uncertainty
• 2 weeks: Most common, balances feedback with focus time
• 3-4 weeks: Larger, more complex work (use sparingly)

The Sprint Goal is the single objective for the Sprint. It provides:

Focus: A clear target that guides daily decisions. When priorities conflict, the Sprint Goal is the tiebreaker.

Coherence: Individual items connect to something meaningful. The Sprint isn't just a random collection of tasks.

Flexibility: As long as the Goal is achieved, the specific items can be adjusted. This protects the Sprint from scope creep while allowing adaptation.

Good Sprint Goals are:

• Business-focused: "Enable users to reset passwords" not "Implement password reset endpoint"
• Measurable: You can tell if you achieved it
• Achievable: The team believes it's possible
• Singular: One main objective, not a list

Sprints can be cancelled, but it's rare and only the Product Owner can do it.

When to cancel:

• The Sprint Goal becomes obsolete (market shift, strategy change)
• Continuing would be wasteful given new information

What happens:

• Completed work is reviewed
• Remaining work returns to the Product Backlog
• A new Sprint is planned immediately

Signs something is wrong (but don't cancel for these):

• Team won't hit all their commitments—adjust scope, don't cancel
• Stakeholder wants something different—negotiate, don't cancel
• Team is struggling—help them, don't cancel