Keep Scrum. Keep Jira. Change what the board means.
Most frameworks ask you to start over. VECTOR adds one hypothesis, one number and five lines per epic to the tools and cadence you already run. Below is a normal sprint board — flip the switch to see what changes.
Your board, before and after.
Pick the tool you already use — the board takes on its colours and layout. Before is the board as your team runs it today; After is the same board with VECTOR bolted on. Same data throughout: three epics across two teams, nine tickets, sprint 14. Click an epic to focus its tickets.
Every Scrum element has a VECTOR counterpart. Most already exist in your tool.
| You have | It becomes | What actually changes |
|---|---|---|
| Sprint (2 weeks) | Proof Window | Keep the cadence. Add one hypothesis at the start and a written verdict at the end. Sprint goal → hypothesis. |
| Epic | Outcome Brief | The epic description becomes five fields: problem, desired outcome (number + date), success metrics, dependencies, owner. |
| Stories / tasks under the epic | Enabler Sheet rows | Nothing changes on the ticket except one new field: Confidence. The epic’s child list is the sheet. |
| Story points | Confidence Score (0–100) | Estimate belief in delivering the outcome, not effort. Re-score at each window review. Points can stay if you like them. |
| Blocked flag / “is blocked by” link | Explicit dependency | Already exists in most tools. Make it point at an epic (outcome), not just a ticket, when the dependency is cross-team. |
| Sprint review + retro | Window review (15 min, written) | Three questions: did the hypothesis hold, what is the evidence, what is confidence now. Add a retro only if you want one. |
| Daily stand-up | Optional | Keep it if the team likes it. VECTOR does not require it — the artifacts carry the status. |
| Roadmap / portfolio view | Nested outcomes + dependency map | Company outcome on top, team outcomes beneath. Filter your tool by the Confidence field for the executive view. |
Thirty minutes, no plugins, no admin ticket.
Everything below uses standard Jira Software features: custom fields, issue links, dashboards. Project admin rights are enough. Paths may differ slightly between Jira Cloud and Data Center.
Jira is a trademark of Atlassian. VECTOR is not affiliated with or endorsed by Atlassian.
- 01
Add a Confidence field
Project settings → Fields → Create custom field → Number. Name it “Confidence (0–100)”. Add it to the Epic and Story screens. Optional: a Number range validator of 0–100.
5 min - 02
Turn the epic description into an Outcome Brief
Edit the Epic issue type’s description template (or add five short-text fields): Problem · Desired outcome · Success metrics · Dependencies · Owner. Keep each to one or two lines.
10 min - 03
Rename the sprint’s goal field in your head
Sprint goal = the window’s hypothesis. Write it as something that can be true or false at the end of the sprint (“completion ≥ 50% for new cohorts”), not a list of tickets.
0 min - 04
Make cross-team dependencies explicit
Use the existing “is blocked by” link type, but link epic to epic when another team owns the blocker. Add a board quick-filter for issues with an open blocker.
5 min - 05
Build the executive view
A dashboard with a Filter Results gadget: type = Epic AND status != Done, columns Summary · Confidence · Assignee · Updated. Sort by Confidence ascending so the risks are on top.
10 min - 06
Run the first window review
At sprint end, in the review meeting you already have: read the hypothesis, write the evidence in the epic, update Confidence on the epic and its stories, set next sprint’s goal as the next hypothesis. Done.
15 min, recurring
The same four ideas, wherever your work lives.
Project = Outcome Brief (use the description template). Cycle = Proof Window. Custom “Confidence” property on projects and issues. Roadmap view for nesting.
See it on a Linear boardPortfolio = company outcome; Project = team outcome. Custom number field “Confidence”. Milestones as window boundaries; dependencies are native.
See it on a Asana boardBoard group = Proof Window; item = enabler; numbers column “Confidence”. A high-level board with mirror columns is the executive view.
See it on a Monday.com boardGoal = Outcome Brief with Targets as metrics. Sprint = Proof Window. Custom field “Confidence”; use Dependencies natively.
See it on a ClickUp boardOne database of outcomes with the five brief fields plus Confidence; a related database of enablers. A linked view filtered to this window is the review.
No tool at all? The playground is a complete standalone implementation — export the JSON when you are ready to move it somewhere permanent.
Open the playgroundProduct names are trademarks of their respective owners and are used here only to describe compatibility.
Start with one team and one sprint.
Pick the epic that matters most this quarter. Write its Outcome Brief in the description. Set the sprint goal as a hypothesis. Add the Confidence field to its stories. Run the sprint exactly as you would have. At the review, answer three questions in writing and re-score.
If leadership reads the Confidence column instead of the burndown by the third sprint, expand to the next team. If they don’t, you have lost thirty minutes of configuration.
- Sprint cadence and ceremonies you find useful
- Story points, if the team likes estimating with them
- Every ticket, board, filter and automation you have today
- One hypothesis per sprint
- One 0–100 Confidence field, re-scored each review
- Five lines per epic: problem, outcome, metrics, dependencies, owner
- Cross-team dependencies that point at the other team’s outcome
- Any ceremony the artifacts now make redundant — your call, per team