Can a Scrum Master be a Product Owner?

Today a colleague asked me “Can the Scrum Master and Product Owner role be filled by one person?”.  My initial reaction was a resounding NO.  However, as we talked it over it seemed like it could be possible, assuming the right person was available to fill that role.  Let’s take a look at what each role is responsible for:

Scrum Master (via Mountain Goat):

The Scrum Master is responsible for making sure a Scrum team lives by the values and practices of Scrum. The Scrum Master protects the team by making sure they do not overcommit themselves to what they can achieve during a sprint.

The Scrum Master facilitates the Daily Scrum Meeting and becomes responsible for removing any obstacles that are brought up by the team during those meetings.

The Scrum Master role is typically filled by a Project Manager or a Technical Team Leader

Product Owner (via Mountain Goat):

The Product Owner (typically someone from a Marketing role or a key user in internal development) prioritizes the Product Backlog.

The Scrum Team looks at the prioritized Product Backlog and slices off the top priority items and commits to completing them during a Sprint. These items become the Sprint Backlog.

In return for their commitment to completing the selected tasks (which, by definition, are the most important to the Product Owner), the Product Owner commits that he or she will not throw new requirements (Sprint Backlog items) at the team during the sprint. Requirements are allowed to change (and change is encouraged) but only outside the sprint. Once the team starts on a sprint it remains maniacally focused on the goal of that sprint.

Ok, so the Scrum Master is responsible for:

  • Ensuring the team lives by values and practices of Scrum
  • Protects the team by making sure they don’t overcommit
  • Facilitates the daily scrum
  • Is responsible for removing any obstacles that come out of the daily scrum

And the Product Owner is responsible for:

  • Prioritizing the product backlog
  • Commits to not throw new requirements at the team during a sprint

Assuming a single person is able to fill both of these roles by not mixing and matching it seems feasible that they could be done by a single person if absolutely required.  Ideally I would still keep the roles separate since I think it’s difficult to find someone who is able to fill both roles.  The Scrum Master should be focusing on the current sprint, with some visibility into what may come in future sprints, while the product owner should always be looking at the product backlog and continuously evaluating what is the highest priority.  Since the Scrum Master has a lot of insight into the development cycle and has close interactions with the Sprint Team it may be difficult for the Scrum Master to switch hats and objectively evaluate what features from the backlog are the highest priority. 

What do you think, can a single person fill the role of Product Owner AND Scrum Master?

# re: Can a Scrum Master be a Product Owner?

Wednesday, June 22, 2005 6:01 PM by Darrell    
I'd say probably not because it would be hard for one person to argue for adding a feature and then deny themselves that feature. :)

If 1 person had to play multiple roles, I would think the separation of business and developer would be the most important to make.

# re: Can a Scrum Master be a Product Owner?

Monday, June 27, 2005 9:17 AM by Steve    
Yeah, the more I think about this one the more I think it really is best to make the roles seperate. It's tough at my current gig becuase we usually don't have a "real" product owner available so someone on our team has to support the role. It just so happens that the person who would be supporting that role is the Scrum Master.

# re: Can a Scrum Master be a Product Owner?

Thursday, August 17, 2006 1:22 AM by Alexander Kriegisch (CSM)    
First I thought: absolutely so, because I have kind of done that before. But having reflected on this some more, I am convinced that this is a fallback solution that should be avoided by all means. And here is why:

Having led a major software project involving multiple operative and technical departments, four sub-projects and quite a few people as an external consultant to an insurance company lately, I remember that even though I was the only external person working on the project and acted like the impartial consultant not being part of any of those rival departments I really felt I was, the team's perception of me was different at the beginning: On one hand they wanted to trust me because I was not the usual operating officer leading the project and showing them my commitment to driving the project forward and removing obstacles, but on the other hand they felt they should not, just because I was the operating department's proxy and responsible for the product backlog, thus effectively playing both roles: Scrum Master and Product Owner.

This clearly was a conflict of interests, and I had a hard time convincing everybody that this Janus-faced guy who acted as a facilitator once and as somebody demanding requirements being cast into features another time was trustworthy. Neither was that guy on their side exclusively, nor was he on "the others'".

Finally, all's well that ends well, because they trusted me after a while, and I managed to get there without losing the operating department's trust. BUT - but it took a few weeks and was like dancing on a wire sometimes. We definitely lost time at the beginning, because people only become committed to your cause if they trust you. Oh, and by the way: Both being a Scrum Master or a product owner are full-time jobs if done properly. So I am sure I could have performed better as either one of them, if I would not have been required to impersonate both roles.

# re: Can a Scrum Master be a Product Owner?

Wednesday, February 27, 2008 6:32 PM by Shawn    
Can you use scrum on a project of 1? 2? 3? If not, what is your minimum number? I argue that on a 1 pizza team project you will self-organize and self-manage with many people playing multiple roles. As your project and team size increases, you can afford and need the specialization. There is no magic number at which you have both a Scrum Master and a Product Owner, but if you value people over process, you will find your way grasshopper.

Post a Comment

 
 
Prove you're not a spammer: 
3 + 3 =