Skip to content
JiraVision
AI Scrum Master
Powered by IBM Granite

The sprint draft your team can actually defend

JiraVision reads capacity, history and skills, drafts the sprint, and writes the reasoning next to every item. You edit, you approve, nothing moves without you.

  • Per-item rationale in plain language
  • Accounts for holidays, on-call and open-ended work
  • Two-way Jira sync — read-only until you approve

The problem

Sprints fail before planning even starts

Planning meetings run on optimism and loudest-voice rules. The evidence is already in your Jira — nobody has time to read it before Thursday.

01

Capacity is a guess

Who's on leave, who's on-call, what's the real interruption rate — the plan rarely knows, so the team absorbs the difference.

02

Rationale lives in heads

Commitments get defended with vibes. When someone asks why they got three spikes, there's no written answer.

03

History doesn't repeat, it gets ignored

Last sprint's over-commitment is this sprint's input — except nobody collates it before the meeting.

What you get

A planning partner with receipts

Every capability produces something you can read, edit and approve — never an invisible action.

Capacity-aware drafts

Time off, on-call rotations and past completion rates feed one greedy, explainable pass.

Written rationale

Each suggested item carries the reason it was picked and who it fits, in plain English.

Skill matching

Stretch assignments are flagged as stretch — with the person's own opt-in.

Draft, don't commit

The plan is a proposal until a human approves it in your workspace.

Mid-sprint re-planning

When scope breaks, get a re-draft that names what slips and why.

Estimate quality tracking

Compare drafts to reality each cycle; the model's accuracy is shown, not asserted.

01

The draft arrives before the meeting

Connect Jira once. Before planning, you get a sprint proposal sized to the team's real availability — holidays, on-call and the historical gap between estimates and reality.

  • Ready-to-review proposal, not a blank board
  • Every number traces to a source you can open
  • Edit anything; the rationale updates live
A sprint team working side by side on laptops

02

Rationale you can argue with

“Ada gets the billing spike because she shipped two of them and has 6 points of slack.” When the reasoning is written down, the team can disagree with the actual reason instead of the person.

  • Plain-language explanations per item
  • Alternative assignments shown with trade-offs
  • Model confidence displayed, never hidden
Engineers reviewing a plan together

03

Human approval is the only write path

JiraVision proposes; your team decides. Board changes, reassignments and sprint content only happen when someone approves — and the approval is logged.

  • Read-only until approval
  • Every applied change is attributed and auditable
  • One-click revert for the whole draft
Two colleagues approving items on a shared screen
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.

How it works

From connected to committed in four steps

The whole loop happens inside tools you already run.

  1. Step 1

    Connect Jira

    Point JiraVision at a project. It reads boards, issues, cycles and calendars — read-only.

  2. Step 2

    Review the draft

    Open the proposal before planning. Every item shows its reason, fit and risk.

  3. Step 3

    Edit and approve

    Move, drop or swap anything. When the team agrees, one approval writes the sprint.

  4. Step 4

    Close the loop

    After the cycle, predicted vs actual is charted — and feeds the next draft.

Straight talk

Be honest about the fit

Works well if

  • Teams running Scrum or hybrid cycles in Jira
  • Leads who want planning arguments settled with evidence
  • Teams recovering from a bad over-commitment streak

Not for teams that

  • Teams wanting auto-pilot sprint management — approval is mandatory here
  • Orgs needing per-person productivity rankings
  • Non-Jira boards today (GitHub/GitLab are roadmap, labelled planned)

Who it's for

Who this changes the week of

Three seats in the planning meeting, one shared draft.

Engineering managers

Walk in with a plan that already counted the holidays, and a written answer for every “why me”.

  • Defensible commitments
  • Less re-planning by Slack
  • Predictability trend per team

Scrum masters

Facilitate from a proposal instead of a blank board; disputes move to the evidence.

  • Shorter planning sessions
  • Rationale-first conversations
  • Mid-sprint re-drafts

ICs

See why work landed on you — and push back on the reason, not the person.

  • No silent overload
  • Stretch flagged, not forced
  • Fair share visible

No black boxes

How the draft is built

The model is deliberately simple and fully inspectable. Here is the recipe.

Inputs
Jira issue history, sprint velocity, calendar availability and on-call rota, team-declared skills. Nothing else — no keystrokes, no content of messages.
Selection
A greedy pass ranks backlog items by skill fit, then size, against remaining capacity. Deterministic: same inputs, same draft.
Rationale
IBM Granite turns the selection trace into plain-English sentences. The numbers come from the algorithm; the prose comes from the model.
Safeguards
Suggestions expire after the cycle, approvals are logged and attributed, and the whole draft is reversible in one action.

Included in every plan

This product ships with the platform — Starter, Professional and Enterprise all include it. Pricing scales by seat, annual billing saves 20%.

What early teams say

“The first sprint draft in two years my team didn't immediately argue with — it had already counted the holidays.”
Early-access participant — Engineering manager — Series B fintech
“Opening an item and reading why it was picked ended the standing 'why does everyone think my work is small' argument.”
Early-access participant — Staff engineer — Product studio

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

Shipped

Recent updates for this product

  1. 2026-10-23

    Feature

    AI sprint reports

    Capacity-aware sprint drafts now ship with a written rationale per suggested item, so planning decisions can be reviewed and edited before approval.

Full changelog

FAQ

Questions about this product

All questions

Draft your next sprint before the meeting

Connect one Jira project and see the first capacity-aware draft with rationale on every item. 14-day trial, no card.