<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:GuidanceDescription 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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf"
    epf:version="1.5.0" xmi:id="-IdlCQXdDNYGrGJU4TBwvCA"
    name="new_example,_Nzv5kDoAEdusGsHODb-STA" guid="-IdlCQXdDNYGrGJU4TBwvCA" changeDate="2009-08-05T16:38:30.353-0700"
    version="1.0.0">
  <mainDescription>&lt;h3>&#xD;
    1 Introduction&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    This plan covers the content and enablement portions of the EPF 1.0 project. A separate plan covers the tooling&#xD;
    component.&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    2 Project Organization&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    See also: &lt;a href=&quot;http://www.eclipse.org/epf/&quot;>http://www.eclipse.org/epf/&lt;/a>&lt;br />&#xD;
    &lt;br />&#xD;
    The work is divided into a number of content areas. Each content area is lead by a committer that is the content lead,&#xD;
    working closely with a number of committers and contributors. The content lead is responsible for making sure that bugs&#xD;
    and enhancement requests are triaged and assigned, and responsible for updating the project burndown (status) on a&#xD;
    weekly basis.&lt;br />&#xD;
    &lt;br />&#xD;
    We also have a content architect (Ricardo Balduino), who is responsible for the overall structure and integration of&#xD;
    content from all content areas.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The work is divided into the following content areas:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Project management: Chris Armstrong (lead), Jochen Krebs, Per Kroll&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Requirements: Chris Sibbald (lead), Paul Bramble, Ana Paula Valente Pereira, Leonardo Medeiros, Kurt Sand, Bruce&#xD;
        MacIsaac, Jim Ruehlin, Ricardo Balduino, and others.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Change management: Chris Sibbald (lead), Kurt Sand, and others.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Development: Brian Lyons (lead), Scott Ambler, Ricardo Balduino, and others.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Architecture: Mark Dickson (lead), Jim Ruehlin, Ana Pereira, Chris Doyle, and others.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Test: Brian Lyons (lead), Nate Oster, Jeff Smith, Dana Spears, and others.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        General: Steve Adolph (lead),&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Developer outreach: Per Kroll / Naveena Bereny (leads), Ricardo Balduino, Scott Ambler, Kurt Sand, and others.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    3 Project Practices and Measurements&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    The OpenUP component team will use OpenUP practices adapted to address the fact that we are doing content development&#xD;
    rather than coding. Key artifacts include: Project Plan (Word), Work Item List (Bugzilla + Excel), Iteration Plan&#xD;
    (Word), and Status Assessment (Word).&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Progress is tracked using two primary measurements using a point system. It is estimated that 1 point represents 2h of&#xD;
    work:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Project backlog: The project backlog shows progress relative to overall work to be done within the project.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Iteration backlog: The iteration backlog shows progress relative to work intended for the current iteration.&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;h3>&#xD;
    4&amp;nbsp; Project Milestones and Objectives&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    This section covers objectives for the entire EPF 1.0 project.&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Governance process in place, including guidelines for how to work with CVS&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Tutorials available to help people adopt EPF composer&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Process tools matured and usable to produce a broad set of processes and method content.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Basic set of interfaces / APIs defined, stabilized, and delivered.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Deliver basic printing capability.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Mature content. Deliver a mature OpenUP, and beta quality of one or more other processes, whereof one should be&#xD;
        another agile process.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Generate a high level of interest around EPF v1.0. Press releases, papers, tutorials, workshops, presentations,&#xD;
        etc.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Identify a broader set of process champions with an interest to contribute to EPF within a specific domain, such as&#xD;
        MDA or project management, or a specific vertical such as telecom.&lt;br />&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;table title=&quot;&quot; cellspacing=&quot;0&quot; cellpadding=&quot;2&quot; width=&quot;85%&quot; border=&quot;1&quot;>&#xD;
    &lt;tbody>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                &lt;strong>Phase&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;strong>Iteration&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;strong>Primary Objective (risks and use cases scenarios)&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;strong>Scheduled start or milestone&lt;/strong>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;strong>Duration Estimate (calendar days)&lt;/strong>&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Inception/ Warm-up&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                M0&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Project acceptance and provisioning.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        IBM donation. Project environment established.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Committer meeting. Project organization and plan agreed to.&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                12/23/2005&lt;br />&#xD;
                1/15/2005&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                24 days&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Elaboration&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                M1&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Legal process to be completed by initial committers&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Train all committers.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Provision project, set up website, mailing lists, etc.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Agree on structure of OpenUP; agree on how to structure of OpenUP into work units, principles and&#xD;
                        resources to evolve each unit.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Identify outreach activities&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                1/16/2006&lt;br />&#xD;
                2/28/2006&lt;br />&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                43 days&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Elaboration&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                M2&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Naming convention agreed to&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Agree to key structural information for OpenUP (e.g. tasks, work products, etc. defined)&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Engage with additional contributors&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Agree on user experience and have a few examples for OpenUP&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Validate extensibility / composibility of OpenUP&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                3/1/2006&lt;br />&#xD;
                4/15/2006&lt;br />&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                45 days&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Elaboration&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                M3&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Identify an initial set of key promoters presenting at conferences, writing blogs and articles,&#xD;
                        etc.&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Agree on general structure of OpenUP&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                4/15/2006&lt;br />&#xD;
                5/31/2006&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                45 days&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Construction&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                M4&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Produce realistic plans for M5&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Agree on a management process&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Have all structural content decisions taken&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Have 30% of content ready for review&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Plan Agile2006, SD Best Practices, and other outreach activities&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                6/1/2006&lt;br />&#xD;
                7/16/2006&lt;br />&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                45 days&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Construction&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                M5&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Finalize structure&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Improve usability and first impression&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Review 30% of content&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Make additional 30% of content available for review&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Establish a functioning management process for the project&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Establish a review board&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Produce initial draft collateral for EPF 1.0 launch&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Make preview at Agile 2006 successful&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Start to build a user community. Identify 2 pilot projects.&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                7/17/2006&lt;br />&#xD;
                8/4/2006&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                21 days&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Construction&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                M6&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        Improve usability and first impression&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Have 60% of content reviewed&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Make the final 40% of content available for review&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Produce more draft collateral for EPF 1.0 launch&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Continue building a user community&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                8/7/2006&lt;br />&#xD;
                9/1/2006&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                28 days&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
        &lt;tr>&#xD;
            &lt;td>&#xD;
                Transition / End Game&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                M7&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                &lt;ul>&#xD;
                    &lt;li>&#xD;
                        End game&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Finalize content 0.9&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Finalize launch collateral&#xD;
                    &lt;/li>&#xD;
                    &lt;li>&#xD;
                        Plan next release&#xD;
                    &lt;/li>&#xD;
                &lt;/ul>&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                9/4/2006&lt;br />&#xD;
                9/29/2006&#xD;
            &lt;/td>&#xD;
            &lt;td>&#xD;
                28 days&#xD;
            &lt;/td>&#xD;
        &lt;/tr>&#xD;
    &lt;/tbody>&#xD;
&lt;/table>&#xD;
&lt;h3>&#xD;
    &lt;br />&#xD;
    5 Deployment&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    N/A.&#xD;
&lt;/p>&#xD;
&lt;h3>&#xD;
    6 Lessons Learned&#xD;
&lt;/h3>&#xD;
&lt;p>&#xD;
    N/A.&lt;br />&#xD;
    &lt;br />&#xD;
    &lt;br />&#xD;
&lt;/p>&lt;br />&#xD;
&lt;br /></mainDescription>
</org.eclipse.epf.uma:GuidanceDescription>