TL; DR: 71 Product Owner Interview Questions to Avoid Imposters
If you are looking to fill a position for a Product Owner in your organization, you may find the following 71 interview questions useful to identify the right candidate. They are derived from my fourteen years of practical experience with XP and Scrum, serving both as Product Owner and Scrum Master and interviewing dozens of Product Owner candidates on behalf of my clients.
So far, this Product Owner interview guide has been downloaded more than 8,000 times.
TL; DR: The Frustrated Scrum Master — When all the Effort Leads Nowhere
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. One failure symptom of a botched agile transformation is the frustrated Scrum Master.
📺 Join me and explore the consequences of a Scrum Master who has thrown in the towel in 92 seconds.
TL; DR: Scrum Failure Culture: A Requirement to Be Successful
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. To make things worse, a crucial success factor of every Scrum team is not even mentioned in the Scrum Guide: Any organization that wants to employ Scrum to learn faster than its competitors needs to have a solid failure culture.
📺 Join me and explore the consequences of not living a failure culture in less than three minutes.
TL; DR: Success Metrics, Maker-User-Gap—Food for Agile Thought #293
Welcome to the 293rd edition of the Food for Agile Thought newsletter, shared with 31,307 peers. This week, we delve into why picking success metrics is so challenging yet critical, and Henrik Kniberg shares some vital insights after years of working with Spotify, LEGO, and Minecraft development. Also, we point at how sociotechnical architecture and systems thinking are key to enabling product thinking in organizations.
We then share an eight-step strategy workshop; we understand why ‘going deep’ is Stripe’s core product principle, and we wonder why some product managers hold on to timeline-based planning while product roadmaps have evolved so rapidly in recent years.
Lastly, we analyze the idea of ‘autonomy’ in the workplace, particularly regarding two challenges: the air sandwich and politics.
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 Stakeholder Failures
There are plenty of Scrum stakeholder failures. Given that Scrum is a framework with a precise and concise yet short “manual,” this effect should not surprise anyone. While the Scrum Guide makes numerous references to stakeholders in Scrum, stakeholders themselves are no official role (accountability), no matter their crucial contribution to a Scrum team’s overall success.
Explore with me three widespread examples of how stakeholders fail their Scrum teams in three short video clips, totaling 6 minutes and 5 seconds.