Spent 25 years in banking tech watching teams drown in Agile ceremonies. Building the content I wish existed back then. Sometimes the problem IS the framework.
@allenholub 25 years in banking systems, same pattern everywhere. teams with the best estimates got rewarded with more estimation meetings. teams that shipped something visible every week got left alone. nobody asks for story points after a demo.
Googled "is scrum master certification worth it." Every top result says yes — and every one is written by someone who sells it. That's not an answer, it's a funnel. A cert is a receipt, not a skill. Follow the money.
@allenholub Agreed — and the reason the standardized process wins anyway isn't efficacy. It's that it's sellable. $295/yr renewals, 20+ cert tracks, ~2M certified, ~$300M of PE behind it. Nobody buys SAFe because it ships software. They buy it because it's defensible in a board deck.
I once nearly got put on a performance plan for suggesting we cut a meeting that everyone privately agreed was useless. Three months later I showed the same manager a spreadsheet. Hours per meeting. Decisions made per meeting. He looked at it and said we should probably fix this.
20 years building banking systems taught me this:
Teams that ship have an architect who can say no, a manager who acts as a shield, and 6 people, not 60.
None of this requires a certification.
Take the 90-second diagnostic: https://t.co/jFTDmeRsci
The inventor of Scrum told me 65% of teams fail, his diagnosis: they're doing it wrong. At what point does a 65% failure rate stop being an implementation problem and start being a design problem?
Asked the CEO of PMI what his new manifesto offers that the previous ones didn't. He accused me of self-promotion and removed my comment. I have 5 followers and linked to nothing. The Agile industrial complex can't handle questions about its own data.
https://t.co/DBjMEhtjGS
The consulting firm's incentive is not to solve your problem. It's to extend the engagement. Every CTO knows this. They hire them anyway, because nobody gets fired for hiring IBM.
Most companies don't need a digital transformation. They need a CTO who understands the stack well enough to stop outsourcing technical judgment to consultants billing $350/hr. Wrote about why this never changes.
https://t.co/nql9vbJb8B
An executive once told me why companies keep hiring consulting firms that deliver mediocre work: "Nobody gets fired for hiring IBM. I hired the best. If they couldn't do it, nobody could." Digital transformation isn't a technology strategy. It's a career protection strategy.
The Scrum Master certification takes 2 days. A senior engineer takes 10 years to build. They earn the same salary. Explain how that makes sense.
https://t.co/oMbtiBhfiW
The Scrum Alliance has certified over 1.4 million Scrum Masters at $1,000 each. That's a $1.4 billion industry built on one premise: you can manage software engineers without understanding software engineering. Wrote the full breakdown.
2 days. $1,000. 95% pass rate. Now you manage engineers who've been shipping production systems for 15 years. You've never deployed anything. But you're certified. That's the Scrum Master pipeline.
Wrote about why most retros are memory rituals, not improvement tools. Teams keep documenting the same problems every two weeks and calling it Agile.
→ https://t.co/cNLJQ0i3Oy
Your retro action items from January are the same as July. The wording changes. The problem doesn't. That's not continuous improvement. That's continuous documentation.
@saen_dev Perfect example, every box checked, system still went down. Because checklists measure compliance, not understanding. DoD was never about quality it's about having something to point at when things break. We followed the process is the most expensive sentence in engineering.
When production breaks at 3am the postmortem asks "was the DoD followed?"
Answer is always yes. Every box checked.
The DoD didn't prevent the incident, it prevented the blame.
Why nobody fixes it:
Real DoD = fewer stories per sprint = lower velocity = conversation with management nobody wants to have.
So the DoD stays loose. Numbers stay high. Risk relocates to production.