agile

The Right Answer Nobody Ordered

Responding to Change Over Following a Plan (The Plan Was to Follow the Plan)

A Fish That Was Technically a Boat

The Person Who Herds the Cat Herders

A Document Renamed to Sound Archaeological

An Infinite List of Things Nobody Will Build

Grooming, But We Don't Call It That Anymore

The Room That Worked Best When It Was Empty

The Chart That Burns Sideways

A Meeting That Became Sacred by Being Renamed

A Status Meeting Performed Vertically

A Checklist Redefined Every Time Someone Ships Something That Wasn't

The Book That Distinguished "Doing Agile" From "Being Agile" and Was Punished for Its Clarity

A Project, But We Can't Call It That

The Meeting That Hasn't Happened Yet

The Word So Unfortunate They Had to Rename It

The Board That Replaced the Process, Then Became the Process

The Philosophy That Worked Until It Became a Brand

Minimum Viable Product, Maximum Viable Excuse

The Same Meeting, in a Castle

Three Days of Training to Conflict with Three People on the Org Chart

The Gatekeeper Who Decides Whether Software Happens

Group Therapy With Sticky Notes

Scaled Agile Framework, or The Enterprise Strikes Back

A Framework for Meetings About Work Instead of Work

A Servant Leader Who Serves Primarily the Scrum Guide

Research Disguised as a Ticket So It Fits on the Board

Two Weeks to Do What Takes Three, Reported as One

Planning the Plan to Plan

The Unit of Measurement That Measures Nothing

A Novel About Throughput That Became the Throughput of Novels

Build-Measure-Learn (Emphasis on Build, Skip Measure, Forget Learn)

s/factory/IT department/g

Squads, Tribes, and Guilds for Twelve People

s/Brent/developer experience/g

As a Reader, I Want a Shorter Article, So That I Can Get Back to Work

The Rule Everyone Sets and Nobody Follows

The Five-Week Sprint and Other Contradictions in Terms

The Methodology That Works Perfectly as Long as You Know Everything in Advance