Scrum has to many rules

by Nov 30, 2022

I am starting to hate Scrum.

8 years ago, I started with Scrum, and I was a fan.

It removed friction of writing down everything before implementing and it gave the team way of saying no to too much work.

Now it’s become a project methodology for managers to control the team.

It was supposed to be a set of guidelines to improve communication, focus and creating value.

The idea of all those meetings was to improve communication until people started to do it naturally. When you reach that point, the meetings become useless because everyone is already informed.

Then the artificial time constraints. A deadline every two weeks for whom? Everyone rushing at the end of the sprint, losing quality out of sight, just to have their tasks done.

When the sprint ends, we need to start a new one with as many features as possible to deliver. An endless treadmill where refactoring and experimentation slowly dies.

Scrum is starting to limit teams.

It needs fewer rules.

It should become Kanban.

Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more