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