| <?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="-pR6ni3h0dcW2muuMCoRzgw" name="development_case_project,_uWZwAF3gEd-8pIBWBGuz7w" guid="-pR6ni3h0dcW2muuMCoRzgw" changeDate="2010-05-17T02:26:20.000-0700" version="7.1.0"> |
| <mainDescription><h3 class="Section1"> |
| The XYZ Project Process |
| </h3> |
| <h3 class="Section1"> |
| 1. Introduction |
| </h3> |
| <h4 class="Section1"> |
| 1.1 Purpose |
| </h4> |
| <p class="MsoBodyText"> |
| This document describes the process followed by project XYZ. |
| </p> |
| <h4 class="Section1"> |
| 1.2 Definitions, Acronyms, and Abbreviations |
| </h4> |
| <p class="MsoBodyText"> |
| See the <u><font color="#0000ff">XYZ Project Glossary</font></u> (XYZ-GLO) for a comprehensive list of terms used on |
| this project. |
| </p> |
| <h4 class="Section1"> |
| 1.3 Overview |
| </h4> |
| <p class="MsoBodyText"> |
| Project XYZ generally follows the <u><font color="#0000ff">Disciplined Agile Delivery for ABC V2.0</font></u> (DAD-ABC) |
| process configuration, which is the default software development process for most projects at Company ABC. |
| </p> |
| <p class="MsoBodyText"> |
| The remainder of this development case addresses how this project deviates from the standard process. It explains how |
| the lifecycle model, discipline workflows, work products usage, and associated roles are customized for the needs of |
| XYZ Project. |
| </p> |
| <h3 class="Section1"> |
| 2. Lifecycle |
| </h3> |
| <p class="Section1"> |
| The XYZ Project modifies the standard lifecycle described in DAD-ABC as follows: |
| </p> |
| <div class="Section1"> |
| <ul type="square"> |
| <li> |
| Drop "Elaboration" phase and the "Lifecycle architecture" milestone, in order to follow a more evolutionary |
| architecture approach. However, weekly project status reporting will report progress on architecture risks. |
| </li> |
| </ul> |
| </div> |
| <p> |
| Thus the phases and milestones will be as follows: |
| </p> |
| <ul type="square"> |
| <li> |
| Inception phase |
| </li> |
| <li style="LIST-STYLE-TYPE: none"> |
| <ul type="circle"> |
| <li> |
| stakeholder consensus achieved |
| </li> |
| </ul> |
| </li> |
| <li> |
| Construction phase: |
| </li> |
| <li style="LIST-STYLE-TYPE: none"> |
| <ul type="circle"> |
| <li> |
| Sufficient functionality |
| </li> |
| </ul> |
| </li> |
| <li> |
| Transition phase |
| </li> |
| <li style="LIST-STYLE-TYPE: none"> |
| <ul type="circle"> |
| <li> |
| Production ready |
| </li> |
| </ul> |
| </li> |
| </ul> |
| <h3> |
| 3. Practices |
| </h3> |
| <p class="MsoBodyText"> |
| Project XYZ follows all the practices in DAD-ABC, with the exception of "Staged Integration". The project is small |
| enough that only a single integration stream is required, and no dedicated integrator role is required. |
| </p> |
| <h3> |
| 4. Work Products |
| </h3> |
| <p> |
| With regards to work products, the XYZ project has some deviations from DAD-ABC as listed below: |
| </p> |
| <ul type="square"> |
| <li> |
| Formal-Internal reviews and approvals are made by the Product Manager role, as opposed to the external Project |
| Review Authority established by the <u><font color="#0000ff">ABC Governance Process</font></u> (ABC-GOV). |
| </li> |
| <li> |
| Globalization Plan is waived: the XYZ product will be initially marketed in North America, and therefore a waiver |
| for translation is requested. |
| </li> |
| <li> |
| Software Architecture Document is not produced; instead, we generate automated reports from our visual modeling |
| tool. |
| </li> |
| <li> |
| Added new artifact for Storyboards, which are maintained in Rational Requirements Composer tool |
| </li> |
| <li> |
| Rational Team Concert tool is used to capture User Stories description and related work. The User Stories in |
| Rational Team Concert are linked to the respective Storyboards in Rational Requirements Composer. |
| </li> |
| </ul> |
| <h3> |
| 5. Reports |
| </h3> |
| <p class="MsoBodyText"> |
| In addition to standard metrics required by ABC-GOV, the Team Lead gathers Requirements Traceability Coverage metrics |
| and use Rational Insight tool to generate them, as there is a need to be aware of high level system requirements that |
| were allocated to and refined by the XYZ project team. |
| </p> |
| <p class="MsoBodyText"> |
| The team lead takes snapshots of all metrics every 2 weeks as opposed to once a month, as indicated by ABC-GOV. |
| </p> |
| <h3> |
| 6. Roles |
| </h3> |
| <p class="MsoBodyText"> |
| Added Course Developer role to the team - as part of the project we need to produce training material. |
| </p> |
| <p class="MsoBodyText"> |
| Team Lead on this project will be referred to as covering both the Project Manager and Architect roles. |
| </p> |
| <p class="MsoBodyText"> |
| Note: The assignment of specific individuals to particular roles or job positions is documented in the <u><font |
| color="#0000ff">XYZ Project Plan</font></u> (XYZ-PPLAN). |
| </p> |
| <h3> |
| 7. Project-Specific Guidelines and Procedures |
| </h3> |
| <ul> |
| <li> |
| <font color="#0000ff"><u>Getting started on the XYZ Development Environment</u></font> |
| </li> |
| <li> |
| <font color="#0000ff"><u>ABC Architectural Guidelines</u></font> |
| </li> |
| <li> |
| <font color="#0000ff"><u>Q Language Programming Guidelines</u></font> |
| </li> |
| <li> |
| <font color="#0000ff"><u>Requirements Management Guidelines</u></font> |
| </li> |
| <li> |
| <font color="#0000ff"><u>Configuration and Change Management Guidelines</u></font> |
| </li> |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:GuidanceDescription> |
