| <?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.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="-GRJW_KNOJoEQF3r6lmBrEw" |
| name=",_0hmKgBOMEduCNqgZdt_OaA" guid="-GRJW_KNOJoEQF3r6lmBrEw" changeDate="2008-07-11T10:14:27.087-0700" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| The purpose in this phase is to achieve concurrence among all stakeholders on the lifecycle objectives for the project.
 |
| </p>
 |
| <p>
 |
| There are four objectives of the Inception phase that clarify the scope, project objectives, and feasibility of the
 |
| intended solution <a class="elementlinkwithusertext" href="./../../../core.mgmt.common.base/guidances/supportingmaterials/references.mgmt_D80619F3.html#KRO03" guid="_JlTPUM6aEdyuBO4ZIzcyig">[KRO03]</a>:
 |
| </p>
 |
| <ol>
 |
| <li>
 |
| 
 |
| <p> <strong>Understand what to build.</strong> Determine an overall vision, 
 |
| including the scope of the system and its boundaries. Identify the stakeholders: 
 |
| who is interested in this system and what are their success criteria?</p>
 |
| </li>
 |
| <li>
 |
| <p>
 |
| <strong>Identify key system functionality.</strong> Decide which requirements are most critical.
 |
| </p>
 |
| </li>
 |
| <li>
 |
| 
 |
| <p> <strong>Determine at least one possible solution.</strong> Assess whether 
 |
| the vision is technically feasible.&nbsp;This may involve identifying a 
 |
| candidate high-level architecture or doing technical prototypes, or both.</p>
 |
| </li>
 |
| <li>
 |
| <p>
 |
| <strong>Understand</strong> the high-level estimate for cost, schedule, and risks associated with the project.
 |
| </p>
 |
| </li>
 |
| </ol>
 |
| <h4>
 |
| Key considerations
 |
| </h4>
 |
| <p> Projects may have one or more iterations in the Inception phase. These are 
 |
| among the reasons for multiple iterations: </p>
 |
| <ul>
 |
| 
 |
| <li> Project is large, and it is hard to define its scope</li>
 |
| 
 |
| <li> Unprecedented system</li>
 |
| 
 |
| <li> Too many stakeholders with competing needs and complex relationships</li>
 |
| 
 |
| <li> Major technical risks demand the creation of a prototype or proof of concept</li>
 |
| </ul>
 |
| <p> There are some commonly observed&nbsp;counterproductive patterns during the 
 |
| Inception phase. Some teams postpone providing estimates until they analyze 
 |
| the entire domain and have written a large amount of requirements documentation. 
 |
| This behavior often leads to &quot;analysis paralysis.&quot; Another pattern 
 |
| is poor planning of Inception iterations. Avoid such patterns by planning iterations 
 |
| during Inception in a way that iterations are risk-driven, include early integration 
 |
| and testing, and produce a product increment that you can demonstrate to stakeholders. 
 |
| By default, have one (potentially short) iteration in Inception to avoid analysis 
 |
| paralysis. </p></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
