Sprint

A sprint is Scrum's basic unit of time: a fixed, short cycle — usually two weeks — in which a team commits to a set of work and delivers it in a usable state. Sprints are why agile teams have a rhythm, and the sprint boundary is where an executive engages: you steer between sprints, not during them.

What It Is

A sprint is a time-boxed iteration with a fixed length (one to four weeks; two is common), a goal selected at sprint planning from the prioritised backlog, and a definition of done that items must reach before the sprint closes. The time-box is the discipline: work that won't finish moves to a future sprint rather than stretching the current one — sprints never extend. The cycle repeats continuously, giving delivery a heartbeat: plan, build, demonstrate at review, improve at retrospective, repeat. A sprint's committed scope is a forecast, not a contract; what is sacrosanct is the cadence and the working increment at its end.

Why It Matters to You

The sprint structure hands executives a clean steering interface. Scope may be re-prioritised between sprints at no process cost — which is precisely what makes agile responsive; interrupting a sprint in progress is possible but corrosive, reserved for genuine emergencies. Sprint length itself is a tuning decision: shorter sprints give faster feedback and coarser increments; longer ones suit work with heavy setup. When a team's sprints routinely end without a demonstrable increment, the methodology has become scheduling theatre — the sprint exists, the point of it does not.

When You'll Meet It

In sprint planning priorities, reviews, and any request to add work mid-flight. The rule of thumb to communicate: new priorities enter at the next sprint boundary; only incidents interrupt the current one.