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 Metrics Report Agent

Accurate sprint metrics with clear notes on scope changes

ReportingIT and developmentProduct development
See how it worksGet access
Sprint Metrics Report Agent: what goes in, what the agent does and what you get

What it does

At the end of each sprint the Scrum Master shares velocity, completed versus committed work, cycle time and carry-over, but bad tracker data makes the numbers wrong. This agent pulls sprint items, estimates and status history, then looks for common errors such as stories without estimates or items closed after the sprint ended. If the data is not clean, it lists the errors for owners to fix and pulls again. Only then does it compute the metrics. Scope added after day 2 is shown separately. If sprint length changed, velocity is normalized per working day before comparing. It builds charts and writes a short plain summary for the team and a separate one for managers. Metrics describe the team and are never ranked by person. The Scrum Master approves both summaries before sharing. Edge case: a story split mid-sprint is counted once, not twice.

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, continueApprovedNo 1 STARTS WHEN Sprint ends 2 USES A TOOL Pull sprint items, estimates and status history 3 DOES Find data errors such as missing estimates or lateclosures 4 CHECKS THE RESULT Is the data clean? If not: list errors for owners to correct and pullagain. Back to step 2. 5 DOES Compute velocity, cycle time, carry-over and scopechange 6 DOES Draft team and manager summaries 7 YOU APPROVE Scrum Master approves before sharing 8 RESULT Sprint metrics report
Read the steps as a list
  1. Sprint ends
  2. Pull sprint items, estimates and status history
  3. Find data errors such as missing estimates or late closures
  4. Is the data clean?If not: list errors for owners to correct and pull again. Back to step 2.
  5. Compute velocity, cycle time, carry-over and scope change
  6. Draft team and manager summaries
  7. Scrum Master approves before sharingThe agent waits here for your OK.
  8. Sprint metrics report

How it decides

It flags data errors before computing metrics and only compares velocity between sprints of equal length unless normalized.

  • Scope added after day 2 is shown separately
  • Velocity is normalized when sprint length differs
  • Metrics are about the team, never ranked by person

Make it yours

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

  • Metrics shown
  • Audiences for summaries
  • Scope change cutoff day (default day 2)
  • Chart style

What keeps you in control

It always asks you first

  • Sharing the report

Hard limits

  • Never shows individual performance rankings
  • Never edits tracker items itself

It stops when

  • Done: approved report shared
  • Stop: data still incomplete after one day, report with marked gaps

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 happensSprint 18 ended on July 11. The first pull showed 6 stories without estimates and 2 closed on July 12, so the clean data check failed. The agent sent the list to owners, who fixed it that afternoon, and pulled again. Corrected velocity was 29 points instead of 23. The summary noted 8 points of scope added on day 4. The Scrum Master approved both summaries.

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