Document II. The frAGILE Playbook For internal circulation Field Manual · 12 cases · 4 verdicts
A field manual

The Playbook

Field notes from ceremonies that solved nothing, filed under names that should not have been printed.

Index of Known Incidents

Each case file: the line you’ve heard in the room → what’s actually happening → what to do instead.

Chapter I.

Ceremonies

Four rituals investigated. No blockers reported. Everything blocked.

Case No. 001
Recurring

The Sprint That Planned Itself

Subject

Sprint Planning

Symptom

“We’ll figure out scope during the sprint.”

Diagnosis

Jira/ADO filled with vague hopes and drams and duplicate epics. Nobody names the outcome.

Recommendation

Start with outcomes, not tickets. If nobody can state the goal, do not start the sprint.

Filed by The Cult of Clarity Sprint ∞
Case No. 002
Unresolved

The Standup That Said Nothing

Subject

Daily Standup

Symptom

“Yesterday I... Today I... No blockers.”

Diagnosis

Rote status ritual with no real signal. Team performs updates for the room, not the work.

Recommendation

Ask: “What would unblock the team today?” Then let people leave.

Filed by The Cult of Clarity Daily @ 9:00
Case No. 003
Standing

The Retro That Solved Nothing

Subject

Sprint Retrospective

Symptom

Complaints aired. Post-its written. Nothing changes by next sprint.

Diagnosis

Venting mistaken for progress. No owner assigned to any action.

Recommendation

Turn one vent into one action item every sprint. Name the owner before the meeting ends.

Filed by The Cult of Clarity End of Sprint
Case No. 004
In Regression

The Demo of a Thing That Doesn’t Exist Yet

Subject

Sprint Demo

Symptom

“Please imagine this is clickable.”

Diagnosis

PowerPoint pixels shown in place of shipped work. Team performs delivery.

Recommendation

Show real value or say the truth. “We did not ship this sprint” is a valid demo.

Filed by The Cult of Clarity Fortnightly
Chapter II.

Roles & Personas

Four archetypes at large. Suspected of Agile theater in varying degrees.

Case No. 005
Confidential

The Voice That Forgot to Listen

Subject

Product Owner

Alias

“Voice of the customer.”

Diagnosis

Speaks for customers. Has not spoken to customers in six sprints.

Recommendation

Schedule the customer call. Bring transcripts. Stop paraphrasing.

Filed by The Cult of Clarity Ongoing
Case No. 006
Suspected

The Master Who Forgot the Purpose

Subject

Scrum Grandmaster (the Scrum Master who’s been doing this so long, the ritual outranks the role)

Alias

“Keeper of the ceremony.”

Diagnosis

Enforces every ritual. Cannot explain why any of them exist.

Recommendation

Ask what each ceremony is for. If the answer is “the framework,” cancel it.

Filed by The Cult of Clarity Recurring
Case No. 007
Open

The Lead Who Only Measured Delivery

Subject

Delivery Lead

Reputation

“The one who gets things shipped.”

Diagnosis

Measures success only by shipping. Value shipped is not measured at all.

Recommendation

Add one outcome metric per initiative. Ship becomes shipped-and-used.

Filed by The Cult of Clarity Q4
Case No. 008
Witnessed

The Stakeholder Who Joined Sprint Six

Subject

Stakeholder X

Alias

“I have a small change.”

Diagnosis

Missed every discovery session. Reappears in sprint six. The "small change" touches four epics.

Recommendation

Publish the decision log. Late input is welcome; late overrides are not.

Filed by The Cult of Clarity Sprint 6
Chapter III.

Tools & Templates

Four artifacts recovered from the scene. All still in circulation.

Case No. 009
Preserved

The Poster That Time Forgot

Subject

Definition of Done

Condition

Laminated. Last revised: pre-pandemic.

Diagnosis

Written when the team was different. Referenced by no one. Enforced by silence.

Recommendation

Rewrite it in the next retro. Anything you do not defend, you should not display.

Filed by The Cult of Clarity Wall, third floor
Case No. 010
Neglected

The Chart Nobody Read

Subject

Burndown Chart

Condition

Exists. Only reviewed when things go wrong.

Flatlined burndown chart An ideal burndown line falls toward zero while the actual burndown line stays almost flat. DAY 1 DAY 10 STILL FINE
Diagnosis

Compliance artifact. Signal after the fact.

Recommendation

Delete it or use it. If you would stop reading it tomorrow and nothing would change, that is your answer.

Filed by The Cult of Clarity Auto-generated
Case No. 011
Misapplied

The Score That Was Not a Score

Subject

Velocity Metrics

Condition

Used to compare team happiness. Incorrectly.

Diagnosis

Planning signal treated as performance metric. Teams inflate points to keep the number steady.

Recommendation

Use velocity for planning only. Never in a performance review. Ever.

Filed by The Cult of Clarity Dashboard, TV lobby
Case No. 012
In Progress

The Board That Never Moved

Subject

Agile Board

Condition

78% of tickets in “In Progress” or “Blocked” purgatory.

Diagnosis

Board does not reflect the actual work. Standups happen anyway.

Recommendation

Jira/ADO boars are not the sources of truth we wish they were. That is not real life. People are. Talk to the humans before you touch the board.

Filed by The Cult of Clarity All quarters
Chapter IV. Findings

The Verdict.

Twelve cases reviewed. Four truths recovered. Filed under the only category that matters.

01

The ceremony is never the cure. It is only a container. If nobody brings truth into the room, the ritual will politely preserve the lie.

02

A metric becomes theater the moment it is used to avoid judgment. Measure to learn. Not to decorate the dashboard.

03

You do not need more process. You need more courage. Courage to speak clearly, say no, and show up human.

04

If you are never laughing, you are not doing it right. Satire is a signal. It means we care enough to notice.

Chapter V. Close of File

Twelve cases.
One standard.

The Playbook does not exist to make Agile prettier. It exists to help teams name the pattern before the pattern becomes culture.

Acknowledge Receipt

Legal status: ceremonial. Emotional accuracy: unfortunately high.