blob: cff852de2c3395b4e4faae247935cc60953e6cbb [file] [log] [blame]
<?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.3/uma.ecore" rmc:version="7.1.0" epf:version="1.0.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>&lt;p&gt;
During development, he's in charge of helping the team to work autonomously and constantly improve itself.
&lt;/p&gt;
&lt;p&gt;
To achieve that, he performs the following tasks:&amp;nbsp;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
periodical tasks,&amp;nbsp;their objective is the application of Scrum by organizing and animating the &lt;a
class=&quot;elementLink&quot; href=&quot;./../../Scrum/guidances/concepts/Travail collaboratif,_OUjj0AEZEduzRosbOajx7w.html&quot;
guid=&quot;_OUjj0AEZEduzRosbOajx7w&quot;&gt;Collaborative Work&lt;/a&gt;&amp;nbsp;(meetings)&amp;nbsp;:
&lt;ul&gt;
&lt;li&gt;
Daily Scrum.
&lt;/li&gt;
&lt;li&gt;
Sprint planning
&lt;/li&gt;
&lt;li&gt;
Sprint review
&lt;/li&gt;
&lt;li&gt;
Retrospective
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
Event tasks
&lt;ul&gt;
&lt;li&gt;
eliminitating impediments&amp;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
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
background task
&lt;ul&gt;
&lt;li&gt;
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.
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
Analogies
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
The Scrum term comes from rugby. The half-scrum game position is the closest equivalent to the ScrumMaster role.
&lt;/li&gt;
&lt;li&gt;
Ken Schwaber compares the ScrumMaster to a sheepdog.
&lt;/li&gt;
&lt;/ul&gt;</mainDescription>
<keyConsiderations>&lt;ul&gt;
&lt;li&gt;
He is not a project leader &amp;nbsp;: he does not lead, nor oblige, neither constrain.
&lt;/li&gt;
&lt;li&gt;
He is part of the team: he shares responsability with the other team members.
&lt;/li&gt;
&lt;li&gt;
He must reguraly physically meet the other team members.
&lt;/li&gt;
&lt;/ul&gt;</keyConsiderations>
<skills>&lt;p&gt;
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:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
good knowledge of Scrum,
&lt;/li&gt;
&lt;li&gt;
good presentation, communication and negociation skills,
&lt;/li&gt;
&lt;li&gt;
guiding without obliging,
&lt;/li&gt;
&lt;li&gt;
showing good men leadership and knowing how to motivate a team,
&lt;/li&gt;
&lt;li&gt;
being a problem and conflict solver,
&lt;/li&gt;
&lt;li&gt;
honestly commucatiing on work progress,
&lt;/li&gt;
&lt;li&gt;
respecting the essential objective: to release a product fulfilling its requirements.
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
However, it is not necessary to:
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
have experience in the application domain (not essential, but can help),
&lt;/li&gt;
&lt;li&gt;
have technical development competencies.
&lt;/li&gt;
&lt;/ul&gt;</skills>
<assignmentApproaches>&lt;p&gt;
for a typical Scrum team(6 to 10 persons) , a single person plays this role on a project.
&lt;/p&gt;
&lt;p&gt;
The ScrumMaster can, eventually, participate to sprint tasks witht he other team members, but it needs to be limited.
&lt;/p&gt;</assignmentApproaches>
<synonyms>&lt;p&gt;
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.
&lt;/p&gt;</synonyms>
</org.eclipse.epf.uma:RoleDescription>