From scattered history to a plan you can trust.
For your next PI or quarterly planning, Outcome Vault reads what your teams really finished in Jira and shows, as you plan, whether each sprint fits and how likely it is to be delivered.
How it works
A plan is only as good as the capacity behind it.
See which sprints are over capacity before the quarter starts.
Copied by hand
Work moves from Jira to a whiteboard and back, card by card, before and after every planning.
Committed on hope
Capacity is a guess from story points or velocity, often counted as hours, and a show of hands decides if it fits.
Found out too late
Spill-over shows up at the sprint review, when the quarter's plan is already broken.
- Capacity, from finished work
- Committed beyond capacity
Plan every sprint on the capacity your team really has.
Bring in the backlog
Features and stories come straight from your Jira projects into a list of work to plan.
Plan against real capacity
Drag work into sprints. Each sprint shows its load against what the team really finishes, holidays included, and how likely it is to be delivered.
Apply to Jira
One click puts every issue in its sprint, after showing you exactly what will change.
- Planned within capacity
- Over capacity
- Capacity, from finished work
Example data. The dashed line is what the team really finishes, read from its past sprints.
Commit to numbers you can defend.
Ranges, not promises
Forecasts at 50%, 85% and 95% likelihood, never a single date.
Your data's health, first
Problems in your Jira data that would skew a forecast are shown up front, with what they change.
Works on the Jira you have
No clean-up and no setup: capacity comes from the finished work already in your history.
Stays in Atlassian
Outcome Vault runs inside Jira. Your data never leaves Atlassian.
Check it fits the way your teams plan.
How is this different from planning with story points and velocity?
Velocity adds up the story points a team estimated. Outcome Vault counts the work each team really finished, sprint by sprint, from its Jira history. Teams can keep their story points, but points never set capacity.
Our sprints keep spilling over. How does this help?
While you plan, it shows which sprints hold more work than the team really finishes, so overcommitment is fixed before the quarter starts, not found at the sprint review. It advises; the team decides.
How is team capacity worked out for PI planning?
From the work each team really finished in its past sprints, read from Jira: no estimates and no setup. Each team gets its own capacity, from its own history.
How likely is our PI plan to be delivered?
As you plan, each sprint shows its chance of being delivered, so a plan that looks full but is unlikely to hold is caught before anyone commits. Move work, and the chance updates at once.
How are holidays and time off counted in sprint capacity?
Each team enters its days off per sprint as one total (say, 12 days off in sprint 3), and that sprint's capacity accounts for them. Nothing is recorded per person.
Does it work for quarterly or big room planning, not only PI planning?
Yes: for any group of teams planning several sprints ahead in Jira, whether the event is called PI planning, quarterly planning or big room planning.
Is Outcome Vault on the Atlassian Marketplace yet?
Not yet. Outcome Vault is in development and coming to the Atlassian Marketplace, for Jira Cloud only (not Data Center or Server). To vote on it, use the buttons below.
How much will Outcome Vault cost?
Plans and prices are being finalised for the launch on the Atlassian Marketplace, where it will be billed on your Atlassian invoice.
Would your teams plan this way?
Outcome Vault is in development and coming to the Atlassian Marketplace. One anonymous vote helps shape it: nothing to buy, nothing to sign up for.
Anonymous: no cookies and no personal data. This browser only remembers that it voted.