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

Working Agreement Drift Agent

Show the team, with facts, where it has drifted from its own working agreement

AnalysisMonitoringReportingIT and developmentProduct development
See how it worksGet access
Working Agreement Drift Agent: what goes in, what the agent does and what you get

What it does

A team writes its working agreement, then the sprint gets busy. WIP limits creep up, tickets close without tests, and reviews wait days. Raising it without evidence feels like nagging. This agent checks the board and repository each week against each written agreement. It counts how often WIP limits were exceeded, how many tickets closed without the definition-of-done items, and how long reviews waited. It compares the numbers with the last four weeks to see if this is a trend or a one-off. Where drift is clear, it drafts a coaching note with the facts and an open question for the team, not a rule reminder. If the data source for an agreement is missing, it says so rather than guessing. The scrum master decides whether to raise it in a retro or one-to-one. Edge case: an agreement the team changed recently is measured only from the change date.

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 Friday afternoon check 2 USES A TOOL Read the current working agreement and its changedates 3 USES A TOOL Pull board history and pull request data for theweek 4 DOES Measure each agreement: WIP breaches,done-without-tests, review wait time 5 CHECKS THE RESULT Is there data for every agreement item? If not: note the missing source and skip that iteminstead of estimating. Back to step 3. 6 DOES Compare with the last four weeks 7 CHECKS THE RESULT Did the breach happen in two of the last threeweeks? If not: log it as a one-off and keep watching. Back tostep 6. 8 DOES Draft a coaching note with facts and one openquestion per drift 9 YOU APPROVE Scrum master decides how and where to raise it 10 RESULT Weekly drift note for the scrum master
Read the steps as a list
  1. Friday afternoon check
  2. Read the current working agreement and its change dates
  3. Pull board history and pull request data for the week
  4. Measure each agreement: WIP breaches, done-without-tests, review wait time
  5. Is there data for every agreement item?If not: note the missing source and skip that item instead of estimating. Back to step 3.
  6. Compare with the last four weeks
  7. Did the breach happen in two of the last three weeks?If not: log it as a one-off and keep watching. Back to step 6.
  8. Draft a coaching note with facts and one open question per drift
  9. Scrum master decides how and where to raise itThe agent waits here for your OK.
  10. Weekly drift note for the scrum master

How it decides

Drift is flagged when a measure breaks the agreement in two or more of the last three weeks; a single breach is noted but not raised.

  • Raise drift only when it repeats in 2 of the last 3 weeks
  • Measure changed agreements only from their change date
  • Report counts, never names, in the team-facing draft
  • Limit the note to the three biggest drifts

Make it yours

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

  • Weeks of history to compare (default 4)
  • Repeats needed before raising (default 2 of 3 weeks)
  • Agreement items to track (default WIP, definition of done, review wait)
  • Day and time of the check (default Friday 15:00)

What keeps you in control

It always asks you first

  • Sharing the drift note with the team

Hard limits

  • Never names individuals in team-facing drafts
  • Never changes board settings or WIP limits

It stops when

  • Done: note delivered
  • Stop: no written working agreement found

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 happensThe team's WIP limit for In Progress is 5. In week 31 it hit 8 on three days, and in week 30 on two days, so the agent flagged it. Review wait averaged 2.4 days against an agreed 1. Test data was missing for the mobile repo, so it skipped that item. The scrum master used the WIP chart in the retro on 2 August.

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