AI Scrum Master
How AI changes the agile routine
The ceremonies an AI assistant genuinely improves, the ones it leaves alone, and the five numbers worth measuring in your own workspace instead of trusting ours.
Read articleAI Scrum Master
What an AI Scrum Master actually does: where the draft comes from, what the rationale contains, and why nothing reaches your board until a person accepts it.
4 min read24 October 2026JiraVision team
An AI Scrum Master is not a chatbot with a sprint calendar. In JiraVision it is a recommendation engine with an approval gate: it reads the same task rows you can see on the board, produces a draft plan with a written reason for every item, and then waits. Nothing is written to your sprint until a person accepts it.
This guide covers what the draft reads, what the rationale contains, how acceptance works, and where the feature stops on purpose.
The draft plan is built from four inputs, every one of which is visible somewhere in the workspace:
Nothing here is inferred from chat content or from activity telemetry. If a signal is not already a row in your workspace, the model does not use it.
Every suggested task carries a plain-language reason: why this person, why this sprint, what capacity assumption it rests on. That is a deliberate choice, for two reasons.
A score without a reason invites two bad responses — ignoring it entirely, or deferring to it uncritically. Both are worse than not having the feature.
Accepting a draft writes through the ordinary task and sprint endpoints. That matters more than it sounds: the same notifications fire, the same activity entries are written and the same validation runs as if you had made the change by hand. There is no privileged write path for the model.
Dismissing works the same way in reverse. A dismissed recommendation moves to an archive that keeps the reason you gave, so a pattern of dismissals stays visible later instead of disappearing.
Re-drafting mid-sprint is allowed, and it names what slips. Accept a revised plan in week two and the draft tells you which committed items no longer fit and why, rather than quietly re-planning around them.
Three views sit alongside the draft, all computed from task rows:
Each one prints its own formula in the ethical metrics documentation. If a number cannot show you how it was produced, it does not belong on the page.
These refusals are product decisions, not gaps in a roadmap:
The AI Scrum Master documentation lists every endpoint and field. The metrics guide explains the formulas behind the health gauge and the forecast. And if you would rather see it move, the dashboard page runs against your own tasks.
Written by the JiraVision team. Corrections and disagreements welcome via the contact page.
AI Scrum Master
The ceremonies an AI assistant genuinely improves, the ones it leaves alone, and the five numbers worth measuring in your own workspace instead of trusting ours.
Read articleTeam Wellbeing
Remote work removed the signals that tell you how a colleague is doing. Rebuilding them on purpose is mostly a scheduling and reporting problem, not a policy one.
Read articleTeam Wellbeing
The five factors behind the burnout score, the four bands it maps to, and the interventions that actually move the number — starting with the disclaimer.
Read articleDouble opt-in, no tracking pixels, and an unsubscribe link in every message.