by Stefan Wolpers|Â
Agile and ScrumAgile Transition
TL; DR: My Top Ten Worst Scrum Anti-Patterns
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.
by Stefan Wolpers|Â
Agile and ScrumAgile Transition
TL; DR: Abandoning Scrum
Can a Scrum team simply decide to abandon Scrum? After all, the Scrum team is self-managing, according to the Scrum manual, also known as the Scrum Guide. So, let’s explore this question at the very heart of team autonomy.
by Stefan Wolpers|Â
Agile and ScrumAgile Transition
TL; DR: The Oversized Product Backlog Problem — When Noise Interferes with Signal
There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. Neglecting the critical Scrum artifact for continuous value creation is one of the common Scrum anti-patterns. If your Scrum Team strives to make your customers’ lives easier Sprint after Sprint, beware of the oversized Product Backlog.
📺 Join me and explore the consequences of inadequate Product Backlog management in less than three minutes.
Update: I am running a poll on LinkedIn—join the voting: “What reasons have you observed why Scrum Teams stuff their Product Backlogs — a very costly pattern that diminishes ROI and value creation?”
by Stefan Wolpers|Â
Agile and ScrumAgile Transition
TL; DR: A Sprint Review without Stakeholders
There are plenty of failure possibilities with Scrum. Given that Scrum is a framework with a reasonable yet short “manual,” this effect should not surprise anyone. A Sprint Review without stakeholders may create an unhealthy bubble for the Scrum Team due to the disconnect, thus resulting in lower effectiveness.
Join me and explore the reasons and the consequences of stakeholders avoiding participating in the Sprint Review in less than 150 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.
3rd Party Cookies
This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, and the most popular pages.
Keeping this cookie enabled helps us to improve our website.
Please enable Strictly Necessary Cookies first so that we can save your preferences!