The 15105 rule is a practical mnemonic designed to help agile teams remember the core operational constraints of the Scrum framework. If you're wondering what the numbers mean, they map directly to essential timeboxes and standards: a maximum 1-month sprint duration, up to 5 days for sprint planning, 15 minutes for the daily standup, zero ambiguity in the definition of done, and a maximum of 5 hours combined for sprint reviews and retrospectives. Understanding this framework helps teams cut through process bloat and focus on shipping real software.
Many agile teams fall into the trap of process theater, treating ceremonies as bureaucratic chores rather than value-driven touchpoints. The 15105 heuristic strips away the noise and returns the focus to empiricism: transparency, inspection, and adaptation. By setting rigid guardrails around time, teams protect their focus and maintain a sustainable delivery cadence. Let's break down each component of the rule and see how to apply it effectively in your organization.
Breaking Down the 15105 Framework
Every digit in the rule corresponds to a specific constraint established by the official Scrum Guide maintained by Scrum co-creators Ken Schwaber and Jeff Sutherland. When you understand why these limits exist, you can enforce them without feeling like you're imposing arbitrary rules.
The First "1": One-Month Maximum Sprint Length
Sprints are the heartbeat of Scrum. The rule specifies that a sprint cannot exceed one month. Shorter sprints, such as two weeks, are often preferred because they reduce risk and tighten the feedback loop. For another angle on this development, check out the latest coverage from Reuters.
When you limit work intervals to four weeks or less:
- Market feedback arrives faster so you don't build the wrong thing for a quarter.
- Planning accuracy improves because forecasting two weeks out is easier than planning six months ahead.
- Stakeholders get regular opportunities to inspect working increments.
The "5": Five Days Max for Sprint Planning
For a one-month sprint, sprint planning is timeboxed to a maximum of eight hours, but for typical two-week sprints, it takes far less. The "5" in the heuristic serves as an upper guardrail reminding teams not to spend an entire week debating hypothetical edge cases.
Planning sessions answer two core questions: what can be delivered in this increment, and how the work will be achieved. If planning drags on, it usually indicates that the product backlog items aren't refined enough. Teams should use backlog grooming sessions earlier in the cycle to ensure user stories have clear acceptance criteria before planning begins.
The Second "1": Fifteen-Minute Daily Standup
The daily scrum is a 15-minute event for the developers on the Scrum team. It's not a status report for managers or project directors; it's a synchronization meeting where developers inspect progress toward the sprint goal and adapt their plan for the next 24 hours.
To keep the daily scrum under 15 minutes:
- Never use it to solve complex technical problems. Flag impediments and spin up a separate breakout discussion after the meeting.
- Focus on the sprint backlog and what needs to shift today to keep items moving across the board.
- Stand up literally or figuratively to keep energy high and rambling updates to a minimum.
The "0": Zero Ambiguity in the Definition of Done
The zero stands for zero tolerance for vague completion criteria. The Definition of Done is a shared understanding of what it means for work to be releasable. Without it, team members have conflicting interpretations of whether a feature is finished, leading to hidden technical debt.
A robust definition of done typically includes:
- Code is peer-reviewed and merged into the main branch.
- Automated unit and integration tests pass successfully.
- Documentation and release notes are updated.
- Acceptance criteria verified in a staging environment.
The Final "5": Five Hours Combined for Review and Retrospective
At the end of the sprint, the team holds two final events: the sprint review to inspect the product increment with stakeholders, and the sprint retrospective to inspect team processes and plan improvements. For a one-month sprint, these combined ceremonies are timeboxed to a maximum of four to five hours.
For shorter two-week sprints, these meetings scale down proportionally—often taking two hours total. Capping these sessions ensures that people stay engaged and that the team spends most of its time building, not meeting.
Common Pitfalls When Implementing the 15105 Rule
Even experienced teams struggle when they treat agile frameworks as rigid dogma rather than practical guardrails. Here are the most frequent missteps and how to avoid them.
Treating Timeboxes as Minimums, Not Maximums
Teams often schedule a full 15 minutes for the daily scrum or a full hour for a retro even when everything is resolved in five minutes. Timeboxes are upper limits. If you finish early, give the time back to the team so they can return to focused coding.
Allowing Scope Creep Inside the Sprint
Once a sprint backlog is locked during planning, the sprint goal shouldn't change. Stakeholders often try to sneak urgent requests into an active sprint. The 15105 framework reinforces discipline: if new work is truly critical, it goes into the product backlog for the next sprint planning session.
Neglecting Continuous Refinement
If your sprint planning sessions consistently hit their maximum time limits, your backlog is starved of attention. Spend an hour mid-sprint breaking down epic stories and clarifying requirements so planning runs smoothly.
Frequently Asked Questions
Can the 15105 rule be adapted for one-week sprints?
Yes. The numbers in the heuristic represent upper boundaries based on the maximum one-month sprint limit. If your team runs one-week sprints, your sprint planning scales down to an hour or less, and your review and retrospective meetings shrink proportionally.
Is the 15105 rule part of the official Scrum Guide?
The rule is a mnemonic and heuristic created by agile practitioners to help teams remember core Scrum timeboxes. While the individual constraints match the official Scrum Guide rules, the acronym itself is a training tool rather than an official Scrum Alliance mandate.
Who is responsible for enforcing these timeboxes?
The Scrum Master acts as a coach and facilitator to ensure timeboxes are respected, but the entire team shares responsibility for maintaining the discipline required to keep ceremonies focused and productive.
What happens if we exceed the 15-minute daily limit?
If your daily standup consistently runs past 15 minutes, it's a symptom of deeper issues. You're likely trying to solve technical design problems during the meeting or inviting people who don't need to be there. Move detailed discussions to separate ad-hoc syncs involving only the relevant team members.
