Whats the difference between Scrum master and just a book keeping or AI maintainer

This is a discussion thread that i received on the topic of Scrum Master. It looks very much relevant in most companies


Saurabh Agarwal <s*****@gmail.com> Sat, Jan 5, 2013 at 9:49 AM
Reply-To: scrumalliance@googlegroups.com
To: scrumalliance@googlegroups.com
Hi All,

I am little confused with my understanding of Scrum master and not
sure if its correct.

As per my understanding SM need not have any technical contribution to
the project and main job is resolving obstacles ( mostly tracking with
folks with not understanding things technically mostly).
He participate in Iteration planning to just pen down the tasks and
not contributing anything technically.
Rest work definition includes sending meeting invite, tracking PO for
US acceptance, manage WIP etc.

Most of them look basically tracking tasks only.
I am little confused if my understanding is correct or there are many
gaps in the same.

Thanks
Saurabh

--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To post to this group, send email to scrumalliance@googlegroups.com.
To unsubscribe from this group, send email to scrumalliance+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scrumalliance?hl=en.

Yuen-Chi Lian <m*****@yclian.com> Sat, Jan 5, 2013 at 1:14 PM
Reply-To: scrumalliance@googlegroups.com
To: scrumalliance@googlegroups.com

As per my understanding SM need not have any technical contribution to
the project and main job is resolving obstacles ( mostly tracking with
folks with not understanding things technically mostly).

In Scrum, we call it "impediments".

He participate in Iteration planning to just pen down the tasks and
not contributing anything technically.

To your surprise, a Scrum Master is not required in many events of the Scrum, only when it`s requested or needed (and just to facilitate, not to pen down).

Rest work definition includes sending meeting invite, tracking PO for
US acceptance, manage WIP etc.

Many of these tasks can be done by a self-organized team.

Most of them look basically tracking tasks only.

Scrum Master doesn`t track. Scrum Master is there to ensure that Scrum is properly implemented.

YC

[Quoted text hidden]
Daniel James Gullo <d******@trinacria-consulting.com> Sat, Jan 5, 2013 at 5:22 PM
Reply-To: scrumalliance@googlegroups.com
To: scrumalliance@googlegroups.com
Saurabh-

A good Scrum Master wears many hats: coach, facilitator, counselor, negotiator, mentor, teacher, advocate... They also do NOT wear others: functional manager, project manager, architect, business owner, Product Owner, etc.

Scrum does not specifically prescribe domain knowledge or technical knowledge but it is implied that a Scrum Master is from the area in which they functioning; that is, anyone from a particular project area can become a Scrum Master if they understand the full scope of the responsibilities and characteristics. We can have a theoretically debate over this, I am sure. Some will argue that you could take someone off the street, teach them Scrum, and then put them in a Scrum Master role. However, I would argue that they need to understand the business model, the technology being used, etc. or they are going to spend a lot of time asking simple questions that someone who comes from that background already understands.

I would recommend attending a CSM course where the various nuances of the role would be covered in depth. It`s one thing to read about Scrum and what a CSM should be and yet another to actually experience it first hand. HTH.

Ganbarimasu-

Daniel Gullo
CSC, ACP, PMP, CSP, CSM, CSPO

Trinacria Consulting
d*****@trinacria-consulting.com

See you at:

REGISTER NOW for 2013 Scrum Gathering Las Vegas - #sglas

For more information on how to sponsor a Gathering, download the information packet or contact Yvonne at ydewar@scrumalliance.org or (905) 281-0555 ext 111.



[Quoted text hidden]
[Quoted text hidden]
Saurabh Agarwal <s*******@gmail.com> Sat, Jan 5, 2013 at 6:02 PM
Reply-To: scrumalliance@googlegroups.com
To: scrumalliance@googlegroups.com
Thanks a lot for your comments.

I liked the pick up from street part , Actually the SM choosen in our
case has a view that he/she need not understand tech things and is
merely more of tracking ,helping team member`s in removing obstacles
and to me seems like a role which is not taking any ownership.

I understand major stake is with the team but since the team is new
and they are more in driven mode rather than driving mode.

Thanks
Saurabh


On Sat, Jan 5, 2013 at 5:22 PM, Daniel James Gullo
<d******@trinacria-consulting.com> wrote:
>
> Saurabh-
>
> A good Scrum Master wears many hats: coach, facilitator, counselor, negotiator, mentor, teacher, advocate... They also do NOT wear others: functional manager, project manager, architect, business owner, Product Owner, etc.
>
> Scrum does not specifically prescribe domain knowledge or technical knowledge but it is implied that a Scrum Master is from the area in which they functioning; that is, anyone from a particular project area can become a Scrum Master if they understand the full scope of the responsibilities and characteristics. We can have a theoretically debate over this, I am sure. Some will argue that you could take someone off the street, teach them Scrum, and then put them in a Scrum Master role. However, I would argue that they need to understand the business model, the technology being used, etc. or they are going to spend a lot of time asking simple questions that someone who comes from that background already understands.
>
> I would recommend attending a CSM course where the various nuances of the role would be covered in depth. It`s one thing to read about Scrum and what a CSM should be and yet another to actually experience it first hand. HTH.
>
> Ganbarimasu-
>
> Daniel Gullo
> CSC, ACP, PMP, CSP, CSM, CSPO
>
> Trinacria Consulting
> d******@trinacria-consulting.com
>
> See you at:
>
[Quoted text hidden]
Daniel James Gullo <d******@trinacria-consulting.com> Sat, Jan 5, 2013 at 6:27 PM
Reply-To: scrumalliance@googlegroups.com
To: scrumalliance@googlegroups.com
That`s where the coaching and mentoring come into play. Coaching and mentoring is not about commanding and controlling. It`s about figuring out where people are trying to go (per their own agenda) and then helping them get there. A Scrum Master should not be appointed or assigned. Someone should aspire to being Scrum Master with the full understanding of the role. The one critical requirement in Scrum for the Scrum Master is that they be a Master of Scrum; as in the master of their craft and the Scrum framework. If the person in the role is very new to Scrum, there may be some significant growing pains. Those can be alleviated somewhat by enlisting the help of those who are more experienced; e.g. hiring experienced Scrum Masters, seeking coaching, investing in training, establishing communities of practice in the organization which are deeply involved in the Agile/Scrum community externally...

Ganbarimasu-

Daniel Gullo
CSC, ACP, PMP, CSP, CSM, CSPO

Trinacria Consulting
d******@trinacria-consulting.com

See you at:

REGISTER NOW for 2013 Scrum Gathering Las Vegas - #sglas

For more information on how to sponsor a Gathering, download the information packet or contact Yvonne at ydewar@scrumalliance.org or (905) 281-0555 ext 111.