Skip to content
JiraVision

AI-native project management

Sprints that plan themselves. Teams that don't burn out.

JiraVision reads your team's capacity, history and workload, then helps you plan sprints and protect wellbeing — with you approving every decision.

Built on open, accountable foundations
  • IBM Granite· AI models powering sprint insights
  • Jira· Two-way sync with your boards
  • Human-in-the-loop· Every AI suggestion needs your approval

The problem

Sprint planning is set up to fail

Most teams plan against hope, not capacity — and the cost shows up as missed sprints, quiet burnout and metrics nobody trusts.

01

Planning by gut feel

Sprints get committed on optimism, not on who is actually available, skilled and at capacity this week.

02

Burnout arrives late

Overload hides in overtime, after-hours commits and shrinking review quality until someone quits.

03

Metrics that mislead

Velocity leaderboards reward the loudest work and quietly punish care, review and mentoring.

The four pillars

One system for planning, people and fairness

Each pillar works alone; together they keep delivery commitments and team health in the same conversation.

AI Scrum Master

Draft sprint plans that account for real capacity, past velocity and skills — then explain the reasoning behind every suggestion.

  • Capacity-aware drafts
  • Transparent rationale
  • You approve, it executes
Explore AI Scrum Master

Team Wellbeing

Workload and mood signals aggregated anonymously, so you rebalance before burnout instead of after.

  • Early overload signals
  • Anonymised by design
  • Suggested re-balances
Explore Team Wellbeing

Gamification

Skill trees and rewards built around real engineering work — reviews, mentoring and reliability count too.

  • Skills, not just speed
  • Team-level recognition
  • Opt-in and configurable
Explore Gamification

Ethical Metrics

Monitor workload distribution, inclusion and fairness indicators — and see exactly how each number is calculated.

  • Methodology on every metric
  • Drift and imbalance alerts
  • No surveillance scoring
Explore Ethical Metrics

How it works

How it works

Four steps, no black boxes.

  1. 1.Connect

    Link Jira and your calendar. JiraVision reads boards, issues and cycles — read-only until you say otherwise.

  2. 2.Analyse

    Granite models summarise capacity, history and workload patterns across the team, anonymously aggregated.

  3. 3.Plan

    Get a drafted sprint with per-item rationale. Adjust anything, then approve — nothing changes without you.

  4. 4.Improve

    After each cycle, compare predictions with reality and watch the plan quality — and team load — steady out.

Product tour

See the working views

A draft plan you can defend

Every suggested item carries a reason: who has capacity, which skills match, what the last three sprints actually finished.

DEMO
live in your browser, no signup

Sprint planning sandbox

Watch a sprint overload itself — then fix it, one approved move at a time

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.

0 of 42 pts committed · sprint is empty — run the auto-draft

Backlog · unassigned

Nine sample tickets, one sprint, no crystal ball.

  • Auth token refresh flow
    5 pts
    JV-101backend
  • Sprint retro summary view
    3 pts
    JV-104frontend
  • Export CSV endpoint
    2 pts
    JV-108backend
  • CI pipeline speedup
    3 pts
    JV-112infra
  • Onboarding empty states
    4 pts
    JV-115frontend
  • Regression pack for billing
    3 pts
    JV-118qa
  • Search ranking fix
    5 pts
    JV-121backend
  • Staging environment rebuild
    5 pts
    JV-124infra
  • Wellbeing check-in modal
    3 pts
    JV-127frontend

Team load spread

100

100 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.

AK

Ada Kwarteng

frontend · qa · 8 pts capacity

0/8
  • No work assigned — capacity left on the table.
JM

Jonas Meier

backend · 14 pts capacity

0/14
  • No work assigned — capacity left on the table.
TP

Tessa Pham

infra · 8 pts capacity

0/8
  • No work assigned — capacity left on the table.
RS

Rin Sato

frontend · 12 pts capacity

0/12
  • No work assigned — capacity left on the table.

Deterministic draft: best skill match first, then smaller tickets, then backlog order — no randomness, same input, same plan.

DEMO

Gamification playground

A skill tree that rewards how good teams actually work

A toy version of the real thing — you decide what counts, and nobody competes on speed.

Recognised behaviours
Tick what the team did this week. Every point here was chosen by the team, not by us.
Guardrails
The two switches the real product ships with. Flip them and watch what changes.

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.

Skill tree
Three branches, three nodes each. Unlocks come from recognised behaviours, never from ticket speed.
Craft0 XP
  • Review Craft

    Locked · unlocks at 2 Craft XP

  • Safe Shipping

    Locked · unlocks at 5 Craft XP

  • Debt Hunter

    Locked · unlocks at 9 Craft XP

Reviews, safe shipping and keeping the codebase tidy.

Collaboration0 XP
  • Pairing Basics

    Locked · unlocks at 2 Collaboration XP

  • Unblocker

    Locked · unlocks at 4 Collaboration XP

  • Team Glue

    Locked · unlocks at 6 Collaboration XP

Pairing, unblocking and sharing context.

Stewardship0 XP
  • Runbook Author

    Locked · unlocks at 3 Stewardship XP

  • Follow-through

    Locked · unlocks at 7 Stewardship XP

  • People First

    Locked · unlocks at 11 Stewardship XP

Mentoring, docs and follow-through.

Level 1 · Getting started0 XP
0 of 6 XP toward level 2 — “Warming up”.
Demo data

Ethical metrics

Workload & equity explorer

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.

Within watch bandPast watch threshold (marked *)Team mean

Engineer A is taking on 1.4× the team's average sprint load. (Watch above 130% of the team mean.)

Synthetic demo dataset — six anonymised engineers. Active metric: Sprint points · watch above 130% of the team mean.
EngineerBandSprint pointsptsReviews per weekreviews/wkAfter-hours commitscommits/moComp index× band midpoint
Engineer Awatch *III41321.04
Engineer BII38450.98
Engineer CII36941.00
Engineer DIII21630.86
Engineer EI182111.06
Engineer FI24230.95

Trust

Security, privacy and responsible AI

AI that manages people's workloads has to answer for its decisions. Here is where we stand — plainly.

Human-in-the-loop, always

JiraVision proposes; your team decides. No sprint, reassignment or message is applied without approval.

Anonymity by default

Wellbeing and load signals are aggregated at team level. Individual answers are never shown to managers raw.

Explained, not magic

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.

Honest about compliance

We are early-stage: SOC 2 and GDPR alignment are in progress, not certifications we hold today. Ask us about specifics.

Read our responsible-AI approach

Use cases

Built for the people who carry the outcome

Stop defending sprint commitments you didn't choose

Walk into planning with a capacity-true draft, the evidence behind it, and a live view of who is quietly overloaded.

  • Draft plans with per-item rationale
  • Load alerts before the retro
  • Estimate quality tracked over time

Integrations

Works with your stack

Live integrations are available today; planned items are labelled and not yet shipped.

  • Jira
    Issues, boards and sprints
    live
  • GitHub
    PR and commit signals
    planned
  • GitLab
    Merge and pipeline signals
    planned
  • Slack
    Digests and check-ins
    planned
  • Microsoft Teams
    Notifications
    planned
  • Google Calendar
    Meeting-load context
    planned

Results

What changes

We will publish measured results once we have them. Until then, here is what teams tell us they feel first.

  • Planning meetings get shorter because the draft is ready before them.
  • Rebalancing happens mid-sprint, not after a resignation.
  • Metric disputes shrink when the formula is visible next to the number.

Measured outcomes coming soon — we publish numbers only after we can verify them.

Try the models

Two calculators we'd rather show than describe

Burnout pressure for your team, and an ROI projection with every assumption visible. Both run on your inputs, in this tab.

Sometimes

Committed work regularly exceeds available hours.

Sometimes

Little say over scope, sequencing or how the work gets done.

Sometimes

Goals shift mid-sprint and "done" is negotiable.

Rarely

Evenings, weekends or standby becoming the norm.

Sometimes

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

Starter templates for calmer delivery

Twelve routines we hand new workspaces on day one. Browse a few — the full library ships inside the product.

Planning
capacity-sprint

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

Planning
backlog-triage

Weekly backlog triage

A 25-minute routine that keeps priorities honest without a meeting marathon.

  • Triage checklist
  • Decision log template
  • Escalation lanes

For: Product + eng pairs

Rituals
retro-rotate

Rotating retro formats

Four retro styles on a cycle so the room doesn't calcify into complaint theatre.

  • Ship-it / sailboat / starfish prompts
  • Action-owner sheet

For: Established scrums

Rituals
demo-day

Demo day that isn't a status meeting

Show working software and the care behind it — reviews, fixes and docs count too.

  • Run-of-show
  • Recognition slots
  • Async recording guide

For: Teams up to 30 people

Rituals
wip-limits

WIP-limit rollout

Introduce limits in stages, measure flow, and keep the team's veto real.

  • Rollout phases
  • Flow metrics sheet
  • Escape-hatch policy

For: Kanban-ish teams

Wellbeing
checkin-pulse

Wellbeing check-in pulse

Anonymous mid-sprint pulse with team-level-only reporting, from day one.

  • Question set (5)
  • Aggregation rules
  • Act-on thresholds

For: Leads who suspect, don't know

Wellbeing
after-hours

After-hours recovery plan

A concrete protocol for the week after a hard deadline — decompression built in.

  • Load-drop schedule
  • Meeting blackout block
  • Standby handoff notes

For: On-call and launch teams

Wellbeing
load-rebalance

Mid-sprint rebalance playbook

Spot the overloaded person before standup #20 and move work, not blame.

  • Signal list
  • Rebalance moves menu
  • How to say it script

For: Scrum masters and EMs

Metrics
metric-menu

Ethical metrics starter menu

Nine metrics with formulas, anti-patterns and the question each one answers.

  • Metric cards
  • Formula appendix
  • Do-not-ranking list

For: First dashboards

Metrics
predictability

Predictability review

Compare drafts to reality each cycle — estimate quality, not blame quality.

  • Commit vs finish sheet
  • Drift chart spec
  • Review agenda

For: Quarterly planning prep

Docs
runbook

Team runbook kit

Operational docs people actually update, with owners and expiry dates.

  • Runbook skeleton
  • Review cadence
  • Searchability rules

For: Tribal-knowledge escape

Docs
ai-review

AI suggestions review log

Track which AI drafts you accepted, edited or rejected — and why.

  • Decision log
  • Reason codes
  • Monthly digest template

For: Teams piloting AI planning

Want one adapted to your workflow? Ask us

Testimonials

What early teams say

“The sprint draft was the first plan in two years my team didn't immediately argue with. It had already counted holidays.”

EM
Early-access participant — Engineering manager
Series B fintech

“We caught a colleague carrying three sprints' worth of load mid-cycle and rebalanced. That used to surface in the exit interview.”

PO
Early-access participant — People ops lead
Product studio

“Opening a metric and seeing its formula ended a standing argument with my staff engineers. That alone was worth it.”

CT
Early-access participant — CTO
Health-tech startup

Example quotes from early-access conversations. We publish attributed testimonials only with permission.

Built for keyboards

If it can be typed, it can be typed

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.

  • Open search anywhere⌘K
  • Shortcut cheat sheet?
  • Go to pricingGthenP
  • Go to contactGthenC
  • Close any overlayEsc

Pricing

Simple plans, no surprises

Every plan includes the AI Scrum Master and wellbeing signals. Team size scales the rest.

14-day trial, no card

Starter

$9/user/mo

Up to 10 users, one Jira project

12 seats → $86/mo (annual)

Professional

Most picked

$19/user/mo

Unlimited projects, ethical metrics, priority support

12 seats → $182/mo (annual)

Enterprise

$49/user/mo

SSO, advanced controls, dedicated onboarding

12 seats → $470/mo (annual)

12 seats

FAQ

Questions teams ask us

All questions

Plan sprints your team can actually finish

Connect Jira, get your first capacity-aware draft in minutes, and approve every step yourself.