How to Sabotage A Product Owner
Stefan Wolpers
?? I help Product Owners, Product Managers, Scrum Masters & Agile Coaches Grow w/ Classes, Courses, Books & Community. ?? Author of the ”Scrum Anti-Patterns Guide;” ??Trainer at Scrum.org; ?? Book a 1-on-1; talk chances!
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.)
???? Hier geht es zur deutschsprachigen Version:?Product Owner Sabotage — 53 Beispiele aus der Praxis.
???Shall I notify you about articles like this one? Awesome! You can?sign up here for the ‘Food for Agile Thought’ newsletter and join 34,000-plus subscribers.
?? Join Stefan in one of his?upcoming Professional Scrum training classes!
???? Zur deutschsprachigen Version:?Scrum Master Gehalt 2022 — die Umfrageergebnisse.
The Exercise: Consider How to Best Sabotage A Product Owner
The exercise is based on a Liberating Structure microstructure called?TRIZ.
Here is the briefing for the participants; typically, they have a five-minute timebox to come up with suggestions and observations in a workgroup of three to five people.
Once we accomplish the first part of the exercise — aggregating sabotaging practices — the workgroup then identifies those practices to sabotage Product Owners they have already witnessed, followed by identifying possible ways to counter these practices.
I categorized the results from the before-mentioned classes into eight groups:
1. Messing with the Scrum Framework in General
The first category of how to best sabotage a Product Owner is generally about disqualifying Scrum itself as a helpful framework or introducing changes to conflict with the first principles of Scrum:
2. Scrum Team Building & Line Management
If the direct approach does not yield the expected results, why not use the backdoor and help make the Scrum team as dysfunctional as possible? Some suggestions worth considering are:
3. Flow of Information
If you are already messing with the Scrum Team team-building process, why not place a few obstacles into the Scrum Team’s way of working? Sabotage your Product Owner by keeping them in the dark while holding them accountable for not being up-to-date:
4. Metrics & Reporting
The next bucket of useful sabotage practices are metrics, OKRs, KPIs —?you name it. Just turn the members of your Scrum team into glorified data-entry clerks with a challenging reporting burden:
5. Vision, Product Discovery & Product Backlog Management
All sabotage is—at least partly—based on deception. Therefore, obfuscate whatever might help the Product Owner to get an understanding of what strategic direction they are supposed to support with their Scrum team:
6. Messing w/ the Sprint, Increment, or Release
Does the Product Owner still lead the Scrum team towards creating Increments? Time for some rearguard action by introducing new approval stages and security measures—for the sake of your customers, of course:
7. Politics
Use your career equity, the network you have been building for years, to your advantage. Maybe, it is time to call in some favors:
8. Budget
If everything fails, don’t waste time reading the Scrum Guide. Instead, use the budgeting process to your advantage:?
How to Sabotage A Product Owner — Conclusion
Every middle manager has ample opportunity to sabotage Product Owners. Moreover, most of the time, it will be unlikely that others will identify these practices as deliberate obstruction. Providing the benefit of the doubt and assuming positive intent, they probably get away with it. Therefore, reading these signals early in the process is vital to us agile practitioners.?
Please keep in mind: not everyone will be excited when the organization succeeds in becoming a learning organization. Self-management and shifting decision-making to those closest to the problems will likely flatten the hierarchy, reducing the need for managers. Typically, scaling “agility” equals “descaling the organization.”
What practices to sabotage Product Owners have you observed? Please share your learnings with us in the comments.
?? Resources
The following resources may support your efforts to avoid to sabotage a Product Owner in your organization:
?? Training Classes, Meetups & Events 2022
Upcoming classes and events:
?? Join 3,500-plus Agile Peers on Youtube
Now available on the Age-of-Product Youtube channel:
? Do Not Miss Out: Join the 11,000-plus Strong ‘Hands-on Agile’ Slack Community
I invite you to join the?“Hands-on Agile” Slack Community?and enjoy the benefits of a fast-growing, vibrant community of agile practitioners from around the world.
If you like to join all you have to do now is provide your credentials via this Google form, and I will sign you up. By the way,?it’s free.
?? Do You Want to Read more like this?
Well, then:
How to Sabotage A Product Owner — 53 Anti-Patterns from the Trenches was first published on Age-of-Product.com.
Software solutions, data engineering.
3 个月Thank you for this excellent article, Stefan! It’s a concise yet impactful guide that highlights key areas where Product Owners can improve. Looking forward to more insights from you!