In 30 seconds
- Teams should be able to keep their pace for months, not weeks.
- Overtime gives a short boost, then lowers quality and speed.
- Sustainable pace is a delivery strategy, not a perk.
Why it matters
One of the twelve agile principles says sponsors, developers and users should be able to maintain a constant pace indefinitely. Extreme Programming originally expressed it as a 40-hour week. Tired people make more mistakes, which create more work later.
Warning signs
- Regular evening or weekend work to hit sprint commitments
- Rising defect counts and technical debt
- Sprint Goals routinely met only by heroics
- People leaving or disengaging
How teams protect it
- Plan to realistic capacity, not wishful velocity
- Leave slack for unplanned work
- Use WIP limits to stop overload
- Treat repeated overtime as a problem to discuss in the retrospective
Myth vs reality
Myth · Sustainable means slow.
Reality · Steady teams usually deliver more over months than crunching ones.
Myth · Crunch before a launch is unavoidable.
Reality · Occasional pushes happen; regular crunch is a planning failure.
Myth · Pace is each person's responsibility.
Reality · It's set by the system: commitments, priorities and staffing.
FAQ
Is a short crunch ever OK?
Rarely and briefly, followed by recovery and a look at why it happened.
How does velocity relate to pace?
A stable velocity is a sign of sustainable pace; spikes often aren't.
Who protects the pace?
The whole team, with support from the Scrum Master and management.