| <?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\tasks\improve_team_skills.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: improve_team_skills.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,{1C4325AC-17DE-4CD0-8AA0-4B210570579F} CRC: 1025171830 -->Improve Team Skills<!-- END:presentationName,{1C4325AC-17DE-4CD0-8AA0-4B210570579F} --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: purpose<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:purpose,-32JWpciwfc2e7HgQavJDkw CRC: 694350008 --><a id="XE_improve_team_skills__activity_definition" name="XE_improve_team_skills__activity_definition"></a> |
| <ul> |
| <li> |
| Help the team members identify skills that need improvement and implement activities to improve those skills. |
| </li> |
| </ul><!-- END:purpose,-32JWpciwfc2e7HgQavJDkw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_oNuxsWE-EdqnIZeW8YpHcA CRC: 2262641835 -->General <!-- END:name,_oNuxsWE-EdqnIZeW8YpHcA --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_oNuxsWE-EdqnIZeW8YpHcA CRC: 3647953136 --><a id="Prep" name="Prep"></a> |
| <p> |
| Teams are made up of individuals with an imperfect balance of technical expertise, domain or customer awareness, and |
| people skills. The team must continually identify and improve those skill areas that are lacking. The XP Coach helps |
| ensure that this happens. |
| </p> |
| <p> |
| The coach must always be aware of what difficulties the team is having in succeeding on their project. Some of these |
| will be evident, often communicated directly by the team. Some will be subtle with little awareness on the team that |
| there is a problem. To maintain this awareness, the coach must balance time spent in the trenches with the team, |
| observing specific use of the practices, with time spent reflecting on the team's capabilities, unencumbered by the |
| direct pressures of the project. |
| </p> |
| <p> |
| With an awareness of where the team needs improvement, the coach must help the team integrate improvement activities |
| into their work. Improvement activities need to be prioritized just as User Stories do. Different options will exist to |
| address skill improvement needs. The coach should be familiar with a wide variety of activities, courses, and games to |
| help people further their skills in a given practice. The coach acts as a conduit that connects the team with the |
| expertise required to improve a skill whether that other resource is in the organization or is an external resource. |
| </p> |
| <p> |
| One of the most effective tools to help the team identify areas for improvement is the Retrospective, a form of project |
| review. Techniques for this are described in Norm Kerth's book, <i>Project Retrospectives</i> [<a |
| class="elementLinkWithUserText" |
| href="./../../xp/guidances/supportingmaterials/xp_and_agile_process_references,6.191633934532389E-306.html#KER01" |
| guid="6.191633934532389E-306">KER01</a>]. Many teams have adapted the tools from the book to perform abbreviated |
| retrospectives after each iteration in addition to the more comprehensive session held at the completion of a full |
| project. |
| </p><!-- END:sectionDescription,_oNuxsWE-EdqnIZeW8YpHcA --> |
| </body> |
| </html> |