| <?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>\base_concepts\guidances\concepts\team_profile.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: team_profile.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_dRKRMBtHEdqSLrJ4Ij2LVA CRC: 3704797792 -->Team Profile<!-- END:presentationName,_dRKRMBtHEdqSLrJ4Ij2LVA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_dRKRMBtHEdqSLrJ4Ij2LVA CRC: 2995988243 -->A Team Profile is a Breakdown Element that groups Role Descriptors or Composite Roles, thus defining a nested hierarchy of teams and team members.<!-- END:briefDescription,_dRKRMBtHEdqSLrJ4Ij2LVA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-J7jcN9p3FRyhuwV5Hq42Kw CRC: 3853389569 --><p> |
| Work assignments and Work Product responsibilities can be different from Activity to Activity in a development project. |
| Different phases require different staffing profiles, that is, different skills and resources doing different types of |
| work. Therefore, a Process needs to define these profiles in a flexible manner. Whereas Core Method Content defines |
| standard responsibilities and assignments, a Process expressed in breakdown structures needs to be able to refine and |
| redefine these throughout its definition. |
| </p> |
| <p> |
| Role Descriptors, Composite Roles, as well as Team Profiles provide the data structure necessary to achieve this |
| flexibility and to provide Process users with the capability to define different teams and Role relationships for |
| every Activity (including Activities on any nesting level as well as Iterations or Phases). Hence, in addition to the |
| work breakdown and Work Product breakdown structures, Team Profiles are used to define a third type of breakdown |
| structure: The Team Breakdown Structure. It is created as an Activity specific hierarchy of Team Profiles comprising of |
| Role Descriptors and Composite Roles. These structures can be presented as Org-Charts.<br /> |
| </p><!-- END:mainDescription,-J7jcN9p3FRyhuwV5Hq42Kw --> |
| </body> |
| </html> |
