Skip to main content

Scrum Master reporting to Product Owner?

Last post 06:11 pm May 16, 2017 by Timothy Baffa
5 replies
04:54 pm May 1, 2017

This doesn't seem like a good set up, but I'm curious as to what your thoughts are. Is it a good idea or a bad idea for the SM to have the PO as their manager?


01:53 pm May 3, 2017

What are your own thoughts on this, based on your reading and understanding of the Scrum Guide?


05:09 am May 4, 2017

As far as I understand, reporting doesn't matter as long as PO understand the roles and responsibilities of a Scrum Master. Also his/her own roles and responsibilities towards Scrum Master and doesn't direct him/her.


12:11 pm May 5, 2017

Since the PO is a Scrum Team member, why would he or she need reports at all? Shouldn't team transparency be adequate for product ownership purposes? 


01:42 pm May 16, 2017

The sticky part is that the PO wants to push the Scrum Master to do things that may not be in the team's best interest - because the entire team reports to the PO -  they are the manager of the team.

This bring hierarchy into the team where there should be none.


04:58 pm May 16, 2017

Melissa, the Product Owner is not the manager of the Development Team.   The main responsibility of the Product Owner is to insure that the Development Team is offered the most valuable and critical items each sprint based on organizational needs and customer input.   The Product Owner should also work with the Development Team to hold them accountable for their sprint forecast, and ensure that the Sprint Goal is achievable.

 

Your ending statement is spot-on, though.   Hierarchy does not belong in a Scrum Team.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.