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