about services publications events blog
Pichler logo

All Things Product Owner

Archive for March, 2010

The Desirable Characteristics of a Product Owner

Mar
31

I often get asked what characteristics a product owner should exhibit. Even though the answer depends on a number of factors including the type of the product, its importance, complexity and newness as well as the size of the project, successful product owners I have worked with share the attributes discussed below.

Visionary and Doer

The product owner is a visionary who can envision the final product and communicate the vision. But the product owner is also a doer who sees the vision through to completion. This includes describing requirements, closely collaborating with the team, accepting or rejecting work results, and steering the project by tracking and forecasting its progress. As an entrepreneur, the product owner facilitates creativity; encourages innovation; and is comfortable with change, ambiguity, debate, conflict, playfulness, experimentation, and informed risk taking.

Leader and Team Player

“Good business leaders create a vision, articulate the vision, passionately own the vision, and relentlessly drive it to completion,” says Jack Welch, GE’s former chairman and CEO. The product owner is just such a leader. As the individual responsible for the product’s success, the product owner provides guidance and direction for everyone involved in the development effort and ensures that tough decisions are made. For instance, should the launch date be postponed or should less functionality be delivered? At the same time, the product owner must be a team player who relies on close collaboration with the other Scrum team members, yet has no formal authority over them. You can think of the product owner as primus inter pares, first among peers, regarding the product.

Being a leader and team player can be a hard line to toe. By no means should the product owner dictate decisions, yet at the same time neither should the product owner be indecisive or employ a laissez-faire management style. Instead, the individual should act as a shepherd for the innovation process, guiding the project and seeking team consensus in the decision-making process. Making decisions about the product collaboratively ensures the team’s buy-in, leverages the team’s creativity and knowledge, and results in better decisions. Working this way requires facilitation and patience because team members often have to disagree and argue first before a new solution can be synthesized from the different ideas and perspectives.

Communicator and Negotiator

The product owner must be an effective communicator and negotiator. The individual communicates with and aligns different parties, including customers, users, development and engineering, marketing, sales, service, operations, and management. The product owner is the voice of the customer, communicating customer needs and requirements and bridging the gap between “the suits” and “the techies.” Sometimes this means saying no and other times negotiating a compromise.

Empowered and Committed

The product owner must have enough authority and the right level of management sponsorship to lead the development effort and to align stakeholders. An empowered product owner is essential for leading the effort to bring the product to life. The product owner must have the proper decision-making authority—from finding the right team members to deciding which functionality is delivered as part of the release. The individual must be someone who can be entrusted with a budget and at the same time has the ability to create a work environment that fosters creativity and innovation. Finally, the product owner must be committed to the development effort.

Available and Qualified

The product owner must be available and qualified to do a great job. Being the product owner is usually a full-time job. It is important to give product owners enough time to sustainably carry out their responsibilities. If the individual is overworked, the project’s progress suffers and the resulting product may be suboptimal. Being adequately qualified usually requires an intimate understanding of the customer and the market, being passionate about the user experience, and the ability to communicate needs and describe requirements, to manage a budget, to guide a development project, and to be comfortable working with a cross-functional, self-organizing team.

Nobody is Perfect

Before you now look for the perfect product owner or worry that you might not fit the bill, be aware that product owners usually need time and support to transition into the role and to acquire the necessary skills. And nobody is perfect: Every product owner has some strengths that facilitate playing the role as well as some weaknesses that can make it challenging. A product owner may be very good at envisioning the product, talking to customers, and creating the product roadmap but may not be used to work closely with a bunch of techies or lack the necessary release planning skills, for instance. A common challenge is finding employees with the necessary breadth and depth of knowledge and experience to do the job well.

More Information

You can find out more about the product owner role in my book Agile Product Management with Scrum: Creating Products that Customers Love available now on amazon.com. The book dedicates a whole chapter to the product owner role and provides more information about the desirable product owner characteristics. Why not register for one of my upcoming product owner classes to learn through dialogue and exercises what it takes to be an effective product owner. I also teach in-house product owner courses and run in-house product owner workshops.

spacing rule

New Book — First Look

Mar
26

Agile Product Management with Scrum

This copy of my new book Agile Product Management with Scrum arrived a few days ago on my desk fresh off the press. Needless to say, seeing the final product after two years of hard work was very exciting, and I was well chuffed!

But I could not have written the book without the support of many people. Two played a particularly important role: Mike Cohn acted as my shepherd patiently reading and re-reading chapters as they evolved. My wife Melissa Pichler did not only provide feedback and encouragement on sections and chapters as they emerged but also gave me the time and space to write the book.

Many thanks to everyone else who helped with the book by reviewing chapters or by sharing information (in alphabetical order): Lyssa Adkins, Geir Amsjø, Markus Andrezak, Gabrielle Benefield, Robert Bogetti, Thomke Buhl, Marty Cagan, Sabine Canditt, John Clifford, Alistair Cockburn, Jens Coldeway, Kaustabh Debbarman, Pete Deemer, Chris Fry, Steve Greene, Roland Hanbury, Kevlin Henney, Ben Hogan, Clinton Keith, Andreas Klinger, Hans-Peter Korn, Jochen Krebs, Craig Larman, Bill Li, Lowell Lindstrom, Catherine Louis, Rodrigo Luna, Artem Marchenko, Jason Martinez, Ralph Miarka, Philip Missler, Bent Myllerup, Jeff Patton, Tobias Pichler, Brett Queener, Cesário Ramos, Dan Rawsthorne, Simon Roberts, Stefan Roock, Rene Rosendahl, Johanna Rothman, Kenneth Rubin, Martin Rusnak, Hans-Peter Samios, Bob Schatz, Andreas Schliep, Ken Schwaber, Christa Schwanninger, Karl Scotland, Martin Shaw, Lisa Shoop, James Siddle, Michele Sliger, Preston Smith, Dieter Stefanowitz, Jeff Sutherland, Mads Troels Hansen, Bas Vodde, Geoff Watts, Harvey Wheaton, Rüdiger Wolf, Elizabeth Woodward, and Lv Yi.

The book is available now at amazon.com! It should just be a matter of days before the book is on sale in Europe.

spacing rule