The thing that never worked — while it worked perfectly
Disclaimer: I’m not a certified Scrum Master, Practitioner, Coach, or whatever title comes next. I’m just a software engineer who’s been fortunate enough to work at multiple companies, each with its own “flavor” of Scrum*.
I’ve always had mixed feelings about Scrum. Some things worked, some didn’t, and some only worked part of the time. Lately, though, I see more and more criticism framing Scrum as something that actively blocks progress. Much like “Scrum everywhere” ten years ago—only in reverse.
That’s not necessarily bad. There is no progress without challenging old ideas. But before going fully Scrum-free, it’s worth asking: do we really understand what we’re giving up?
Think about the estimation process.
Estimates have a terrible reputation, and for good reason. They never really answered the questions management cared about:
- When will this feature ship?
- Can the team squeeze in more work?
In that sense, estimation failed.
And yet, at the same time, it did something incredibly valuable.
Planning poker slowed us down. In fast-paced planning sessions, it created a deliberate pause—a precious moment to check whether we actually understood what we were about to build. It was the time to say: I don’t know what we’re doing or I think we’re solving the wrong problem.
Everyone was heard, and most importantly, every voice carried the same weight.
I remember being a junior, afraid of being judged by other team members while trying to keep up with everything happening around me. That single “?” card was my weapon. It was a safe signal. A permission slip to ask questions without justification.
So the real value of estimation was never about predicting delivery dates or measuring task complexity. It was about creating a shared, familiar environment where people felt allowed to speak up. It worked—not because Scrum was perfect, but because its rituals reduced ambiguity. Even when you changed companies, the practice stayed the same, and you always knew how to participate.
So before joining the next “Scrum is bad” demonstration, it’s worth asking:
If we remove the ritual, how do we preserve the space it created?
If you have no answer, there is always the “?” card you can use.
* 30-person circle stand-ups and effort measured in bananas included