TL; DR: How to Sabotage A Product Owner — 53 Anti-Patterns from the Trenches to Avoid
One of my favorite exercises from my Professional Scrum Product Owner classes is how to best sabotage a Product Owner as a member of the middle management. The exercise rules are simple: You’re not allowed to use any form of illegal activity. So, outsourcing the task to a bunch of outlaws is out of the question. Instead, you are only allowed to use practices that are culturally acceptable within your organization.
Read on and learn more on how to best sabotage a Product Owner from the exercise results of more than twenty PSPO classes. (I edited the suggestions for better readability.)
TL; DR: The Lack of Agile Leadership Qualities — When Change Agents Don’t Act as Role Models
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. When Scrum becomes an element of an agile transformation, a lack of agile leadership qualities on the incumbents’ side may impede its overall progress significantly despite the best efforts of all other change agents.
📺 Join me and explore the consequences of a lack of agile leadership qualities and what you can do about it in less than three minutes.
Update: Join the LinkedIn Poll: What leadership behavior have you noticed in the past that is impeding an agile transformation?
TL; DR: The Developers Code Fallacy — They Should Talk to Customers, Too, Though
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. The Developers Code Fallacy starts with the idea that Developers are rare and expensive and should focus on creating code. Business analysts or customer care agents can talk to customers instead. However, in practice, it has a diminishing effect on a Scrum team’s productivity and creativity. It is a sign for an organization still profoundly stuck in industrial paradigm thinking.
Join me and explore the reasons and the consequences of this Scrum anti-pattern in 110 seconds.
TL; DR: Three Wide-Spread Product Owner Failures
There are plenty of Product Owner failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone.
Explore with me three widespread examples of how Product Owners fail their team in three short video clips, totaling 6 minutes and 9 seconds.
TL; DR: Product Discovery Anti-Patterns
Scrum has proven to be an effective product delivery framework for all sorts of products. However, Scrum is equally well suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. What product discovery part, you may think now. And this is precisely the point: The Product Owner miraculously identifies what is the best way to proceed as a Scrum Team by managing the Product Backlog. How that is supposed to happen is nowhere described in the Scrum Guide. Consequently, when everyone is for themselves, product discovery anti-patterns emerge.
From sunk costs, HIPPO-ism, my-budget-my-features to self-fulfilling prophecies — learn more about the numerous product discovery anti-patterns that can manifest themselves when you try to fill Scrum’s product discovery void.
TL; DR: How to Make Agile Work in Fast-Growing Startups
For years, I worked in several Berlin-based, fast-growing startups in my capacity as Scrum Master, agile coach, and Product Owner. These are my lessons learned on making ‘agile’ — including Scrum as a framework — work in a fast-growing startup. Also, let me introduce you to the anti-patterns agile startups shall avoid at all costs.