Know what your team can actually deliver.
Sprint velocity forecasting, capacity planning, and estimation retrospectives — built for Scrum teams who need honest numbers, not false certainty.
No spam. One email when we launch. Unsubscribe any time.
Velocity · Focus Factor · Forecast
Sprints 1–7 · Sprint 8 forecast
The problem
Why most sprint forecasts are just guesses
Scrum teams have the data. They just don't have the tools to use it properly.
Spreadsheets without context
Velocity is tracked in rows and columns — without statistical range, trend analysis, or a way to understand if this sprint is normal or an outlier.
Capacity ignored at planning
Sprint planning uses full-team estimates while half the team is on leave, on call, or sharing attention between two projects.
Misses with no explanation
When the sprint ends under target, there's no structured record of why — so the same patterns repeat sprint after sprint.
How it works
The loop that makes forecasts improve over time
Five steps — from raw sprint history to a forecast that actually gets better.
Enter sprint history
Log past sprints — planned SP, completed SP, team availability. Bulk entry and paste-from-spreadsheet supported.
Track real capacity
Mark days off, holidays, and partial availability on the team calendar before each sprint planning session.
Get a forecast range
A statistically-weighted SP range for the next sprint — with a confidence score, not a false single number.
Review actual vs forecast
After each sprint, compare what was predicted with what was delivered. Track whether actuals land in range.
Improve calibration
Identify bias patterns, improve your estimation scale, reduce variance. The system gets more accurate with every sprint.
Core features
Everything you need to forecast accurately
All signal, no noise. Six focused tools that work together.
Team Velocity Forecast
A weighted forecast range for your next sprint — derived from real history, never a single optimistic number. Confidence score shown alongside every forecast.
Focus Factor
The bridge between capacity and velocity. Tracks SP delivered per man-day across sprints. Translates available time into a meaningful SP ceiling.
Sprint Capacity Calculator
Total available man-days for the upcoming sprint, accounting for holidays, partial availability, support duty, and leave — before you commit.
Team Calendar
Per-member availability grid with quick-tick day marking, bank holiday sets by country, partial availability, and multi-sprint rolling view.
Estimation Retrospective
After each sprint, compare forecast range vs actuals. Track bias patterns, systematic over-commitment, and whether your predictions are genuinely improving.
Story Point Calibration
Define what each scale value means to your team. Attach a reference story to each complexity level. Keep estimation sessions anchored to shared meaning.
A forecasting layer, not another PM tool.
allstorypoints does not store your backlog, manage your tickets, or replace Jira, Linear, or any task tracker. It sits alongside those tools as a focused forecasting and estimation health layer. It does one job: help your team forecast more accurately and understand why your estimates miss.
What we are
What we are not
Design principles
Honesty over comfort
Forecasts are always ranges. Confidence is always surfaced. We don't manufacture certainty we can't back up.
Feedback loops, not dashboards
The estimation retrospective is what makes the product better over time. A forecasting tool without a feedback loop is just a calculator.
Speed for repeated actions
Calendar entry, sprint logging, and anomaly marking happen constantly. The UX must make these feel fast and frictionless.
Team-relative only
All metrics compare a team to its own history. Cross-team comparisons are permanently out of scope — they produce misleading signals.