Should a scrum master become a product owner?


Scrum Guide

Scrum Accountabilities

  1. developers → the people doing the work, delivering a high-quality done increment.

So what’s the problem?

Let’s go through all possible combinations

Exploring the Scrum Master Role

  1. observing through listening, sensing, smelling, whatever senses they’ve got available;

  2. mentoring, giving advice, coaching, maybe asking Socratic questions teaching, coaching, mentoring, with permission. Don’t inflict help on people;

  3. acting as a change agent;

  4. keeping an eye on the scrum implementation;

  5. working with the rest of the organization to help them to understand how scrum and agility works; and

  6. removing impediments that are beyond the control and influence of the team.

Exploring the Product Owner Role

  1. The product owner really should be doing a lot of work in product management;

  2. Product ownership;

  3. Commercial pricing;

  4. Looking at customer analytics;

  5. Visiting customers; and

  6. Managing the expectations of stakeholders, and connecting with them. Managing their expectations in terms of uncertainty. Setting their expectations that we don’t know when we will be done. We’re committing sprint by sprint. We’re using an iterative, incremental approach. We’re trying to work empirically here.

Why shouldn’t scrum masters be product owners?

By John Coleman

Keywords: Agile, Business Strategy, Change Management

Share this article