Shades of Scrum: 3 Product Owners and a Product Owner Shaped Object

December 9, 2012 at 6:24 pm 8 comments


The Scrum Guide by Ken Schwaber and Jeff Sutherland states about the Product Owner role:

The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.
The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes:

  • Clearly expressing Product Backlog items;
  • Ordering the items in the Product Backlog to best achieve goals and missions;
  • Ensuring the value of the work the Development Team performs;
  • Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
  • Ensuring the Development Team understands items in the Product Backlog to the level needed.

Product Owner Personas

I have seen four different types of Product Owners. I have created little personas to describe them: Walter, Marty, Eric and Jeff.

Walter

Walter is very accurate when preparing the next Sprint. He knows the domain very well and doesn’t need the support of the team for Sprint preparation. He only calls the developers for Sprint preparation when he needs an estimate for a newly created Product Backlog Item. In the Sprint Planning Walter hands over very clear and detailed specifications of what has to be done in the Sprint.

Walters Product Backlog Items are described very carefully and have a detailed list of acceptance criteria. Therefore there is no need for intense contact with the development team during the Sprint.

Marty

Marty asks the development team regularly for help during Sprint preparation. He writes some of the Product Backlog Items together with the development team and often details Product Backlog Items and their acceptance criteria together with the team.

Marty is available during the Sprint to clarify details that are not described by the Product Backlog Items.

Eric

Eric does not only work as a Product Owner; he is also a member of the development team. He creates and manages the whole Product Backlog together with the development team. When the Sprints begins, the Product Backlog Items are often very rough and a lot of stuff is detailed and clarified during the Sprint.

Jeff

Jeff has some distance to the development team. Normally he interacts with the development team only during Sprint Planning and Review. His Product Backlog Items are coarse grained leaving out most of the details. The development team has to figure out the details itself. Jeff may provide a Product Backlog Item “Birthday list” and the team has to figure out the filter criteria, printed data and layout.

Conclusion

In my point of view three of the described Product Owner personas are valid Scrum Product Owners and one is only a Product Owner Shaped Object (POSO). From an outside view the POSO complies with the Scrum rules but he doesn’t incorporate the Scrum mindset.

Walter

Walter is the POSO and his complete name is Walter Falls. His way of working is still sequential waterfall. He specifies the requirements and the team does the execution. What is missing here is the overlap of development activities (namely analysis and development) and the collaboration between the Product Owner and the development team.

Walter is a guy you would meet in a lot of Scrum implementations, because his way of working is very similar to the way the people have worked in waterfall projects for years. When doing a transition to Scrum Walter may be a suitable temporary type of Product Owner. But you should keep in mind that it is only an intermediate step and that Walter should transform into one of the other Product Owner personas.

Marty

Marty is the Product Owner that is described by the most of the Scrum literature and he is the most common valid Scrum Product Owner. I have chosen the name ‘Marty’ since I think this type of Product Owner is what Marty Cagans book “Inspired” implies.

Marty is relatively easy to implement and is therefore quite often. For a team beginning with Scrum Marty is normally a good choice. And then it may evolve into Eric or Jeff.

Eric

A lot of people think that Eric and Jeff aren’t valid Scrum Product Owners since they don’t provide all the details to the development team. Often the following statement referring to the dotted lists with the Product Owners responsibilities from the Scrum Guide is ignored:

The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable.

As long as Eric (or Jeff) remain accountable their approach to the Product Owner role is completely valid.

Eric is the most collaborative Product Owner regarding the interaction with the development team. Eric is a good choice when the what (the Product Backlog Items) is very unclear and need to be refined and redefined within the Sprint based on feedback gained during the Sprint. Teams doing Lean Startup with Scrum normally end up with Eric as the Product Owner. (And that is the explanation for the name. The cross-functional Lean Startup team described by Eric Ries is very similar to a Scrum team with Eric as the Product Owner).

Jeff

Jeff is the less supportive Product Owner but gives the development team the greatest freedom. The development team is not only responsible for the how but also defines large parts of the what. Jeff needs a mature development team with deep domain knowledge. Typically a Jeff Product Owner comes with long Sprints (e.g. a month) because the development team needs more time within the Sprint to figure out the details of the Product Backlog Items.

Jeff is suitable when the Product Owner can’t dedicate a lot of time to the Product Owner role. An example could be a CEO or other manager who assumes the Product Owner role. But this is only successful, when the development team has enough domain knowledge and is trusted adding all the details of the Product Backlog Items in a meaningful way.

And for the name: As far as I understand the first Scrum software project done by Jeff Sutherland at Easel incorporated a Jeff as Product Owner.

Entry filed under: it-agile-blog-planet. Tags: .

Shades of Scrum: The Scrum Master role Shades of Scrum: Sprint length

8 Comments Add your own

  • 1. sebsonconferences  |  December 17, 2012 at 12:31 pm

    I’ve worked with Jeff and it sucks. Been there, done that, never will do it again.

  • 2. stefanroock  |  December 17, 2012 at 7:16 pm

    I think there are specific contexts for each of the Product Owner personas. I think it would be very valuable to share these. Maybe you could provide some more informations?
    * What were the actual problems in your case?
    * How deep was the Scrum understanding at the Product Owner?
    * How experienced with the development team?
    * How experienced was the ScrumMaster?
    * How long were your Sprints?

  • 3. Shades of Scrum: Sprint length « Stefan Roock  |  December 20, 2012 at 7:48 am

    […] the Product Owner is overloaded (e.g. he is a Jeff type of Product Owner) […]

  • 4. Shades of Scrum | Stefan Roock  |  August 9, 2013 at 9:52 am

    […] 3 Product Owners and a Product Owner Shaped Object: The article describes 4 implementations of the Product Owner role and argues that one of the more common implementations isn’t a valid Scrum Product Owner. […]

  • 5. Buchtipp: “Software in 30 Tagen” | Stefan Roock  |  January 5, 2014 at 7:31 pm

    […] In den Fallbeispielen sind die Product Owner immer hochrangige Manager und nicht umgeschulte Business-Analysten, die zu vorgegebenen Features die Details aufschreiben. Ich habe über die Besetzung der Product-Owner-Rolle hier gebloggt. […]

  • 6. Urban legends on the ProductOwner role | Markus Gärtner  |  January 10, 2014 at 9:37 am

    […] role that would be more chicken-like or more pig-like. My colleague Stefan Roock blogged about three different ways to fill the product owner role, and one that does not justify the […]

  • 7. Alex Bepple (@alexbepple)  |  February 9, 2014 at 4:55 pm

    This is how I have been illustrating these PO personas in teaching and consulting: https://www.dropbox.com/s/saf0ol2zrd97uem/PO%20Personas.pdf

  • […] horizon needs another type of product ownership. According to the three types of product owners Eric may serve horizon 3 best, Jeff may be necessary to drive a horizon 2 innovation and Marty may […]

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed



%d bloggers like this: