AI Scrum Master
The complete guide to AI Scrum Masters
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.
Read articleAI 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.
4 min read24 October 2026JiraVision team
Agile ceremonies are cheap to describe and expensive to run. Planning takes an hour because nobody has read the backlog. Stand-up takes twenty minutes because three people are reciting status nobody asked for. The retro produces four action items and completes none of them.
AI helps where the cost is bookkeeping. It does not help where the cost is judgement. This article draws that line, ceremony by ceremony.
Planning splits into two jobs. The first is arithmetic — how many points fit, given who is available, what they already carry, and what the last few sprints actually delivered. The second is negotiation — which of these matters now, and what are we willing to drop.
The arithmetic is a good automation target because it is the same calculation every sprint and because humans do it badly under time pressure. JiraVision drafts the plan from open load, completed points in recent sprints, meeting and time-off pressure, and the skill tags on each member, then writes a reason for every suggested item.
The negotiation stays with the team. The draft is a starting position, and accepting it is a human action that writes through the ordinary task endpoints.
A daily call in which everyone recites yesterday, today and blockers is a status report wearing a meeting's clothes. The parts that need a room are the exceptions: a blocker open three days, a task that has changed owner twice, a dependency on another team that has gone quiet.
Collect the routine part asynchronously and spend the synchronous time on what the flags turned up. Blocker age is the most useful single signal here, because it is already sitting in your task data and because it is hard to argue with.
Historical data improves estimates in one specific way — it tells you which kinds of task consistently overrun. If everything tagged "integration" has taken twice its estimate for three sprints running, that is a real, checkable pattern and it is worth putting in front of the team at planning time.
It does not make estimation accurate in general. Any tool quoting a percentage improvement in estimation accuracy is reporting a number it cannot reproduce on your data, because the number depends entirely on what your team was estimating before.
What you can measure is the gap between estimated and completed points, per sprint, in your own workspace, over the sprints you have actually run. That is a smaller claim and a useful one.
Retros fail for one reason more than any other — nothing comes back. Action items are written, the next retro starts fresh, and after three cycles the team stops answering honestly because answering has been shown to do nothing.
The cheap fix is to carry action items forward as tasks with owners and due dates, and to open the next retro by reading out what happened to the last set. JiraVision stores retro action items on the delivery side for exactly this reason: a completed action item is then visible in the same place, with the same status semantics, as a completed task.
There is no productivity percentage in this article, and that is deliberate. Here are the numbers you can pull from your own data before and after a change, all of which live on pages you can already open:
Take a baseline for two sprints before you change anything. A number you did not measure beforehand cannot tell you whether the change worked.
Where AI earns its place is in removing the bookkeeping that makes the ceremonies expensive, so the time in the room goes to the decisions only people can make.
Written by the JiraVision team. Corrections and disagreements welcome via the contact page.
AI 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.
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.