Skip to main content

What does a good Product Owner need?

Why is it so challenging for a company to get the Scrum Product Owner role right?  It is a great job.  Lots of power to envision a market an deliver the product that makes a difference in that space.  Plenty of feedback and opportunity to learn by guiding a truly Agile team toward achieving the goals.

The responsibilities are few but require discipline and dedication to the vision of the product.  The key task is to prioritize (stack rank - not hi-low bucketing) the product backlog.  By doing this the product owner optimizes the return on investment for the project as a whole and within the enterprise ecosystem.
Steve Jobs on innovation. "It comes from saying no to 1,000 things to make sure we don't get on the wrong track or try to do too much."
-- BusinessWeek Online, Oct. 12, 2004

I was reminded this week of why the committee of product owners will not work. I was working with a Steering Committee.  [Aside:  Is that term an oxymoron or what?  How many peoples hands do you want on your steering wheel?]  My challenge to them was that their primary role was to find the teams a Scrum Product Owner.  It was not to set the priorities of the various projects that the teams should work on - which is what they had met to accomplish.

A colleague mentioned the 1962 Chicago Cubs owner P.K. Wrigley's failed College of Coaches as an analogy. Having tried a baseball analogy and failed to make the point with this largely international group, I decided to search other domains for inspiration.

How about Apple - home of "insanely great" products - is there inspiration for the Scrum roll of the one Product Owner at Apple?  Why, yes - yes there is!

How many companies are envious of Apples ability to deliver great product to market, and even shape the new and emerging markets?  Answer: many - if not all.  Even Nokia is willing to burn their platform to create a reason to change to a new Windows 7 solution in hopes of holding onto market share.  While Nokia's CEO Stephen Elop has realized (perhaps too late) that the environment has changed.  Apple has created a whole ecosystem of simple products that are symbiotic (see eHub strategy - 2001).

While I enjoyed Elop's use of the burning platform metaphor - I don't think one should pour gasoline upon their own burning platform.  That sounds like a suicidal tendency.  Perhaps he intended to mix his metaphors.  I also enjoy a well mixed metaphor - shaken not stirred.

But back to the product owner roll.  Why has Steve Jobs been so successful and has Elop in a panic state?  I think it comes down to vision - purpose - acting to fulfill ones core values.  Steve Jobs has been doing this since he built and sold his first Apple computer kit.  He set out to change how people interact with computers.  The March 2, 2011 iPad 2 announcement indicates that he believes this is at least the 2nd time if not the Nth time Apple has delivered on the dream - "to make computers for the rest of us."  He refers to the iPad device as a post-PC device.  He knows the landscape has changed - he had a dream.

The human is the only creature on earth that is capable of imagining a future and then creating that future.  To do this we use one powerful ability - Imagination.  This is one of my personal values.  I believe this is an ability every great product owner must have.

See Also:  We Don't Hire Product Owners Here


Most Popular on Agile Complexification Inverter

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?

Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.

In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.

Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    To Do
    Work In P…

Webinar: Collaboration at Scale: Defining Done, Ready, and NO.

I was invited to participate in a Scrum Alliance Webinar.  Maybe you would like to listen to us in a discussion of techniques to collaborate at scale (remotely and with many people).  The topic is one that I've got some experience in discussions - yet I never seem to get to done...
Collaboration at Scale: Defining Done and Ready and NO for Distributed Teams
With Joel Bancroft-Connors, Agile Organizational Coach; David A. Koontz, Agile Transition Guide; and Luke Hohmann, CEO and Founder of Conteneo, Inc.

14 February 2018 11 a.m. ET (USA).

The Scrum Guide is pretty clear on the criticality of the definition of Done: "When a Product Backlog item or an Increment is described as "Done," everyone must understand what "Done" means. However, the Scrum Guide ALSO says that the definition of Done can "vary significantly per Scrum Team." This leads us to examine when and how the definition of Done should vary, how distributed teams should cr…

A T-Shaped 21st Century Knowledge Worker

Knowledge workers in the 21st Century must have many areas of deep knowledge, while also be capable of collaboration across multiple other domains with dissimilar T-shaped individuals.  This description of a person is a metaphor.  Compare it to the shape of the "I" in the classic saying there is no "I" in Team.

I first read about Scott Ambler's term "Generalizing Specialist" - but it's so hard to remember the proper order of the words... get it backwards and it has an inverted meaning... T-Shaped is easier to remember. 
A generalizing specialist is someone who:
Has one or more technical specialties (e.g. Java programming, Project Management, Database Administration, ...). Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new skills in both their existing specialties as well as in other areas, including both technical and domain areas.  General…

A FAILURE to Communicate

I was working with a failing team some time ago.  I use "failing" to describe the outcome of the team - not the people on the team.  Are you OK with that description?

An issue arrose in the stand up - a team member that was to verify the quality of a procedure did so and reported that there were a few records that didn't match expectation in the data set.  Upon inquire the number of records not matching was over 2000.  Most people acknowledged immediately the exaggeration - I could tell by the laughter.  After about 10 minutes of discussing the details of the problem - it appeared the team had a handle on the specific situation.

I stopped the discussion and inquired if they could name the impediment.  One team member did a great job of describing the impediment as a _communication gap_.  Wonderful - I could work with that - the problem had a name and it didn't include anyones Proper Name.

"If the problem has a first name; we are going to have a problem."