Risk-Value Lifecycle |  |
This practice aligns the project around four phases (Inception, Elaboration, Construction, and Transition). Each phase has specific goals and risks to be addressed that drive the project towards a successful completion. Milestones at the end of each phase validate mitigation of the risks addressed in the phase, as well as the value achieved.
Relationships
Contents | How to Adopt This Practice Risk-Value Lifecycle Phases Guidances
Main Description
The Risk-Value Lifecycle practice supplements the Iterative Development and Two-Level Planning Practices with the Unified Process Lifecycle. This lifecycle identifies four phases, each of which attempts to balance value provided against risk mitigation appropriate to the phase. [***.......TO BE COMPLETED ***] ### The Essence of the Risk-Value Lifecycle The following capture the key principles of Risk-Value Lifecycle: Inception Phase focuses on identifying the objectives of the project and mitigating risks associated with this goal. Elaboration Phase focuses on solidifying the architecture for the system being built and mitigaing risks associated with this goal. Production of executable examples of the most risky elements of the architecture is included. Construction Phase focuses on actually building the system, culminating in the first beta-level versions of the entire system. Transition Phase focuses on incorporating feedback from early customer evaluations of the system and preparing the entire system for final product release, including end-user materials and distribution. ### Why Adopt this Practice? [*** Include some content here that describes the business value of this practice -- what do you get when you adopt it? This section is essentially the value proposition for the practice. You may want to describe some common problems and how this practice solves those problems. ***] ### How to Read this Practice The best way to read this practice is to first familiarize yourself with its overall structure -- what it is in it and how it is organized. [*** To be completed.... ***] For step-by-step instructions on how to adopt this practice, see How to Adopt This Practice. ### Additional Resources For more information on the whole team approach, see the following: [*** Add more, as needed ***] #### Dependencies on other practices This practice provides additional guidance to the following practices: Iterative Development Bi-Level Project Planning
This program and the accompanying materials are made available under the Eclipse Public License v1.0 which accompanies this distribution. OpenUP Copyright.