Concept 7 of 11

The Sprint

2 questions test this

The Sprint is a fixed-length event of one month or less, and every other event happens inside it. A new Sprint begins immediately after the previous one concludes, which is what gives Scrum its cadence.

What is fixed and what is not

The length of a Sprint is fixed, and so is the quality of what comes out of it, because the Definition of Done sets a standard that does not move to make a deadline reachable. Scope is the part that flexes. As the Developers learn what the work actually involves, they and the Product Owner may clarify and renegotiate it, so long as the Sprint Goal itself is not put at risk.

That combination is the whole bargain of a Sprint. You get a fixed date and a fixed standard, and in exchange the amount of work delivered is allowed to change as understanding improves.

The three constraints on a Sprint in progress

Three rules hold for the length of a Sprint, and they follow from the bargain above. No change may be made that would endanger the Sprint Goal, since the goal is the commitment the Sprint is being run to meet. Quality does not decrease, since lowering the Definition of Done would hide unfinished work rather than remove it. And the Product Backlog is refined as needed throughout, because refinement is ongoing work rather than a scheduled event, and stopping it would leave the next Sprint Planning with nothing ready to select.

Refinement is worth noticing here because it is the one of the three that describes something a team should actively be doing rather than something it must avoid.

Shorter Sprints

A shorter Sprint generates more learning cycles and confines the cost of being wrong to a smaller window, which is why each Sprint can be treated as a short project in its own right. Stretch the horizon too far and two things start to go wrong together. The Sprint Goal has longer to become invalid before anyone acts on it, and complexity accumulates faster than the team can inspect it.

Cancellation

A Sprint may be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has that authority. Cancellations are uncommon, because Sprints are short enough that finishing usually costs less than stopping.

Common misconceptions

A Sprint can be extended when the work is nearly finished.

Sprints are fixed length. Unfinished items return to the Product Backlog; the Sprint ends on its scheduled date regardless of what is complete.

Teams can take a short break between Sprints to regroup.

A new Sprint starts immediately after the conclusion of the previous one.

Anyone on the Scrum Team can cancel a Sprint.

Only the Product Owner has the authority to cancel a Sprint, and only when the Sprint Goal becomes obsolete.

2 questions test this concept

Halfway through a four week Sprint, a regulatory change makes the Sprint Goal obsolete. What does Scrum say may happen, and who decides?

  • AThe Sprint must run to its end date, and the change is picked up in the next Sprint.
  • BThe Sprint may be cancelled if the Sprint Goal becomes obsolete, and only the Product Owner has the authority to cancel it.
  • CThe Developers may cancel the Sprint since they own the Sprint Backlog.
  • DThe Sprint may be extended to absorb the regulatory change.
Check whether it stuck.

One per page, with a worked explanation.

Start the set
Related material
Book
Essential Scrum, On Sprint length and the trade-offs of shorter cycles.