A survival resource for software engineers trapped in the ceremony. The Scrum Master has a certification. You have deadlines. Somewhere in that gap is a shipping problem.
Everything you need to understand, survive, or argue your way out of the ceremony.
An honest accounting of every ritual — how long it actually takes, what it costs, and what you could have shipped instead.
Why story points exist, who they serve, and why the number always comes out wrong.
The role, the certification economy, and what happens when facilitation is mistaken for leadership.
What teams that consistently ship actually do differently — and how little of it involves Agile.
How a ticket system became the point of the work instead of a tool for the work.
How to make the case for a saner process — with data, with tact, and without getting labeled "not a team player."
Three questions, thirty minutes. One person talking while everyone else waits to leave. The standup was designed to last fifteen minutes. Here's why it doesn't, and why that's a symptom of a bigger problem than meeting length.
Read the full piece →What the words actually mean in practice. For engineers who just sat through their first planning session and need a translator.
View the full dictionary — 47 terms defined honestly →
Data is harder to argue with than feelings. Use these to make the case.
No ceremonies. No fluff. One email a week with the best writing on software engineering, team structure, and how to actually ship.
One email/week. No selling your data. Unsubscribe instantly. No ceremony to leave.
PostScrum exists because the same conversation happens in every engineering org, every few years, with every new leadership team that discovers Agile and decides to scale it. The engineers who lived through it know why it doesn't work. The people running the ceremonies don't read engineering blogs.
This site is the resource we wish existed when we were sitting in our first four-hour planning session wondering who decided this was a good use of time. It's criticism backed by data, arguments backed by evidence, and parody that only works because it's accurate.
No Scrum Masters were harmed in the making of this site. Several were mildly inconvenienced.