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