Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for scrum masters

Sprint Review Demo Readiness Agent

A sprint review agenda that shows only done work, ready to demo

Sprint Review Demo Readiness Agent: what goes in, what the agent does and what you get

What it does

Sprint reviews lose stakeholder trust when a demo fails or work shown as done is not really finished. Two days before the review, this agent lists items marked done and gathers evidence that tests passed, code merged and the feature is deployed to the demo environment. It compares that evidence with the Definition of Done and asks owners for anything missing. Items that do not pass every check are labeled as preview or removed. It drafts the agenda with one named demo owner per item and a short stakeholder invite. The Scrum Master approves the agenda and invite. On the morning of the review it checks the demo environment again. If an item now fails, it moves it to a not done list, updates the agenda and checks again. Edge case: work shown only as a preview is clearly labeled so stakeholders do not count it as delivered.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
ApprovedYes, continueNo 1 STARTS WHEN Two days before review 2 USES A TOOL List done items and gather evidence of tests, mergeand deploy 3 DOES Compare evidence with the Definition of Done 4 DOES Draft agenda with demo owners and invite summary 5 YOU APPROVE Scrum Master approves agenda and invite 6 USES A TOOL Check demo environment on review morning 7 CHECKS THE RESULT Does every agenda item still pass? If not: move failing items to the not done list andupdate the agenda. Back to step 3. 8 RESULT Final review agenda
Read the steps as a list
  1. Two days before review
  2. List done items and gather evidence of tests, merge and deploy
  3. Compare evidence with the Definition of Done
  4. Draft agenda with demo owners and invite summary
  5. Scrum Master approves agenda and inviteThe agent waits here for your OK.
  6. Check demo environment on review morning
  7. Does every agenda item still pass?If not: move failing items to the not done list and update the agenda. Back to step 3.
  8. Final review agenda

How it decides

An item is shown as done only if all Definition of Done checks pass; anything else is labeled as preview or removed.

  • Undeployed items are not shown as done
  • Previews are labeled clearly
  • Each item has one named demo owner

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • Definition of Done checks
  • Demo environment URL
  • Review lead time (default 2 days)
  • Stakeholder groups

What keeps you in control

It always asks you first

  • Agenda and stakeholder invite

Hard limits

  • Never changes item status
  • Never sends invites without approval

It stops when

  • Done: agenda final
  • Stop: demo environment down, suggest recorded demos

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensTwo days before the September 4 review, nine items were marked done but two had no deploy to the demo environment. One owner deployed in time; the other item became a preview. The Scrum Master approved the agenda. On review morning the morning check failed: the search feature returned errors. The agent moved it to not done, cut the agenda to seven items and rechecked them all.

More agents for scrum masters