No other role in Scrum can contribute to mediocre outcomes like the Product Owner—garbage in, garbage out. Therefore, the following list of some of the most common Product Owner anti-patterns might be a starting point to reflect on the role; maybe, there is room for improvement?
If you recognize some anti-patterns in your daily work, why don’t you ask the rest of the Scrum Team for support? For example, run a Retrospective with teammates and stakeholders on how the team is doing regarding figuring out what is worth building.
The reasons Scrum Masters violate the spirit of the Scrum Guide are multi-faceted. Typical Scrum Master anti-patterns run from ill-suited personal traits to complacency to pursuing individual agendas to frustration with the team itself.
Read on and learn in this post on Scrum anti-patterns how you can identify if your Scrum Master needs support from the team.
In my experience, the Daily Scrum is the Scrum event with the highest anti-pattern density among all events. Learn more about Daily Scrum anti-patterns that threaten your Scrum team’s success, from becoming a reporting session to assignments to answering these three questions.
TL; DR: The SAFe ® NPS ® Score as a Scaling Framework Is -56
SAFe® has always been a controversial topic within the agile community. Therefore, back in 2017, I ran a first survey on the Net Promoter Score® of the Scaled Agile Framework SAFe®. The result back then was -52. Four and a half years later, I reran the poll: SAFe® has been through several iterations, and many more agile practitioners have experienced working with it. However, the question still is: Would you recommend SAFe ®?
Executive Summary: SAFe®’s NPS® score based on the 2022 sample equals -56. (For details, see the data below.)
I recently was invited to a Scrum.org Webinar, and I picked a topic close to my heart: the worst Scrum anti-patterns. So, without further delay, here are my top ten of the meanest, baddest Scrum anti-patterns I have experienced.
There are plenty of failure possibilities with Scrum. Since Scrum is an intentionally incomplete framework with a reasonable yet short “manual,” this effect should not surprise anyone. For example, how do we communicate with members of the Scrum team that take the Scrum Guide literally? What about a dogmatic Scrum Master?
Join me and delve into the effects of Scrum dogmatism in less than 120 seconds.
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Strictly Necessary Cookies
Strictly Necessary Cookie should be enabled at all times so that we can save your preferences for cookie settings.
