| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription 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="-24MPC2FhJbx7Fr0F6QEq8A" |
| name="xp_practices,2.2937799026801584E-305" guid="-24MPC2FhJbx7Fr0F6QEq8A" changeDate="2006-11-08T18:39:14.245-0500" |
| version="1.0.0"> |
| <mainDescription><a id="XE_xp__practices_of" name="XE_xp__practices_of"></a><a id="XE_practices_in__xp" name="XE_practices_in__xp"></a> 
 |
| <p>
 |
| XP is a collection of guiding values and best practices. Most of these practices have been used in the industry in some
 |
| shape or form for a number of years. XP has simply identified them and tried to push the envelope of these practices in
 |
| order to get the most benefit from them. Taken individually, these practices are all fairly simple. But it is the sum
 |
| of all of them that provides the most benefit as they reinforce each other to address the most difficult problems teams
 |
| encounter when developing software.
 |
| </p><br />
 |
| <br />
 |
| <p>
 |
| <img height="540" alt="" src="./../../../xp/resources/circleOfLife.jpg" width="720" usemap="#xp_practices_image_map" border="0" /> <map id="xp_practices_image_map" name="xp_practices_image_map">
 |
| <area shape="rect" coords="298,19,390,88" href="./../../../xp/guidances/concepts/whole_team.html" guid="7.89591827591278E-306"></area>
 |
| <area shape="rect" coords="176,135,282,200" href="./../../../xp/guidances/concepts/collective_ownership.html" guid="9.300699588493279E-306"></area>
 |
| <area shape="rect" coords="297,168,434,231" href="./../../../xp/guidances/concepts/test_driven_development.html" guid="1.620567348185129E-306"></area>
 |
| <area shape="rect" coords="447,135,547,198" href="./../../../xp/guidances/concepts/coding_standard.html" guid="8.8116853923311E-307"></area>
 |
| <area shape="rect" coords="15,236,122,305" href="./../../../xp/guidances/concepts/customer_tests.html" guid="2.297945473205673E-305"></area>
 |
| <area shape="rect" coords="218,238,362,307" href="./../../../xp/guidances/concepts/pair_programming.html" guid="3.876855509996079E-307"></area>
 |
| <area shape="rect" coords="392,241,512,305" href="./../../../xp/guidances/concepts/refactoring_xp_programming.html" guid="1.4410217108363206E-306"></area>
 |
| <area shape="rect" coords="614,236,714,302" href="./../../../xp/guidances/concepts/planning_game.html" guid="2.7371805612676613E-305"></area>
 |
| <area shape="rect" coords="143,325,270,393" href="./../../../xp/guidances/concepts/continuous_integration.html" guid="3.193414568279561E-305"></area>
 |
| <area shape="rect" coords="310,321,412,379" href="./../../../xp/guidances/concepts/simple_design.html" guid="1.6109092258980447E-306"></area>
 |
| <area shape="rect" coords="468,323,597,393" href="./../../../xp/guidances/concepts/xp_sustainable_pace.html" guid="3.133529870649493E-306"></area>
 |
| <area shape="rect" coords="307,386,413,436" href="./../../../xp/guidances/concepts/metaphor_system_of_names.html" guid="4.884861766532753E-306"></area>
 |
| <area shape="rect" coords="312,475,419,539" href="./../../../xp/guidances/concepts/small_releases.html" guid="5.762953011420275E-306"></area>
 |
| <area shape="rect" target="_blank" coords="561,494,708,538" href="http://www.xprogramming.com"></area>
 |
| </map>
 |
| </p>
 |
| <p>
 |
| This diagram arranges the core practices of Extreme Programming in a way that makes them easy to remember and that
 |
| exemplifies the steering and control cycles of the process.
 |
| </p>
 |
| <p>
 |
| The outer red circle is called the "Circle of Life". It's what keeps an XP project going, producing tested working
 |
| software. The <a class="elementLink" href="./../../../xp/guidances/concepts/whole_team.html" guid="7.89591827591278E-306">Whole Team</a>, customer members and development members, work together - preferably
 |
| physically together - to build the project. Using the <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/planning_game.html" guid="2.7371805612676613E-305">Planning Game</a> elements of Release Planning and Iteration Planning, they plan a
 |
| series of <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/small_releases.html" guid="5.762953011420275E-306">Small
 |
| Releases</a> of software that demonstrably pass all the <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/customer_tests.html" guid="2.297945473205673E-305">Customer Tests</a>.
 |
| </p>
 |
| <p>
 |
| The innermost blue circle describes the day to day, moment to moment, work of the XP developers. Each feature is
 |
| addressed with <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/simple_design.html" guid="1.6109092258980447E-306">Simple Design</a>, ensuring that the design of the system is just right for the features
 |
| supported. The programmers work in <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/pair_programming.html" guid="3.876855509996079E-307">pairs</a> for all production code development, providing continuous code review and
 |
| valuable, team-wide understanding of the system. They build the software using <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/test_driven_development.html" guid="1.620567348185129E-306">Test-Driven Development,</a> a technique that produces well-crafted and well-tested
 |
| software with a minimum of wasted effort, and the design is kept clean by the continuous improvement process of <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/refactoring_xp_programming.html" guid="1.4410217108363206E-306">Refactoring</a>.
 |
| </p>
 |
| <p>
 |
| The middle green circle contains the important supporting practices of XP. The software is designed according to a
 |
| common, shared, evolving <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/metaphor_system_of_names.html" guid="4.884861766532753E-306">Metaphor</a> that helps it all hang together. It is kept <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/continuous_integration.html" guid="3.193414568279561E-305">continuously integrated</a> with many system builds every day, each one fully tested. The
 |
| team shares ownership of of all the code so that needed changes can be made by any qualified pair, not just by one
 |
| individual. Since everyone works on everything, the team evolves a <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/coding_standard.html" guid="8.8116853923311E-307">standard
 |
| way of coding</a>. Finally, XP teams work at a <a class="elementLinkWithUserText" href="./../../../xp/guidances/concepts/xp_sustainable_pace.html" guid="3.133529870649493E-306">sustainable pace</a> that enables them to deliver tested software on a predictable basis
 |
| from the first day of the project until the last.
 |
| </p>
 |
| <p>
 |
| <br />
 |
| &nbsp;
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
