| <?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.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="-JZkT6zDhNVbrcXx8vHOvBQ" name="new_template,_vb78EF3dEd-8pIBWBGuz7w" guid="-JZkT6zDhNVbrcXx8vHOvBQ" changeDate="2010-05-17T01:50:35.000-0700" version="7.5.0"> |
| <mainDescription><h3 align="center"> |
| &lt;Project Name&gt; - Development Case |
| </h3> |
| <h3> |
| 1. Introduction |
| </h3> |
| <p> |
| <em><font color="#0000ff">[The introduction of the <b>Development Case</b> provides an overview of the entire document. |
| It includes the purpose, scope, definitions, acronyms, abbreviations, references, and overview of this Development |
| Case.]</font></em> |
| </p> |
| <h4 class="Section2"> |
| 1.1 Purpose |
| </h4> |
| <p> |
| <em><font color="#0000ff">[Specify the purpose of this <b>Development Case.</b>]</font></em> |
| </p> |
| <h4 class="Section2"> |
| 1.2 Scope |
| </h4> |
| <p> |
| <font color="#0000ff"><em>[A brief description of the scope of this <b>Development Case</b>; what Project(s) it is |
| associated with and anything else that is affected or influenced by this document.]</em></font> |
| </p> |
| <h4> |
| 1.3 Definitions, Acronyms, and Abbreviations |
| </h4> |
| <p> |
| <font color="#0000ff"><em>[This subsection provides the definitions of all terms, acronyms, and abbreviations required |
| to properly interpret the <b>Development Case</b>. This information may be provided by reference to the project's |
| Glossary.]</em></font> |
| </p> |
| <h4> |
| 1.4 References |
| </h4> |
| <p> |
| <font color="#0000ff"><em>[This section is <b>optional</b>. Alternatively to having an explicit references section |
| using the table below, write down the full name of the document you are referring to in-line with the text where if |
| first appears, then add a hyperlink to the location where the referenced element is stored, and add a acronym (between |
| parenthesis) right after the first appearance of that reference. On subsequent appearances of that reference, use the |
| acronym only.</em></font> |
| </p> |
| <p> |
| <font color="#0000ff"><em>If you use this section, provide a complete list of all documents referenced elsewhere in the |
| <b>Development Case</b>. Identify each document by title, report number (if applicable), date, and publishing |
| organization. Specify the sources from which the references can be obtained. This information may be provided by |
| reference to an appendix or to another document.</em></font> |
| </p> |
| <p> |
| <font color="#0000ff"><em>NOTE: Be sure to include a reference to the version of the organizational process this |
| development case is based on.]</em></font> |
| </p> |
| <div class="Section2"> |
| <table class="MsoTableGrid" cellspacing="0" cellpadding="0" border="1"> |
| <thead> |
| <tr> |
| <td class="Normal" valign="top" width="208" bgcolor="silver"> |
| <p> |
| <b>Reference Name</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="211" bgcolor="silver"> |
| <p> |
| <b>Owner/Author</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="208" bgcolor="silver"> |
| <p> |
| <b>Where Stored</b> |
| </p> |
| </td> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td class="Normal" valign="top" width="208"> |
| <p> |
| <em><font color="#0000ff">[Source Process: Identify the process you are using as the base for this |
| development case.]</font></em> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="211"> |
| <br /> |
| <br /> |
| </td> |
| <td class="Normal" valign="top" width="208"> |
| <br /> |
| <br /> |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="top" width="208"> |
| <p> |
| <em><font color="#0000ff">[Identify the Work Products Addendum to this development case - if |
| addendum is used.]</font></em> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="211"> |
| <br /> |
| <br /> |
| </td> |
| <td class="Normal" valign="top" width="208"> |
| <br /> |
| <br /> |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="top" width="208"> |
| <br /> |
| </td> |
| <td class="Normal" valign="top" width="211"> |
| <br /> |
| </td> |
| <td class="Normal" valign="top" width="208"> |
| &nbsp; |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="top" width="208"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="211"> |
| <br /> |
| </td> |
| <td class="Normal" valign="top" width="208"> |
| &nbsp; |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| </div> |
| <h4> |
| 1.5 Overview |
| </h4> |
| <p> |
| <em><font color="#0000ff">[This subsection describes what the rest of the <b>Development Case</b> contains and explains |
| how the document is organized.]</font></em> |
| </p> |
| <h3> |
| 2. Overview of the Development Case |
| </h3> |
| <h4> |
| 2.1 Lifecycle Model |
| </h4> |
| <p> |
| <font color="#0000ff"><em>[Briefly describe the lifecycle model employed by the project including descriptions of the |
| milestones and their purpose. The purpose is to serve as an introduction to the rest of the development case, not to be |
| a project plan.]</em></font> |
| </p> |
| <h4> |
| 2.2 Sample Iteration Plans |
| </h4> |
| <p> |
| <em><font color="#0000ff">[<b>This section is optional</b>. Include sample iteration plans if they will be helpful for |
| your project.</font></em> |
| </p> |
| <p> |
| <em><font color="#0000ff">Your organizational process captured in Method Composer may provide capability patterns that |
| can serve as templates for phase iteration plans. Your organization may have included a delivery process in your |
| published version of the organizational process that can serve as a basis for your iteration plans.</font></em> |
| </p> |
| <p> |
| <em><font color="#0000ff">If you are using a separate project management tool to create project plans, this section is |
| not needed.]</font></em> |
| </p> |
| <h4> |
| 2.2.1 Inception Phase |
| </h4> |
| <p> |
| <em><font color="#0000ff">[List the sample iteration plans used during Inception.]</font></em> |
| </p> |
| <h4> |
| 2.2.2 Elaboration Phase |
| </h4> |
| <p> |
| <em><font color="#0000ff">[List the sample iteration plans used during Elaboration.]</font></em> |
| </p> |
| <h4> |
| 2.2.3 Construction Phase |
| </h4> |
| <p> |
| <em><font color="#0000ff">[List the sample iteration plans used during Construction.]</font></em> |
| </p> |
| <h4> |
| 2.2.4 Transition Phase |
| </h4> |
| <p> |
| <em><font color="#0000ff">[List the sample iteration plans used during Transition.]</font></em> |
| </p> |
| <h3> |
| 3. Workflow |
| </h3> |
| <p> |
| <em><font color="#0000ff">[This section describes the workflow of each of the development phases in your project |
| lifecycle. For each phase, identify or describe the standard workflow that is used on this project. Following are some |
| suggested ways to identify or describe the standard workflow:</font></em> |
| </p> |
| <ul> |
| <li> |
| <div> |
| <em><font color="#0000ff">The delivery process in your published organizational process includes activity |
| diagrams for each development phase. You can copy and paste those diagrams here or describe how to locate them. |
| Use the 'Notes on Workflow' section to document differences for your project.</font></em> |
| </div> |
| </li> |
| <li> |
| <div> |
| <em><font color="#0000ff">More difficult: rework the activity diagrams to accurately reflect the workflow that |
| your project follows. In this case, there is no need for the 'Notes on Workflow' section, so it can be |
| removed.]</font></em> |
| </div> |
| </li> |
| </ul> |
| <h4> |
| 3.1 Inception Phase |
| </h4> |
| <h5> |
| 3.1.1 Notes on Inception Phase Workflow |
| </h5> |
| <p> |
| <em><font color="#0000ff">[Describe any changes made to the standard workflow for this phase. Typical changes include |
| adding or removing activities or tasks to describe project-specific ways of working.]</font></em> |
| </p> |
| <h4> |
| 3.2 Elaboration Phase |
| </h4> |
| <h5> |
| 3.2.1 Notes on Elaboration Phase Workflow |
| </h5> |
| <p> |
| <em><font color="#0000ff">[Describe any changes made to the standard workflow for this phase. Typical changes include |
| adding or removing activities or tasks to describe project-specific ways of working.]</font></em> |
| </p> |
| <h4> |
| 3.3 Construction Phase |
| </h4> |
| <h5 class="Section2"> |
| 3.3.1 Notes on Construction Phase Workflow |
| </h5> |
| <p> |
| <em><font color="#0000ff">[Describe any changes made to the standard workflow for this phase. Typical changes include |
| adding or removing activities or tasks to describe project-specific ways of working.]</font></em> |
| </p> |
| <h4> |
| 3.4 Transition Phase |
| </h4> |
| <h5> |
| 3.4.1 Notes on Transition Phase Workflow |
| </h5> |
| <p> |
| <em><font color="#0000ff">[Describe any changes made to the standard workflow for this phase. Typical changes include |
| adding or removing activities or tasks to describe project-specific ways of working.]</font></em> |
| </p> |
| <h3 style="PAGE-BREAK-BEFORE: always"> |
| 4. Work Products |
| </h3> |
| <p> |
| <em><font color="#0000ff">[A work product is an artifact, outcome, or deliverable. Provide a list of work products to |
| be produced for the project, when the work product is created and completed, along with details of how the work product |
| is reviewed (when appropriate), who reviews and approves the work product (RACI responsibility matrix) what template is |
| used to create the work product, where the work product is kept or what tool is used to manage it. This can be |
| accomplished by embedding a work product addendum to the development case, such as in spreadsheet format. |
| Alternatively, you may use another method to provide the list of work products, either in this document or as an |
| addendum to this document.</font></em> |
| </p> |
| <p> |
| <em><font color="#0000ff">Note that if you keep the work products to be produced separately from this document (for |
| example, using an addendum spreadsheet), you must be sure to maintain proper document control of the |
| information.]</font></em> |
| </p> |
| <p class="MsoBodyText"> |
| NOTE: The work product addendum is considered to be a part of this development case. The two documents are reviewed and |
| approved as if they were one document. |
| </p> |
| <h3> |
| 5. Reports |
| </h3> |
| <p> |
| <em><font color="#0000ff">[List any reports that are useful for this project. Describe who uses the report and how it |
| can be created.]</font></em> |
| </p> |
| <div class="Section2"> |
| <table class="MsoTableGrid" cellspacing="0" cellpadding="0" border="1"> |
| <thead> |
| <tr> |
| <td class="Normal" valign="top" width="209" bgcolor="silver"> |
| <p> |
| <b>Report</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="209" bgcolor="silver"> |
| <p> |
| <b>Audience</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="209" bgcolor="silver"> |
| <p> |
| <b>How Created/ Where Stored</b> |
| </p> |
| </td> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td class="Normal" valign="top" width="209"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="209"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="209"> |
| &nbsp; |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="top" width="209"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="209"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="209"> |
| &nbsp; |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| </div> |
| <h3 style="PAGE-BREAK-BEFORE: always"> |
| 6. Roles |
| </h3> |
| <p> |
| <em><font color="#0000ff">[This section is used for the following purposes:</font></em> |
| </p> |
| <ul> |
| <li> |
| <div> |
| <em><font color="#0000ff">To describe any changes in the set of roles; for example, it is common to refine the |
| role stakeholder into more than one role.</font></em> |
| </div> |
| </li> |
| <li> |
| <div> |
| <em><font color="#0000ff">To map job positions in the organization to the roles in the organizational process. |
| The reason for this is that in some development organizations there are job positions defined. If these job |
| positions are commonly used and have a wide acceptance within the organization, it may be worth doing a mapping |
| between the roles in the process and the job positions in the organization. Mapping job positions to roles |
| makes it easier for people in the organization to understand how to employ the process. The mapping can also |
| help people understand that roles are not job positions, a common misconception.</font></em> |
| </div> |
| </li> |
| </ul> |
| <p> |
| <em><font color="#0000ff">Explanation of columns:</font></em> |
| </p> |
| <ul> |
| <li> |
| <div> |
| <em><font color="#0000ff">Role: Identify the roles used on your project. For example, it is common to refine |
| the role stakeholder into more than one role. You might need to add new roles or clarify how each role is used |
| in the organization by providing role names commonly used in your organization</font></em> |
| </div> |
| </li> |
| <li> |
| <div> |
| <em><font color="#0000ff">Process Role: <b>Y</b> if this is a role identified in the organizational process; |
| <b>N</b> if it is not defined in the process.</font></em> |
| </div> |
| </li> |
| <li> |
| <div> |
| <em><font color="#0000ff">Applicability: Use this column to map job positions in the organization to the roles |
| in the organizational process.</font></em> |
| </div> |
| </li> |
| <li> |
| <div> |
| <em><font color="#0000ff">Responsibilities: Describe any differences in responsibilities in the organization |
| from those described in the process.]</font></em> |
| </div> |
| </li> |
| </ul> |
| <p class="Body"> |
| NOTE: The assignment of specific individuals to particular roles or job positions is documented in the Project Plan. |
| </p> |
| <div class="Section2"> |
| <table class="MsoTableGrid" cellspacing="0" cellpadding="0" width="631" border="1"> |
| <thead> |
| <tr> |
| <td class="Normal" valign="top" width="128" bgcolor="silver"> |
| <p> |
| <b>Role</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="57" bgcolor="silver"> |
| <p> |
| <b>Process Role</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="183" bgcolor="silver"> |
| <p> |
| <b>Applicability</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="263" bgcolor="silver"> |
| <p> |
| <b>Responsibilities Different from Process</b> |
| </p> |
| </td> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td class="Normal" valign="bottom" width="128"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="57"> |
| <br /> |
| </td> |
| <td class="Normal" valign="top" width="183"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="263"> |
| &nbsp; |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="bottom" width="128"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="57"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="183"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="263"> |
| &nbsp; |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| </div> |
| <h3> |
| 7. Project-Specific Guidelines and Procedures |
| </h3> |
| <p> |
| <em><font color="#0000ff">[Identify any guidelines and procedures used by the project that are not included in the |
| organizational process. These should include any special review procedures, style or coding guidelines, etc. Modify the |
| suggested table to fit your needs.]</font></em> |
| </p> |
| <div class="Section2"> |
| <table class="MsoTableGrid" cellspacing="0" cellpadding="0" border="1"> |
| <thead> |
| <tr> |
| <td class="Normal" valign="top" width="167" bgcolor="silver"> |
| <p> |
| <b>Guideline or Procedure</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="151" bgcolor="silver"> |
| <p> |
| <b>Owner</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="159" bgcolor="silver"> |
| <p> |
| <b>Used by</b> |
| </p> |
| </td> |
| <td class="Normal" valign="top" width="161" bgcolor="silver"> |
| <p> |
| <b>Where Stored</b> |
| </p> |
| </td> |
| </tr> |
| </thead> |
| <tbody> |
| <tr> |
| <td class="Normal" valign="top" width="167"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="151"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="159"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="161"> |
| &nbsp; |
| </td> |
| </tr> |
| <tr> |
| <td class="Normal" valign="top" width="167"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="151"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="159"> |
| &nbsp; |
| </td> |
| <td class="Normal" valign="top" width="161"> |
| &nbsp; |
| </td> |
| </tr> |
| </tbody> |
| </table> |
| </div></mainDescription> |
| </org.eclipse.epf.uma:GuidanceDescription> |