The 10% Scrumban rule for every sprint
Committing to full capacity makes every sprint fragile. A 10% Scrumban buffer absorbs risk, protects the sprint goal and lets velocity grow naturally.

Many teams plan to use exactly the capacity shown in their Jira plan. That is often a mistake and leads to failed sprints. Why does it happen when the capacity calculations look so precise?
The rush to deliver more
Product Owners tend to push for higher velocity after every successful sprint, a natural reaction to the latest results. If the team completed a certain number of story points last sprint, it is expected to complete more next sprint. This repeats until a sprint fails. The push is an attempt to test the team's limits. In our experience, it is counter-productive. It ultimately demotivates the team, who come to see every future sprint as doomed.

The doomed sprint
The hectic end of a sprint during a delivery rush
When capacity is planned to fill the sprint exactly, any delay or realized risk creates pressure to work at a frantic pace at the end. The team then delivers less than promised because stress takes over. That end-of-sprint rush should be eliminated.
Let the team deliver more by its own will
Plan only 90% of the team's capacity and reserve the remaining 10% for unplanned backlog work. Those tasks are pulled from the backlog in Scrumban fashion during the sprint. The buffer absorbs risk and lets the team finish the sprint (or at least the sprint goal) a few days early. If an external dependency threatens the sprint, a buffered task can replace the problematic one.
That 10% is not part of the sprint commitment. If risk does not materialize, the team delivers it as extra work; if something goes wrong, the buffer is consumed but the sprint goal and commitment are still met. Monitor how much of the buffer is used: if it regularly reaches 20%, for example, it is time to raise the team's velocity by 10% while keeping the 10% buffer.

Deliver early, deliver extra
Our experience shows that this is when employees work without pressure and contribute the most. Velocity can then increase at the team's own pace, without outside pressure and with less stress. The increase feels natural and sustainable.
Related articles
- Managing sprint dependencies with chained pull requestsDependent tickets stall a sprint while people wait. Learn how stacked pull requests keep work moving and reduce idle time.
- Comparison metrics for agile teamsMetrics should create equal ground, not a leaderboard. Four comparison metrics that motivate agile teams without punishing them.
- Sheepherding story pointsOpen votes let the first estimate anchor the room. See how the sheep effect skews story points and how to run planning poker honestly.
About AELBOX
AELBOX is the team behind Scrumpy Planning Poker for Jira. We write about agile estimation, sprint planning and delivery.