| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:RoleDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmi:id="-Y3SFEe-A-lRF8TaEn9vKNQ" |
| name="new_role,_t1K9kPpYEdqsc-f87sBK8A" guid="-Y3SFEe-A-lRF8TaEn9vKNQ" authors="Claude Aubry" |
| changeDate="2007-01-08T08:37:05.421-0800" version="1.0.0"> |
| <mainDescription><p>
 |
| During development, he's in charge of helping the team to work autonomously and constantly improve itself.
 |
| </p>
 |
| <p>
 |
| To achieve that, he performs the following tasks:&nbsp;
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| periodical tasks,&nbsp;their objective is the application of Scrum by organizing and animating the <a
 |
| class="elementLink" href="./../../Scrum/guidances/concepts/Travail%20collaboratif_8AECB83B.html"
 |
| guid="_OUjj0AEZEduzRosbOajx7w">Collaborative work</a>&nbsp;(meetings)&nbsp;: 
 |
| <ul>
 |
| <li>
 |
| Daily Scrum.
 |
| </li>
 |
| <li>
 |
| Sprint planning
 |
| </li>
 |
| <li>
 |
| Sprint review
 |
| </li>
 |
| <li>
 |
| Retrospective
 |
| </li>
 |
| </ul>
 |
| </li>
 |
| <li>
 |
| Event tasks 
 |
| <ul>
 |
| <li>
 |
| eliminitating impediments&nbsp;: taking into consideration events occuring at any time on a project in
 |
| order to solve them as quickly as possible, while protecting the team from external distractions
 |
| </li>
 |
| </ul>
 |
| </li>
 |
| <li>
 |
| background task 
 |
| <ul>
 |
| <li>
 |
| Make sure the team stays focused on the original project goal, which is to develop backlog items in close
 |
| collaboration with the product owner, and stays productive.
 |
| </li>
 |
| </ul>
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Analogies
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The Scrum term comes from rugby. The half-scrum game position is the closest equivalent to the ScrumMaster role.
 |
| </li>
 |
| <li>
 |
| Ken Schwaber compares the ScrumMaster to a sheepdog.
 |
| </li>
 |
| </ul></mainDescription> |
| <keyConsiderations><ul>
 |
| <li>
 |
| He is not a project leader &nbsp;: he does not lead, nor oblige, neither constrain.
 |
| </li>
 |
| <li>
 |
| He is part of the team: he shares responsability with the other team members.
 |
| </li>
 |
| <li>
 |
| He must reguraly physically meet the other team members.
 |
| </li>
 |
| </ul></keyConsiderations> |
| <skills><p>
 |
| Expected Competencies and experience depend on size, and technical as well as management complexity. To play this role,
 |
| a person should have the following competencies:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| good knowledge of Scrum,
 |
| </li>
 |
| <li>
 |
| good presentation, communication and negociation skills,
 |
| </li>
 |
| <li>
 |
| guiding without obliging,
 |
| </li>
 |
| <li>
 |
| showing good men leadership and knowing how to motivate a team,
 |
| </li>
 |
| <li>
 |
| being a problem and conflict solver,
 |
| </li>
 |
| <li>
 |
| honestly commucatiing on work progress,
 |
| </li>
 |
| <li>
 |
| respecting the essential objective: to release a product fulfilling its requirements.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| However, it is not necessary to:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| have experience in the application domain (not essential, but can help),
 |
| </li>
 |
| <li>
 |
| have technical development competencies.
 |
| </li>
 |
| </ul></skills> |
| <assignmentApproaches><p>
 |
| for a typical Scrum team(6 to 10 persons) , a single person plays this role on a project.
 |
| </p>
 |
| <p>
 |
| The ScrumMaster can, eventually, participate to sprint tasks witht he other team members, but it needs to be limited.
 |
| </p></assignmentApproaches> |
| <synonyms><p>
 |
| Process facilitator. The ScrumMaster is sometimes defined as an Agile variation of the project leader, but this doesn't
 |
| help the understanding of the role.
 |
| </p></synonyms> |
| </org.eclipse.epf.uma:RoleDescription> |
