Roles in a nutshell, according to me: Product Owner: Answers What? for the product. The Team Members: Answers How? for the product. Scrum Master: AnswersMessage 1 of 2 , Sep 10, 2010View SourceRoles in a nutshell, according to me:Product Owner: Answers "What?" for the product.The Team Members: Answers "How?" for the product.Scrum Master: Answers "What?" and "How?" for productivity.Obviously, such terse answers leave much out. For example, it is better for the team if the Scrum Master guides the team to improve productivity rather than just providing answers.Those brief phrases define the boundaries, if you will. However, the boundaries are not hard walls since everyone on the team should pay attention to the whole product and especially how to work better. Another way to look at it is to say that the Scrum Master helps the Product Owner and the Team do their part, but does not do their part for them.I have a post on my blog that is actually not specifically about this topic but the last part of the post might help you understand some of my thoughts on the nutshell explanations above.
Briefly, the Scrum Master cares for the often neglected "people" part of the work.AlanOn Fri, Sep 10, 2010 at 8:23 PM, Rafael Nascimento <rafaelnascimento.rj@...> wrote:
I find kind of hard to define clearly the Scrum Master role. So, I thought I could hear from you some answers that can help us define this role in a better way:
What a Scrum Master should NOT do?
So, people, where do you think the end of the Scrum Master boundary is?