Skip to content
JiraVision

AI Scrum Master

Introduction to AI Scrum Master

How the draft plan is built from capacity, history and skills — and why nothing reaches your board until a human accepts it.

45 minutes · 5 steps

No recording published

We are not going to embed a video that does not exist. What follows is the outline the session works through, in order — every step names a page or a setting you can open yourself. When a recording is published it appears above this note.

Follow it in the dashboard

Session outline

What the session covers, step by step.

  1. 1

    The approval gate

    Every recommendation is a draft. Accepting it writes through the normal task and sprint endpoints, so it produces the same notifications and activity entries as a manual edit.

  2. 2

    What the draft reads

    Open load per member, story points completed in recent sprints, meeting and PTO pressure for the next seven days, and the skills recorded on each member.

  3. 3

    The rationale per item

    Each suggested task carries a plain-language reason rather than a bare score, so you can disagree with the reasoning instead of guessing at it.

  4. 4

    Health score, burndown and velocity forecast

    The gauge, the actual/ideal/projected burndown lines and the forecast are all computed from the same task rows you can see on the board.

  5. 5

    Dismissing and re-drafting

    Dismissed recommendations move to an archive that keeps the reason, and a mid-sprint re-draft names what slips and why.

Want a session on something else?

Tell us what your team is stuck on and we will say honestly whether we can cover it.

Propose a session

Get the outline by email

One email when a session outline or a recording is published. No tracking pixels.