The Ashley rule is a straightforward measurement principle that helps teams align scope, time, and effort when planning projects. It emphasizes realistic commitments by comparing available capacity against estimated task complexity.
Used across product and engineering organizations, the Ashley rule supports transparent prioritization and reduces the risk of overpromising. Teams rely on this rule to set clearer expectations with stakeholders.
Planning Framework Overview
Below is a summary of the Ashley rule applied to typical planning scenarios, showing how team capacity, story points, and sprint length interact.
| Team | Available Hours per Week | Sprint Length (weeks) | Estimated Story Points | Ashley Rule Guidance |
|---|---|---|---|---|
| Alpha Squad | 160 | 2 | 24 | Accept if complexity matches historical velocity |
| Beta Crew | 120 | 2 | 18 | Reduce scope or extend sprint |
| Gamma Team | 200 | 1 | 28 | Re-estimate or split into multiple sprints |
| Delta Group | 180 | 2 | 22 | Accept with buffer for unplanned work |
Capacity and Velocity Alignment
Under the Ashley rule, teams evaluate true capacity by considering meetings, maintenance tasks, and context switching. Velocity is tracked over several sprints to establish a reliable baseline for future planning.
When story point estimates exceed available hours, the rule prompts a review of scope or process inefficiencies. This alignment prevents burnout and protects delivery predictability.
Risk Management and Constraints
The Ashley rule treats constraints such as holidays, training, and production incidents as first-class inputs to planning. Teams explicitly document these risks and adjust commitments before signing off.
By surfacing constraints early, stakeholders understand trade-offs and can make informed decisions about priority shifts or deadline adjustments.
Stakeholder Communication
Clear communication is central to the Ashley rule, ensuring that business stakeholders see the direct link between team capacity and roadmap promises. Product owners use the rule to translate strategic goals into achievable sprint objectives.
Transparent metrics and concise explanations build trust and reduce recurring clarification requests.
Operationalizing the Ashley Rule
To make the Ashley rule part of everyday planning, teams adopt a few disciplined practices that reinforce accuracy and accountability.
- Review historical velocity at the start of each planning session
- Factor in meetings, onboarding, and support duties when calculating capacity
- Define clear thresholds for when to split work or extend timelines
- Communicate deviations early to stakeholders and document decisions
- Retrospect on estimation accuracy every few sprints and adjust the rule’s parameters
FAQ
Reader questions
How does the Ashley rule handle urgent emergency work mid-sprint?
Teams reserve a small buffer based on historical emergency frequency, and they re-scope remaining work to protect the sprint goal while addressing the urgent item.
Can the Ashley rule be combined with relative story point estimation?
Yes, the rule works alongside story points by comparing total estimated points to the team’s measured capacity in hours.
What should a team do if the Ashley rule suggests reducing scope frequently?
Investigate recurring causes, such as unstable dependencies or under-estimation, and adjust definitions of ready or team capacity accordingly.
Does the Ashley rule apply to maintenance and support teams?
Yes, support teams map their available hours, incident load, and break times into the rule to set realistic response and resolution targets.