Exclude Sprint from Events

[pedicurus]

In Scrum, every event except the Sprint has a defined timebox—and each of them can end earlier if the purpose is achieved.

From a logical perspective, we classify things into the same type when they share key characteristics. All Scrum events, except the Sprint, share common features, especially with respect to timeboxing. The Sprint, however, stands apart in this regard.

By distinguishing the Sprint from the other events, we make this difference more transparent. This separation could significantly improve clarity for both learners and practitioners.

[rjocham]

@pedicurus the Sprint was always odd one. How would you explain it; which type would it be if not an event?

[pedicurus]

@rjocham

Totally agree the Sprint is the “odd one.” I’m not suggesting we stop calling it an event; I’m suggesting we name its type explicitly so learners don’t assume it behaves like the others.

Two sub-types of Scrum events

• Container (cadence) event — the Sprint

  • Fixed length (≤ 1 month) and consistent across Sprints

  • Container for all work and the other events

  • Does not end early when “purpose is achieved”; it only ends via normal cadence or cancellation if the Sprint Goal becomes obsolete (by the Product Owner)

  • Purpose: maintain cadence, protect focus on the Sprint Goal, enable predictability

• Session events — Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective

  • Scheduled sessions with defined attendees and outcomes

  • Timeboxed and may end early when the purpose is achieved

  • Purpose: structured inspection and adaptation inside the Sprint

Why this helps: people routinely ask, “We finished early—can we end the Sprint?” Grouping everything under “events” without sub-types invites that mistake. Naming the Sprint as a container/cadence event makes its special rules obvious while keeping us aligned with the Scrum Guide.

If you really want a different noun, “iteration” or “cadence window” also describe the Sprint. Or simply we can say Scrum starts with a sprint including four events. What is Sprint? It is an iteration (not timebox) and a container for all work and the other events.

[ViralGoodAgile]

Hi @pedicurus - We like your idea, “cadence window,” but we'd prefer to use it in the Sprint description rather than create event types. We also like "container of focus, self-management, balance, etc."

[pedicurus]

@ViralGoodAgile I am happy to hear that.

[mhuynh1188]

What about intervals or cadence cycle?