• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Work with all your cloud files (Drive, Dropbox, and Slack and Gmail attachments) and documents (Google Docs, Sheets, and Notion) in one place. Try Dokkio (from the makers of PBworks) for free. Now available on the web, Mac, Windows, and as a Chrome extension!

View
 

Scrum Master Role

Page history last edited by DanMezick 12 years, 2 months ago

The Community Scrum Master is responsible for the following:

 

0. Being a friend to the Team, at all times protecting the Team from disruptinve influences and distractions of all kinds;

 

1. Anticipation, indentification and removal of all impediments and obstacles facing the team;

 

2. Representation of management and team to each other (Schwaber & Beedle, pg 31);

 

3. Communicating constantly with Product Owner to help prioritize the Backlog and organize the work;

 

4. Acting as the driving force behind the use of genuine Scrum to execute on the work.

While our implementation of Scrum is customized to the work, the Scrum Master here at all times works to make sure that we always work consistent with the Scrum values of Commitment, Focus, Openness, Respect, and Courage (Schwaber and Beedle, pg. 147);

 

5. From time to time, the Scrum Master pulls from the Backlog, in affect enlisting as a team member in the work. 

We acknowledge that this occasional dual-role situation has certain risks related to Boundary, Authority, Role and Task. We manage these risks as expert-level Scrum practitioners.

 

The project uses an customized and adaptive Scrum structure. The project has a top-level team consisting of at most 7 categories of work and usually fewer than that. Each category has a Backlog and a Product Owner. Each of these Product Owners maintains a Backlog of work. The Community Scrum Master works with each sub-team Product Owner to help accomplish the work.

 

 

 

 

Comments (3)

George Schlitz said

at 6:35 pm on Aug 8, 2009

Concerning #5- consider not making it an explicit role of the SM to *not* act in accordance with what is probably good practice of the SM not taking on tasks. My point is that #4 and #5 contradict each other. If the SM takes on tasks, that is because the team and SM feel it is the best decision despite any risks of doing so, and not because it is the role of the SM to do so. So, I would remove #5 as an explicit part of the role description. What do you think?

Jean M Laporte said

at 9:54 pm on Aug 8, 2009

I would agree on removing #5 also. I might also add Protecting the team so that they can focus on their work.

DanMezick said

at 10:04 pm on Aug 8, 2009

We need to be clear and explicit here. The SM definitely pulls from the backlog from time to time on this project and this is a fact. This is an advanced technique with risks that are manageable assuming that there is strong competence in Scrum across all the participants in all the roles.

The purpose of the page is to state explicitly the SM role as adapted to this project. As we grow, we need more SM's to manage the work. This page makes plain the SM tasks on this project, such that candidates know what they are jumping into. We are acting on an advanced use of Scrum in our implementation. This includes pulling from the Backlog form time to time.

You don't have permission to comment on this page.