Stop committing to fantasy sprints. Plug in your team, sprint length, PTO, and focus factor. See exactly how many person-hours and story points your team can deliver.
Most engineering teams sit between 60-70% focus factor (the rest is meetings, code review, support, ad-hoc).
—
SprintFlint pulls actual completed points each sprint and rolls them into your capacity for the next one. No spreadsheet drift.
Start FreeFocus factor is the percentage of working hours your team actually spends on sprint work. The remainder goes to meetings, code review, interrupts, support, planning, and context-switching. Most engineering teams realistically sit between 60-70%. New teams often discover they're closer to 50% in practice.
Multiply team size × sprint working days × hours per day to get raw person-hours. Subtract PTO hours. Apply your focus factor. The result is the realistic person-hours available — not the theoretical maximum.
Use your historical velocity (average story points completed per sprint). Divide your available person-hours by the historical hours-per-point ratio. We use a default of 6 hours per point, then adjust if you provide your team's actual velocity.
Most teams over-commit because they plan against raw hours, not focus-adjusted hours. The "suggested commit" here is what your team can realistically finish without working evenings or pulling cards into the next sprint.
Start at 60%. Track actual velocity for 2-3 sprints, then back-calculate your real focus factor. New teams almost always find they're optimistic the first time.