| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\xp\customcategories\xp_roles_and_tasks.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: xp_roles_and_tasks.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,3.967980776087095E-306 CRC: 3903331342 -->XP Roles and Tasks<!-- END:presentationName,3.967980776087095E-306 --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-c5D4uYtVcDvab8GzkO0HiQ CRC: 816026380 --><a id="XE_activities__overview_of_xp_and_rup_activities" name="XE_activities__overview_of_xp_and_rup_activities"></a> |
| <div align="left"> |
| <table width="75%" border="1"> |
| <tbody> |
| <tr> |
| <td width="6%" rowspan="2"> |
| |
| </td> |
| <td align="middle" colspan="5"> |
| <a class="elementLink" href="./../../xp/guidances/concepts/whole_team,7.89591827591278E-306.html" |
| guid="7.89591827591278E-306">Whole Team</a> |
| </td> |
| </tr> |
| <tr> |
| <td align="middle" colspan="2"> |
| <a class="elementLink" |
| href="./../../xp/guidances/supportingmaterials/xp_customer_team,2.9889538140050517E-306.html" |
| guid="2.9889538140050517E-306">XP Customer Team</a> |
| </td> |
| <td align="middle"> |
| <a class="elementLink" |
| href="./../../xp/guidances/supportingmaterials/xp_developer_team,8.608243854485154E-306.html" |
| guid="8.608243854485154E-306">XP Developer Team</a> |
| </td> |
| <td align="middle" colspan="2"> |
| <a class="elementLink" |
| href="./../../xp/guidances/supportingmaterials/xp_organization,5.613949040902463E-308.html" |
| guid="5.613949040902463E-308">XP Organization</a> |
| </td> |
| </tr> |
| <tr> |
| <td align="middle"> |
| <b>XP Roles</b> |
| </td> |
| <td align="middle" width="17%"> |
| <a class="elementLinkWithUserText" |
| href="./../../xp/roles/xp_customer,{3C90DD4F-CFDB-4111-922D-3B840B8942DE}.html" |
| guid="{3C90DD4F-CFDB-4111-922D-3B840B8942DE}">Customer</a> |
| </td> |
| <td align="middle"> |
| <a class="elementLinkWithUserText" |
| href="./../../xp/roles/xp_tester,{FB65D00B-8304-4CF7-9969-52CE82F503DC}.html" |
| guid="{FB65D00B-8304-4CF7-9969-52CE82F503DC}">Tester</a> |
| </td> |
| <td align="middle"> |
| <a class="elementLinkWithUserText" |
| href="./../../xp/roles/xp_programmer,{08A6AF28-69B1-42DC-A957-2E6CDCB436C1}.html" |
| guid="{08A6AF28-69B1-42DC-A957-2E6CDCB436C1}">Programmer</a> |
| </td> |
| <td align="middle" width="13%"> |
| <a class="elementLinkWithUserText" |
| href="./../../xp/roles/xp_tracker,{D8FE277E-4F9A-47EB-855F-C451D601BBAF}.html" |
| guid="{D8FE277E-4F9A-47EB-855F-C451D601BBAF}">Tracker</a> |
| </td> |
| <td align="middle" width="12%"> |
| <a class="elementLinkWithUserText" |
| href="./../../xp/roles/xp_coach,{9C440605-FF0E-4D37-A774-BBF8B5F47AB6}.html" |
| guid="{9C440605-FF0E-4D37-A774-BBF8B5F47AB6}">Coach</a> |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| <br /> |
| </div> |
| <br /> |
| <h3> |
| XP Roles and Tasks |
| </h3> |
| <p> |
| XP defines a more limited set of roles and tasks than Unified Process. The XP roles usually have much broader scope |
| than Unified Process roles. There is a definite push in XP to move away from specialization where only one person on a |
| team has knowledge of specific and critical parts of the system or technology. The consequence is that the XP roles |
| usually map to more than one Unified Process role. Some Unified Process roles/tasks/artifacts do not map to anything in |
| XP as XP has a somewhat smaller scope than Unified Process. |
| </p> |
| <h4> |
| Definition of Roles and Tasks in Unified Process |
| </h4> |
| <p> |
| <b>Roles</b> are typically realized by an individual or a set of individuals working together as a team. A project team |
| member typically fulfills many different roles. <b>Roles</b> are not individuals; instead, they describe how |
| individuals behave in the business and what responsibilities these individuals have. While most roles are realized by |
| people within the organization, people outside of the development organization play an important role. A <b>role</b> is |
| an abstract definition of a set of <b>tasks</b> performed and <b>artifacts</b> generated. |
| </p> |
| <p> |
| <b>Roles</b> have a set of cohesive <b>tasks</b> to be performed. These <b>tasks</b> are closely related and |
| functionally coupled and are often best performed by the same individual. Tasks are closely related to |
| <b>artifacts</b>. Artifacts provide the input and output for the tasks and the mechanism by which information is |
| communicated between tasks. |
| </p><!-- END:mainDescription,-c5D4uYtVcDvab8GzkO0HiQ --> |
| </body> |
| </html> |