Forums

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. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

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.

Development Team Size Question
Last Post 09 Jan 2014 11:22 PM by Ian Mitchell. 3 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Nicolas Sanzana
New Member
New Member
Posts:15
Nicolas Sanzana

--
09 Jan 2014 04:28 PM
    Hello guys,

    I'm reading Scrum guide section 'Development Team Size' and appears the following statement:

    "The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog"

    So my questions are:

    1 - A person who is PO could to have another role in the Team, for example be developer too?
    2 - A person who is SM could to have another role in the Team, for example be developer too?

    Thank you,

    Best Regards,
    Nitin Khanna
    Basic Member
    Basic Member
    Posts:100
    Nitin Khanna

    --
    09 Jan 2014 05:13 PM
    Yes, to both questions.

    However, a Scrum Master cannot be the Product Owner or vice versa.
    Nicolas Sanzana
    New Member
    New Member
    Posts:15
    Nicolas Sanzana

    --
    09 Jan 2014 05:36 PM
    Thanks a lot for your response Nitin.
    Regards
    Nico
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1615
    Ian Mitchell

    --
    09 Jan 2014 11:22 PM
    > However, a Scrum Master cannot be the Product Owner or vice versa.

    I think most would agree. However, this restriction does not appear to be core Scrum, in so far as it is not included in the Scrum Guide.

    It is included in the Scrum Primer and it is clearly a best practice. I wonder if the omission of this constraint is an oversight.

    You are not authorized to post a reply.


    Feedback