May 19, 2026
5 min read
Capacity and sprint planning
Focus Factor Explained for Sprint Planning
A plain-English explanation of focus factor in sprint planning, what it is trying to capture, and why it helps teams plan from realistic delivery time instead of ideal calendar time.
Start with usable delivery time
Focus factor is a way to estimate how much of the team's nominal sprint time is likely to become real, usable delivery time.
In simple terms, it reflects the gap between the hours that exist on the calendar and the time the team can actually spend moving sprint work forward.
Focus factor
Focus factor works best as a realism check on usable delivery time, not as a magic multiplier.
Usable time
Start from the time the team can actually spend on delivery.
Protect focus
It exists to make interruptions visible before commitment.
Interruptions count
Meetings, support, and context switching reduce real capacity.
Not a fixed number
A useful focus factor changes with the sprint conditions.
Planning realism
Used well, focus factor turns calendar time into a more honest sprint view.
Why teams need it
Sprint planning gets misleading fast when teams assume that all available hours are equally usable for delivery.
In reality, a sprint always includes meetings, interruptions, coordination, support work, and context switching. Focus factor exists to account for that normal friction instead of pretending it does not exist.
What focus factor is trying to protect
Focus factor protects the team from building a sprint commitment on theoretical full availability.
It helps the team leave room for the way work actually happens instead of planning from a best-case calendar that rarely exists in practice.
What usually lowers focus factor
Focus factor tends to drop when the sprint is meeting-heavy, when people are split across multiple responsibilities, or when support and interruptions are a meaningful part of normal work.
It can also shift when the team is onboarding new people, coordinating across several roles, or carrying unusual operational load.
- Recurring meetings.
- Interruptions and support work.
- Context switching across teams or roles.
- Coordination-heavy work.
Why it is not just a fixed magic number
Some teams talk about focus factor as if it were a single stable percentage, but in practice it can shift with the sprint conditions.
A team with several holidays, a major launch, or unusual support pressure may have a very different usable focus factor than it had last sprint.
What usually goes wrong
Focus factor becomes unhelpful when the team treats it as a decorative metric instead of a real planning constraint.
If the commitment does not change when the focus factor clearly drops, the number is not actually protecting the sprint from anything.
- The team assumes full availability anyway.
- Focus factor is guessed without looking at sprint reality.
- Meeting and support load are known but not reflected in the plan.
- The number exists, but it never changes the commitment.
What healthy use looks like
Healthy use of focus factor usually feels calmer than people expect. The team uses it to make the sprint more realistic, not to introduce extra math theater.
It is most useful when it helps the team accept that a smaller honest commitment is better than a larger one built on imaginary focus time.
Where to go next
If focus factor makes sense conceptually but your team still plans from ideal time instead of usable time, the capacity tool is the best next step.
That is where the team can turn real availability and reduced focus time into a sprint commitment that fits the way work actually happens.
TL;DR
- Focus factor turns nominal sprint time into usable delivery time.
- Meetings, interruptions, support work, and context switching lower focus factor.
- It should change the sprint commitment when real capacity drops.
- Focus factor only helps when it reflects real delivery conditions instead of pretending to be a fixed rule.