<?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.5/uma.ecore"
    xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmlns:rmc="http://www.ibm.com/rmc"
    rmc:version="7.5.0" xmi:id="-vY5HfUn9RSoqJC3J7QtxhA"
    name="new_concept,_qhCTAFRREd2CWscN8Mx6rg" guid="-vY5HfUn9RSoqJC3J7QtxhA" changeDate="2008-09-04T17:59:01.093-0700"
    version="7.5.0">
  <mainDescription>&lt;h3>&#xD;
    Why Practices?&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Practices enable a compositional approach to building methods. This approach offers the following benefits:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Adaptability and scalability&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Incremental adoption&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Easy to configure and use&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Community development&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    Adaptability and Scalability&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Practices can be adapted to&amp;nbsp;support a range of solutions.&amp;nbsp;In particular, practices can be adapted to suit&#xD;
    your organization and supplemented by your own practices.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The core practices are based on a common framework that allows them to be composed.&amp;nbsp; These core practices&amp;nbsp;are&#xD;
    tool-agnostic, low-ceremony practices that can be extended to address a broad variety of development concerns, such as&#xD;
    SOA, geographical distribution, model-driven architecture and embedded systems. Tool and technology specific guidance&#xD;
    can be added, such as guidance on J2EE, and a variety of development tools. Some of these extensions can be quite&#xD;
    modest, adding&amp;nbsp;for example&amp;nbsp;just tool specific guidance to existing tasks, while others can be comprehensive,&#xD;
    defining processes that provide a radically expanded scope with new or altered artifacts, new or altered tasks, and new&#xD;
    or altered roles.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Extensions and additions to&amp;nbsp;the practices&amp;nbsp;can be:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        used internally by an organization&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        open source as a part of the Eclipse Process Framework (EPF) project&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        made freely available outside the open source licenses of Eclipse (EPL)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        sold commercially as an extension to the basic framework, such as the IBM(R) Practices.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    Incremental Adoption&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Each practice is described as a standalone capability that can be adopted by an organization or project.&amp;nbsp;Each&#xD;
    practice may include enablement materials that explain how to get started.&amp;nbsp;&amp;nbsp;&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    Easy to Configure and Use&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Creating a method is as simple as selecting the practices that you wish to adopt, and then publishing the&#xD;
    results.&amp;nbsp;Each practice adds itself into the framework so that content can be viewed by practice, or across&#xD;
    practices by work product, role, task and so on.&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    Community Development&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    Since a practice can be easily authored on its own, practices are ideal for community development.&amp;nbsp;The basic agile&#xD;
    practices for the&amp;nbsp;EPF Practices are, in fact, developed by the Eclipse Process Framework community.&amp;nbsp;&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>