If you are reading this post, you probably worked following (some form of) Scrum but in case never did: take a seat and be my guest. As for Agile, if you never read its Manifesto (2001), I define it…

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

This post discusses the flaws in the implementation of Scrum and suggests ways to make it work effectively. It emphasizes the importance of flexibility, collaboration, and focusing on results in order to truly embody the Agile philosophy.

Scrum sucks.

<p>Very interesting article!
“Once you set a static metric, people will gradually adapt to go around it.” =&gt; so true! (see <a href="https://en.wikipedia.org/wiki/Goodhart%27s_law" target="_blank" rel="noopener nofollow">Goodhart’s law</a>)
“Way of work should be defined at a team level by its people, not by the company.” =&gt; easy to say, hard to do😬 but i agree.</p>


<p>I might got the article wrong but this „Way of work should be defined at a team level by its people, not by the company” is not a flaw of the scrum framework. This is the problem of people adopting and understanding the scrum in a bad way. Burndown charts, velocity, and story points are not defined by scrum guide at all.
So, The problem described in the article is more about incompetence of people adopting the scrum than the framework it self.
If software development is measured by deadline, time, velocity, and being occupied then no matter which framework will be used, the process will be stressful and devs will find a way to deal with those measures.</p>
