Scrum-but: The Unofficial Agile Methodology

Level 1: The Promise With Crossed Fingers

A cartoon pirate gets asked, "So, you follow the rules of the game?" and he answers with a big smile: "Well yes... but actually no." It's like a kid who says they cleaned their room — and technically they did push everything under the bed. The room looks clean, the checklist says clean, but anyone who opens the closet knows the truth. The joke is that whole companies do this with their way of working: they wear the costume, say the magic words, and skip the actual cleaning — and everyone quietly knows it, which is exactly why this pirate's half-confession makes developers laugh and wince at the same time.

Level 2: The Ceremonies, Decoded

Scrum is a framework for building software in short cycles. Its main parts, and how they look when the pirate's answer applies:

If you're early in your career and your team's "Scrum" matches the right-hand column, the useful realization is that the framework isn't failing you — it was never actually installed. Knowing the textbook version matters mostly so you can tell the difference, ask good questions in retros (if you have them), and avoid concluding that all process is theater.

Level 3: Scrum-But and the Cargo Cult Fleet

The claymation pirate captain's hedge —

Well yes, but actually no

— is the most honest answer ever given to "So, your team does Scrum?", and the Agile community even has a formal name for it: Scrum-but. As in: "We do Scrum, but we skip retrospectives because there's no time." "We do Scrum, but the standup is where the manager collects status." "We do Scrum, but the sprint backlog changes whenever sales lands a deal." Each individual but sounds like pragmatic tailoring; collectively they amputate exactly the parts of the framework that were supposed to deliver the benefits.

The pattern being satirized is cargo cult Agile — the term borrowed from Feynman's cargo cult science, describing Pacific islanders who built bamboo control towers hoping planes would land. Teams adopt the ceremonies (standups, sprints, story points, a board with swimlanes) while discarding the mechanisms (empowered teams, protected sprint scope, inspect-and-adapt loops). The runway is there; no planes land. The most common terminal form is waterfall in sprints: requirements still arrive fixed from above, deadlines are still set before estimation, and the two-week sprint is just a finer-grained Gantt chart with daily confessionals.

Why does every organization converge here? Incentives, as usual. Real Scrum redistributes power — the team owns the how and the sprint scope, management owns priorities, and estimates are forecasts rather than promises. That redistribution is precisely the part middle management has the least appetite for, so what gets adopted is the vocabulary (which costs nothing and looks great in transformation slide decks) without the authority transfer (which costs everything). Story points get converted back into deadline commitments, the Scrum Master becomes a meeting scheduler, velocity becomes a performance metric to be gamed — and Goodhart's law does the rest. The Agile-industrial complex of certifications and consultants happily sells the ceremony layer, because the ceremony layer is the billable layer.

The pirate is the perfect messenger because his answer isn't a lie — it's a negotiated truth. "Yes" is what the org chart reports upward; "actually no" is what every engineer in the standup knows. The comedy is the gap, and the gap is where burnout lives: teams held to Agile's promises (predictability, sustainable pace) while denied its preconditions.