Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Product Owner vs Product Manager #187

Open
eharrisSSA opened this issue Jul 7, 2016 · 3 comments
Open

Product Owner vs Product Manager #187

eharrisSSA opened this issue Jul 7, 2016 · 3 comments

Comments

@eharrisSSA
Copy link

For play #6, is it possible to be less direct about the Product Owner? A lot of times, agencies focus heavily on the role and less on the functions needed to be performed. Aren't we more concerned with having an accountable authoritative person responsible for the "success or failure of the overall service?"

I ask because these duties can be performed by a Product Manager. We have a Product Manager looking outward strategically and a Product Owner looking inward tactically. But saying product owner, and not listing alternatives or allowing for flexibility, makes it hard to implement when Sr. Leaders look to guidebooks for guidance.

Is it possible to say "Product Owner or Manager" showing that different agile process may call this role by different names, but in the end, the functions are largely the same.

Thanks for the consideration.

@rdymond1
Copy link

rdymond1 commented Jul 8, 2016

The Product Manager and Product Owner roles largely overlap. In the large
majority of cases I can't see a need to have both roles. Having both would
lead to waste, including handoffs, information loss, over production of
backlog items, and diffused responsibilities.

The Product Owner is responsible for delivering a return on investment ROI
for the cost and time invested. Having a product manager blocking their
access to customers and assuming responsibility for the customer
relationship without being responsible for delivering the value is a recipe
for long term systemic problems.

There are a few exceptions to this pattern. For example if the organization
has a large customer base that is fragmented and 500+ team members on 50 to
100 teams. In large complex solutions product owners and product managers
may coexist due to the size and complexity of the system and
customer/stakeholder base. In this case a scaling framework such as Large
Scale Scrum (LeSS) provides a good solution.

Robin Dymond, CST
Managing Partner, Innovel
www.innovel.net
www.scrumtraining.com
Direct: (804) 239-4329
twitter: @RobinDymond
Linkedin: https://www.linkedin.com/in/robindymond

@cew821
Copy link
Contributor

cew821 commented Jul 8, 2016

Hi @eharrisSSA and @rdymond1, thanks for the feedback. For the purposes of this section, I think we are using "product owner" and "product manager" interchangeably. We chose "product owner" since that term tended to be more common in government, while "product manager" is a term more common in the private sector.

We agree with the sentiments you are expressing. The important thing is that there is an individual responsible for overall success of the product... regardless of the title that person holds. I think we are open to a change that makes this more clear. Is there a specific wording change you could recommend?

@eharrisSSA
Copy link
Author

@cew821 I agree. I'm more interested in the function/responsibility verses the title. However, gaining buy-in from executives who look at guidance like this playbook, see the term "owner" and make it harder to navigate the various possibilities for improvement (like introducing core-assets for product lines).

I would recommend simply saying manager/owner, or stating the responsibility and making the title an parenthetical example (i.e. product owner or product manager) would take care of it.

Thank you for your attention. This is GREAT and much needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants