SCRUM-Fall

Almost everyone knows the Scrum Ceremonies and roles by heart. On top of that, there are more than a million Scrum-certified professionals; 684K+ from Scrum.org and 400K+ from Scrum Alliance.

With such an abundance of certified people worldwide, Scrum is an obvious choice.

SCRUM It’s often the first choice of companies when they want to work with agile frameworks.

Still, most companies out there “claiming” that they do SCRUM are following what I call SCRUMFall.

SCRUMFall Patterns

Product Managers define the right thing to do, and Product Owners ensure the item is done right.

Product Managers define what to do, UX research, UI designs, and Devs code. Developers aren’t involved in any discovery step; They focus only on execution.

Scrum teams focus on implementation and nothing else. Developers long for well-defined requirements and high-fidelity prototypes.

As in a factory, everyone handles a small part of the product, and nobody cares about the whole.

Agility implies collaboration

Instead of improving collaboration and benefiting from Scrum, teams fall back to a waterfall working mode.

Unlike assembly lines, software development is unpredictable, and investing too much time upfront on a plan will generate waste. The time to market is extensive, and end-user learning takes too long.

Scrum is all about empiricism and collaboration. It will only work well once teams can embrace uncertainty and are empowered.