| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:DeliveryProcessDescription xmi:version="2.0" |
| xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.2.0" xmi:id="-dV7s6ZJXratblG37Lbu0mw" |
| name="openup_lifecycle,_SuWj4dOPEdyqlogshP8l4g" guid="-dV7s6ZJXratblG37Lbu0mw" |
| version="7.2.0"> |
| <mainDescription><p>
 |
| OpenUP is an iterative process with <a class="elementlinkwithusertext"
 |
| href="./../../core.mgmt.common.base/guidances/concepts/core_principle_evolve_BFD9AEB4.html"
 |
| guid="_GXiogMvoEdqukPpotm3DYg">iterations</a> distributed throughout four <a class="elementLinkWithUserText"
 |
| href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/phase_85B003C3.html"
 |
| guid="__7xOEC7aEdqHMdmRzC0-2g">phases</a>: <a class="elementLinkWithUserText"
 |
| href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/inception_phase_C4456871.html"
 |
| guid="_0hmKgBOMEduCNqgZdt_OaA">Inception</a>, <a class="elementLinkWithUserText"
 |
| href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/elaboration_phase_BE880435.html"
 |
| guid="_2plxwBOMEduCNqgZdt_OaA">Elaboration</a>, <a class="elementLinkWithUserText"
 |
| href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/construction_phase_873B6559.html"
 |
| guid="_48EKsBOMEduCNqgZdt_OaA">Construction</a>, and <a class="elementLinkWithUserText"
 |
| href="./../../practice.mgmt.risk_value_lifecycle.base/guidances/concepts/transition_phase_DD5986E5.html"
 |
| guid="__ca5UBOMEduCNqgZdt_OaA">Transition</a>.
 |
| </p>
 |
| <p>
 |
| Each phase may have as many iterations as needed (depending on the degree of novelty of the business domain, the
 |
| technology being used, architectural complexity, and project size, to name a few factors).
 |
| </p>
 |
| <p>
 |
| To offer a quick start for teams to plan their iterations, OpenUP provides work breakdown structure (WBS) templates for
 |
| each iteration, and a WBS template for an end-to-end process.
 |
| </p>
 |
| <p>
 |
| Iterations may have variable lengths, depending on project characteristics. One-month iterations are typically
 |
| recommended, because this timeframe provides:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| A reasonable amount of time for projects to deliver meaningful increments in functionality.
 |
| </li>
 |
| <li>
 |
| Early and frequent customer feedback.
 |
| </li>
 |
| <li>
 |
| Timely management of risks and issues during the course of the project.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| OpenUP is intended to offer process guidance to small, co-located teams.
 |
| </p></mainDescription> |
| <purpose><p>
 |
| This delivery process is intended to:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Promote collaboration (both internal and external to the team), to align interests and share understanding
 |
| </li>
 |
| <li>
 |
| Help the team focus on the architecture early, to minimize risks and organize development
 |
| </li>
 |
| <li>
 |
| Help the team balance competing priorities to maximize stakeholder value
 |
| </li>
 |
| <li>
 |
| Help the team evolve the product to continuously obtain feedback and improve
 |
| </li>
 |
| <li>
 |
| <div id="comment_text_7">
 |
| Allow project managers to track status based on goals
 |
| </div>
 |
| </li>
 |
| <li>
 |
| Allow team members to understand how to perform their work to achieve project goals
 |
| </li>
 |
| </ul></purpose> |
| </org.eclipse.epf.uma:DeliveryProcessDescription> |
