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

Stand-Up Focus Board Prep Agent

Give the scrum master a short, evidence-based focus list for each stand-up

AnalysisMonitoringIT and developmentProduct developmentManagement
See how it worksGet access
Stand-Up Focus Board Prep Agent: what goes in, what the agent does and what you get

What it does

A good stand-up spends its fifteen minutes on work that is stuck, not on everyone listing what they did. Spotting stuck work means checking each ticket's age by hand before the meeting. Each morning this agent reads the sprint board, works out how long every ticket has been in its current column, and compares that with the team's usual cycle time. It lists tickets that are older than normal, have no update since yesterday, or wait on a review or another team. It cross-checks against the impediment log so known blockers are not raised twice. If board data looks wrong, such as a ticket marked done with open subtasks, it adds a short question for the owner. The scrum master decides what to bring up and in what order. Edge case: tickets paused on purpose with a hold label are left off the list.

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
Yes, continueYes, continueApprovedNoNo 1 STARTS WHEN Workday morning, 45 minutes before stand-up 2 USES A TOOL Read the sprint board and ticket history 3 DOES Calculate days in current column for every openticket 4 DOES Compare ages with the team's 85th percentile cycletime per column 5 USES A TOOL Check the impediment log for blockers already raised 6 CHECKS THE RESULT Is each flagged ticket new to the list or changedsince yesterday? If not: drop repeats unless they got older by anotherday without an update. Back to step 4. 7 CHECKS THE RESULT Does the board data look consistent for each flaggedticket? If not: add a question for the owner instead of a flag.Back to step 2. 8 DOES Order the list by sprint goal impact 9 YOU APPROVE Scrum master picks what to raise at stand-up 10 RESULT Focus list posted to the scrum master
Read the steps as a list
  1. Workday morning, 45 minutes before stand-up
  2. Read the sprint board and ticket history
  3. Calculate days in current column for every open ticket
  4. Compare ages with the team's 85th percentile cycle time per column
  5. Check the impediment log for blockers already raised
  6. Is each flagged ticket new to the list or changed since yesterday?If not: drop repeats unless they got older by another day without an update. Back to step 4.
  7. Does the board data look consistent for each flagged ticket?If not: add a question for the owner instead of a flag. Back to step 2.
  8. Order the list by sprint goal impact
  9. Scrum master picks what to raise at stand-upThe agent waits here for your OK.
  10. Focus list posted to the scrum master

How it decides

A ticket goes on the focus list when its age in column is above the team's 85th percentile, it has no update in 24 hours, or it waits on another person.

  • Flag tickets above the 85th percentile age for their column
  • Flag any ticket waiting on review for more than one workday
  • Skip tickets with a hold label
  • Put sprint goal tickets ahead of others

Make it yours

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

  • Age percentile that triggers a flag (default 85th)
  • Hours without update before flagging (default 24)
  • Delivery time before stand-up (default 45 minutes)
  • Labels that exclude a ticket (default hold)

What keeps you in control

It always asks you first

  • Raising a named person's ticket in front of the team

Hard limits

  • Never posts to the team channel on its own
  • Never comments on individual performance

It stops when

  • Done: focus list delivered
  • Stop: no sprint active

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 happensOn Wednesday the agent found 4 tickets over the team's 3-day review threshold. One, a login fix, was already in the impediment log with no change, so it was dropped. Another was marked done with two open subtasks, so it became a question for the owner. The scrum master raised the two remaining tickets first and asked a reviewer to pair after stand-up.

More agents for scrum masters

Analysis · Management

Team Retrospective Follow-through Agent

Retrospective actions judged by outcomes, not activity.

8 steps1 check3 jobs
Quality control · Compliance

Acceptance Criteria Test Mapping Agent

Make sure every accepted story has evidence for each of its acceptance criteria

11 steps1 check2 jobs
Risk management · Monitoring

Roadmap Commitment Risk Watch Agent

Warn early about at-risk commitments with options the owner can act on

11 steps1 check5 jobs
Risk management · Monitoring

Mid-Sprint Goal Health Agent

Spot a failing sprint goal while there is still time to act

11 steps2 checks3 jobs