# I Hired a Scrum Master AI

**Author:** Alexey Krivitsky
**Date:** 2026-03-21
**Reading time:** 1 min
**Category:** Org Design
**Tags:** ai, scrum, agents, team-coaching
**Canonical:** https://krivitsky.com/post/hired-a-scrum-master-ai

---

**TL;DR:** An AI agent now coaches my team by reading session memories and surfacing recurring dysfunctions — approval gate violations, destructive ops without confirmation, plan-mode confusion. It catches patterns across sessions that humans forget. The role works because it observes relentlessly and never tires of pointing out drift.

I have just hired a Scrum Master! 

In the interview, I asked:
What other issues have you observed in my recent sessions? 

Then she replied without hesitation:
Here are the recurring issues I can see from the memories + today's session:
Issues observed

And she continued with a great level of detail:

 1. Approval gate violation (repeated offense) — Memory says "NEVER jump to implementation without approval." Has its own memory file.
 Still happened 3+ times today. The memory/CLAUDE.md approach isn't working — needs a structural fix, not another reminder.

 2. Destructive data operations without confirmation — Cache version bump wiped 3.6MB of WA history. No warning, no backup, no confirmation
 asked. This pattern (making irreversible changes silently) is the most dangerous.

 3. Plan mode confusion — Plan mode's auto-"approved" message gets treated as user approval. This has happened before (it's explicitly in
 the memory file) and happened again today.

 4. Spec/plan location drift — Specs kept ending up in plan files instead of /specs. User had to say "MAKE A SPEC" and "follow OUR
 WORKFLOW." The memory file for this exists too.

 5. Testing against live resources — Previous incident with git e2e tests against working repo. Today: cache flush overwrote real data
 file. Pattern: not isolating test/dev operations from production data.

 6. Over-eagerness / not listening — When user says "stop", I often do one more thing before stopping. When user asks a question, I
 sometimes start implementing instead of just answering.

-----

That's awesome, I said. You are hired! 

Welcome to the team of:
- product manager (me, for now)
- expert UX researcher + user interviewer
- elite BDD (Behavior-Driven Development) specialist
- and a good coder (Opus 4.6)