| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription 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" xmi:id="-ebKPqn9bWfbh1K2spgOwWQ" |
| name="new_concept,_nSfVwCNYEdyCq8v2ZO4QcA" guid="-ebKPqn9bWfbh1K2spgOwWQ" changeDate="2007-07-11T00:14:01.984-0400"> |
| <mainDescription><p>
 |
| The governance lifecycle provides <em>stakeholders</em> with oversight, transparency, and steering mechanisms to
 |
| control project funding, scope, risk exposure, value provided, and other aspects of the process.
 |
| </p>
 |
| <p>
 |
| Each iteration delivers a product increment, which provides an opportunity for stakeholders to understand what value
 |
| has been delivered and how well the project is tracking. It also gives the development team the opportunity to make
 |
| changes to the project to optimize the outcome.
 |
| </p>
 |
| <p>
 |
| OpenUP organizes iterations into a set of phases. Each phase ends with a milestone aimed at providing oversight by
 |
| raising and answering a set of questions that are typically critical to stakeholders:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| <a class="elementLinkWithUserText" href="./../../../openup/guidances/concepts/inception_phase.html"
 |
| guid="_0hmKgBOMEduCNqgZdt_OaA">Inception</a>. Do we agree on project scope and objectives, and whether or not the
 |
| project should proceed?
 |
| </li>
 |
| <li>
 |
| <a class="elementLinkWithUserText" href="./../../../openup/guidances/concepts/elaboration_phase.html"
 |
| guid="_2plxwBOMEduCNqgZdt_OaA">Elaboration</a>. Do we agree on the executable architecture to be used for
 |
| developing the application and do we find that the value delivered so far and the remaining risk is acceptable?
 |
| </li>
 |
| <li>
 |
| <a class="elementLinkWithUserText" href="./../../../openup/guidances/concepts/construction_phase.html"
 |
| guid="_48EKsBOMEduCNqgZdt_OaA">Construction</a>. Do we find that we have an application that is sufficiently close
 |
| to being released that we should switch the primary focus of the team to tuning, polishing and ensuring successful
 |
| deployment?
 |
| </li>
 |
| <li>
 |
| <a class="elementLinkWithUserText" href="./../../../openup/guidances/concepts/transition_phase.html"
 |
| guid="__ca5UBOMEduCNqgZdt_OaA">Transition</a>. Is the application ready to release?
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| If the answer is Yes to the above questions at the phase review, the project continues. If the answer is No, the phase
 |
| is delayed (usually by adding an extra iteration) until a satisfactory answer is received, or the stakeholders may
 |
| determine that the project should be cancelled.
 |
| </p>
 |
| <p>
 |
| One of the objectives of the governance lifecycle is to focus on two key stakeholder drivers: risk reduction and value
 |
| creation. The OpenUP phases focus the team on risk reduction related to the questions to be answered at the end of the
 |
| phase, while tracking value creation, see Figure 3. Risk is a manifestation of the likelihood of unexpected things
 |
| happening to the project, and risk stands in the way of value creation. Risk is directly proportional to uncertainty in
 |
| estimates, and stakeholders typically want to know sooner rather than later what value the project can deliver in the
 |
| stipulated time. In many cases, you reduce risk when you create value by implementing and testing the most critical
 |
| capabilities. However, there are situations where risk reduction and immediate value creation are at odds with each
 |
| other, see <a class="elementLink" href="./../../../openup/guidances/concepts/core_principle_balance.html"
 |
| guid="_ssG6MMvpEdqukPpotm3DYg">Balance competing priorities to maximize stakeholder value</a>. Let’s look at an
 |
| example;
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| <em>If you get legal approval to leverage an open source reporting capability you can develop your application in 6
 |
| months. With no approval, it will take you 10 months. Spending one week on getting legal go / no-go provides zero
 |
| immediate value to end user in terms of working functionality, but will significantly reduce risk and variance in
 |
| the estimate. It is hence likely worth doing as soon as possible.</em>
 |
| </p>
 |
| </blockquote>
 |
| <p dir="ltr">
 |
| &lt;Figure&gt;&gt;
 |
| </p>
 |
| <p dir="ltr">
 |
| <em>Figure 3: Risk reduction (pale curve) and value (purple curve) during the project lifecycle.</em>
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
