An AI scrum master.
It briefs you on the sprint before the standup, flags the decisions that need you and explains why, and runs the ceremonies. Ask it anything about the sprint, an epic, a board or your own work.
Twenty-five of twenty-nine points done, the goal still reachable, two issues that will not close and a bug with no owner. Each one carries the reason it was raised.
The cockpit
Your briefing, and the decisions that need you.
One screen shows how the sprint is going: velocity, capacity, open blockers and scope added since the start. Beside it, a short queue of decisions that need a person, and the ceremonies it is running. Type in the bar at the bottom to ask it anything.
Scrum Manager, your working scrum master. It briefs, recommends, and runs the ceremonies.
Sprint 18 ends tomorrow. 25 of 29 points are done and the sprint goal is within reach.
Two issues will not close in time and one bug still has no owner. I have put both on your list below. I will keep watch and flag anything else that needs your call.
Every recommendation comes with its reason.
See what needs a decision, and why.
On a good day the queue is empty and it says the sprint is on track.
- Get a one-sentence briefing on where the sprint stands
- See velocity, capacity, open blockers and scope added mid-sprint
- See which issues are unlikely to close, and why it thinks so
- See who has gone quiet, and for how long
- Overrule any recommendation, because the reasoning is on screen
It runs the ceremonies.
The standup, the backlog and the retro are ready before you ask.
- Get the standup drafted from what actually changed
- Get the backlog shaped before planning starts
- Get the retro booked before the sprint ends
- Ask why you are behind, or for a summary of the blockers
- Point any question at a sprint, epic or board with @sprint, @epic, @board or @mine
Access
Who can do what.
Anybody on the team can ask about their own work. Accepting a recommendation changes the sprint, and deciding what it runs on its own changes everybody's week, so those need a higher role.
See the briefing and how the sprint is going.
Ask about your own work and act on a recommendation.
Accept its recommendations for the sprint.
Set the rules and choose what it runs on its own.
Admin is the highest role and is not constrained by the permission grid, so it is worth keeping to the smallest group that genuinely needs it.
One morning, start to finish
Three decisions before the standup.
It checked the sprint before anybody was in, summed up where it stood in one sentence, and flagged the three things that needed a person. Then it drafted the standup from what changed and booked the retro, because the sprint ends tomorrow and no retro was on the calendar.
Points done, blockers open, what moved since yesterday.