Capacity-first sprint plan
Commit by available hours and skills before story points get anyone into trouble.
- Capacity worksheet
- Skills matrix
- Slack buffer rule
For: Teams that consistently over-commit
AI-native project management
JiraVision reads your team's capacity, history and workload, then helps you plan sprints and protect wellbeing — with you approving every decision.
The problem
Most teams plan against hope, not capacity — and the cost shows up as missed sprints, quiet burnout and metrics nobody trusts.
Sprints get committed on optimism, not on who is actually available, skilled and at capacity this week.
Overload hides in overtime, after-hours commits and shrinking review quality until someone quits.
Velocity leaderboards reward the loudest work and quietly punish care, review and mentoring.
The four pillars
Each pillar works alone; together they keep delivery commitments and team health in the same conversation.
Draft sprint plans that account for real capacity, past velocity and skills — then explain the reasoning behind every suggestion.
Workload and mood signals aggregated anonymously, so you rebalance before burnout instead of after.
Skill trees and rewards built around real engineering work — reviews, mentoring and reliability count too.
Monitor workload distribution, inclusion and fairness indicators — and see exactly how each number is calculated.
How it works
Four steps, no black boxes.
Link Jira and your calendar. JiraVision reads boards, issues and cycles — read-only until you say otherwise.
Granite models summarise capacity, history and workload patterns across the team, anonymously aggregated.
Get a drafted sprint with per-item rationale. Adjust anything, then approve — nothing changes without you.
After each cycle, compare predictions with reality and watch the plan quality — and team load — steady out.
Product tour
Every suggested item carries a reason: who has capacity, which skills match, what the last three sprints actually finished.
Sprint planning sandbox
Auto-draft fills the sprint optimising for skill fit and nothing else. Someone quietly ends up carrying the plan while someone else waits. Propose a rebalance, read every move, and apply only what you agree with.
Runs entirely in your browser on sample data — in the product this reads your real Jira capacity.
Backlog · unassigned
Nine sample tickets, one sprint, no crystal ball.
Team load spread
100100 minus how unevenly points land across people, with a penalty for anyone over capacity. A low score means someone's week is quietly already lost.
Ada Kwarteng
frontend · qa · 8 pts capacity
Jonas Meier
backend · 14 pts capacity
Tessa Pham
infra · 8 pts capacity
Rin Sato
frontend · 12 pts capacity
Deterministic draft: best skill match first, then smaller tickets, then backlog order — no randomness, same input, same plan.
Gamification playground
A toy version of the real thing — you decide what counts, and nobody competes on speed.
On: the XP UI shows branch totals for the team. Off: you can see exactly why we default this on.
Recognition only works when people choose it. The playground respects that.
Locked · unlocks at 2 Craft XP
Locked · unlocks at 5 Craft XP
Locked · unlocks at 9 Craft XP
Reviews, safe shipping and keeping the codebase tidy.
Locked · unlocks at 2 Collaboration XP
Locked · unlocks at 4 Collaboration XP
Locked · unlocks at 6 Collaboration XP
Pairing, unblocking and sharing context.
Locked · unlocks at 3 Stewardship XP
Locked · unlocks at 7 Stewardship XP
Locked · unlocks at 11 Stewardship XP
Mentoring, docs and follow-through.
Ethical metrics
Which engineer is quietly overloaded? Switch metrics and watch the same six-person team through four lenses.
Synthetic numbers. The point is the pattern: every metric here opens to show exactly how it's calculated.
Engineer A is taking on 1.4× the team's average sprint load. (Watch above 130% of the team mean.)
| Engineer | Band | Sprint pointspts | Reviews per weekreviews/wk | After-hours commitscommits/mo | Comp index× band midpoint |
|---|---|---|---|---|---|
| Engineer Awatch * | III | 41 | 3 | 2 | 1.04 |
| Engineer B | II | 38 | 4 | 5 | 0.98 |
| Engineer C | II | 36 | 9 | 4 | 1.00 |
| Engineer D | III | 21 | 6 | 3 | 0.86 |
| Engineer E | I | 18 | 2 | 11 | 1.06 |
| Engineer F | I | 24 | 2 | 3 | 0.95 |
Trust
AI that manages people's workloads has to answer for its decisions. Here is where we stand — plainly.
JiraVision proposes; your team decides. No sprint, reassignment or message is applied without approval.
Wellbeing and load signals are aggregated at team level. Individual answers are never shown to managers raw.
Every AI suggestion links to the data behind it and the model that produced it (IBM Granite). You can read the reasoning, disagree and edit.
We are early-stage: SOC 2 and GDPR alignment are in progress, not certifications we hold today. Ask us about specifics.
Use cases
Walk into planning with a capacity-true draft, the evidence behind it, and a live view of who is quietly overloaded.
Integrations
Live integrations are available today; planned items are labelled and not yet shipped.
Results
We will publish measured results once we have them. Until then, here is what teams tell us they feel first.
Measured outcomes coming soon — we publish numbers only after we can verify them.
Try the models
Burnout pressure for your team, and an ROI projection with every assumption visible. Both run on your inputs, in this tab.
Committed work regularly exceeds available hours.
Little say over scope, sequencing or how the work gets done.
Goals shift mid-sprint and "done" is negotiable.
Evenings, weekends or standby becoming the norm.
Effort and care outpace what the team visibly counts.
Rate each for your team, honestly. 0 = never, 10 = constant.
Burnout pressure
45
Watch
Nothing on fire, but headroom is thin. Protect slack and check the trend after the next two cycles.
Biggest single driver: Sustained overload. In the product this view is built from signals your tools already emit — and it is aggregated so no individual answer is ever shown raw.
Illustrative models for a product demo — not a clinical assessment or a financial instrument.
Steal our playbooks
Twelve routines we hand new workspaces on day one. Browse a few — the full library ships inside the product.
Commit by available hours and skills before story points get anyone into trouble.
For: Teams that consistently over-commit
A 25-minute routine that keeps priorities honest without a meeting marathon.
For: Product + eng pairs
Four retro styles on a cycle so the room doesn't calcify into complaint theatre.
For: Established scrums
Show working software and the care behind it — reviews, fixes and docs count too.
For: Teams up to 30 people
Introduce limits in stages, measure flow, and keep the team's veto real.
For: Kanban-ish teams
Anonymous mid-sprint pulse with team-level-only reporting, from day one.
For: Leads who suspect, don't know
A concrete protocol for the week after a hard deadline — decompression built in.
For: On-call and launch teams
Spot the overloaded person before standup #20 and move work, not blame.
For: Scrum masters and EMs
Nine metrics with formulas, anti-patterns and the question each one answers.
For: First dashboards
Compare drafts to reality each cycle — estimate quality, not blame quality.
For: Quarterly planning prep
Operational docs people actually update, with owners and expiry dates.
For: Tribal-knowledge escape
Track which AI drafts you accepted, edited or rejected — and why.
For: Teams piloting AI planning
Want one adapted to your workflow? Ask us
Testimonials
“The sprint draft was the first plan in two years my team didn't immediately argue with. It had already counted holidays.”
“We caught a colleague carrying three sprints' worth of load mid-cycle and rebalanced. That used to surface in the exit interview.”
“Opening a metric and seeing its formula ended a standing argument with my staff engineers. That alone was worth it.”
Example quotes from early-access conversations. We publish attributed testimonials only with permission.
Built for keyboards
Jira's best-loved feature is JQL. We agree. JiraVision is fast on your hands first: command palette, two-key navigation, and a product that stays out of the mouse's way.
Pricing
Every plan includes the AI Scrum Master and wellbeing signals. Team size scales the rest.
$9/user/mo
Up to 10 users, one Jira project
12 seats → $86/mo (annual)
$19/user/mo
Unlimited projects, ethical metrics, priority support
12 seats → $182/mo (annual)
$49/user/mo
SSO, advanced controls, dedicated onboarding
12 seats → $470/mo (annual)
Connect Jira, get your first capacity-aware draft in minutes, and approve every step yourself.