5 False Hopes of Scrum and How to Fix Them

, Software Pundits
This post was originally published on this site

Toptal

Like many classic, never-ending conflicts, the debate over how development teams should organize and self-govern rages on. Currently, it almost seems as if there are more critics than fans of Scrum. The three most common complaints are:

The process can take center stage over the work. It can be easily confused for micromanagement by another name. The daily stand-up can feel like a meeting where one has to justify its existence.

In other cases, the roles of Scrum are not represented appropriately. Sometimes, the product owner wants too many things inside of a sprint or wants to change priorities mid-sprint—a Scrum master who is obsessively focused on maintaining velocity and adopting every new Scrum ceremony that they learn. After some time with the framework, a common question seems to come up: “Is it us or the methodology?”

The False Hopes of Scrum

While there are numerous dysfunctions like the ones

To read the full article click on the 'post' link at the top.