| <?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="-u_0D0nwGoZhpANLeqrq14A" |
| name="new_role,_O65KUOF6Edyp34pwdTOSVQ" guid="-u_0D0nwGoZhpANLeqrq14A" changeDate="2008-03-06T18:46:48.828-0500"> |
| <copyrightStatement href="uma://_6Ab_EOF4Edyp34pwdTOSVQ#_4kVeYOGBEdyp34pwdTOSVQ"/> |
| <mainDescription><p>
 |
| The Team:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Is cross-functional, with seven (plus/minus two) members;
 |
| </li>
 |
| <li>
 |
| Selects the Sprint goal and specifies work results;
 |
| </li>
 |
| <li>
 |
| Has the right to do everything within the boundaries of the project guidelines to reach the Sprint goal;
 |
| </li>
 |
| <li>
 |
| Organizes itself and its work; and
 |
| </li>
 |
| <li>
 |
| Demos work results to the Product Owner.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Scrum teams do not include any of the traditional software engineering roles such as programmer, designer, tester, or
 |
| architect. Everyone on the project works together to complete the set of work they have collectively committed to
 |
| complete within a sprint. Scrum teams develop a deep form of camaraderie and a feeling that "we're all in this
 |
| together."
 |
| </p>
 |
| <p>
 |
| A&nbsp;typical Scrum team&nbsp;is 5-9 people but can be scaled using a Scrum of Scrums.
 |
| </p></mainDescription> |
| <assignmentApproaches><p>
 |
| Members should be full-time but there may be exceptions (e.g. database administrator)
 |
| </p>
 |
| <p>
 |
| Members should change only between sprints
 |
| </p></assignmentApproaches> |
| </org.eclipse.epf.uma:RoleDescription> |
