<?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.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-gNCvPJgehxo6Gnb98n0AhA" name="new_roadmap,_rV_9MPndEdyLA5PXdgVJXw" guid="-gNCvPJgehxo6Gnb98n0AhA" changeDate="2008-08-07T03:25:25.000-0700" version="7.2.0">
  <mainDescription>&lt;h3>&#xD;
    How to adopt this practice&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    The following is a list of points that you need to consider when you adopt this practice.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Process scope:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;b>Test coverage:&lt;/b> component, feature, and subsystem, or all three&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Focus on the main elements:&lt;/b> tasks, artifacts, guidelines&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Team impact:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        &lt;b>Team composition:&lt;/b> Testers are part of the team, not external resources that are involved only at specific&#xD;
        points.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Roles:&lt;/b> This practice also needs to be adopted by developers to make sure that they provide tested&#xD;
        components.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        &lt;b>Skills:&lt;/b> Testers need to adopt a more technical skill set, and developers can also fill the Tester role.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Development approach:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Set a goal of stable builds that can be tested from end-to-end.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Provide smaller increments of functionality.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Institute &quot;walkthroughs&quot; to determine whether a micro-increment is correct.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Build and test frequently throughout an iteration.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Make passing automated tests the team's definition of &quot;finished&quot; for a requirement.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    Reach a pattern where the team continuously develops micro-increments, tests them, and then regression tests the&#xD;
    product throughout the day. Obviously, this involves a high degree of regression test automation. Achieving this level&#xD;
    of automation requires the concerted effort of the whole team, across all the levels of testing, with automated unit,&#xD;
    integration, system, and acceptance tests.&#xD;
&lt;/p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
