| | 29 | |
| | 30 | == Inception Phase == |
| | 31 | The following is based on the [http://www.ambysoft.com/unifiedprocess/agileUP.html Agile Unified Process] and is a plan for the first phase of the project, the inception phase. |
| | 32 | |
| | 33 | === Model === |
| | 34 | |
| | 35 | ==== Initial Requirements Modelling ==== |
| | 36 | |
| | 37 | * Use Model - use cases or user stories |
| | 38 | * Domain Model - simple class diagram |
| | 39 | * UI Model - Essential UI prototype/screen sketches/UI flow diagram |
| | 40 | |
| | 41 | ==== Initial Architecture Modelling ==== |
| | 42 | * Free-form diagrams |
| | 43 | * Domain models |
| | 44 | * Change cases (change case, likelihood, impact |
| | 45 | |
| | 46 | === Implementation === |
| | 47 | * Technical prototyping |
| | 48 | * User interface prototyping |
| | 49 | |
| | 50 | === Test === |
| | 51 | * Initial test planning |
| | 52 | * Review initial project management work products |
| | 53 | * Review initial models |
| | 54 | |
| | 55 | === Deployment === |
| | 56 | * Identify the potential release window |
| | 57 | * Begin high-level deployment planning |
| | 58 | |
| | 59 | === Configuration management === |
| | 60 | * Setup the configuration environment |
| | 61 | * Put all work products under CM control |
| | 62 | |
| | 63 | === Project management === |
| | 64 | * Start building the team |
| | 65 | * Build relationships with project stakeholders |
| | 66 | * Determine project feasibility |
| | 67 | * Develop a high-level schedule for the entire project |
| | 68 | * Develop a detailed iteration plan for the upcoming iteration |
| | 69 | * Manage risk - define risks and plan for dealing with them |
| | 70 | * Obtain stakeholder support and funding |
| | 71 | * Close out the phase |
| | 72 | |
| | 73 | === Environment === |
| | 74 | * Set up the working environment |
| | 75 | * Identify the project category |
| | 76 | |
| | 77 | At end of inception phase, have a milestone review to determine whether the "Lifecycle Obectives" milestone has been met: |
| | 78 | |
| | 79 | * Scope concurrence = stakeholders reach agreement on scope of project |
| | 80 | * Intial requirements definition - an agreement that the right set of requirements have been captured and that they are understood |
| | 81 | * Plan concurrence - stakeholders agree with initial cost and schedule estimates |
| | 82 | * Risk acceptance - Risks have been identified, assessed and acceptable strategies to address them have been identified |
| | 83 | * Process acceptance - Process has been agreed by all parties |
| | 84 | * Feasibility - project makes sense from business, technical and operational perspectives |
| | 85 | * Project plan - adequate plans are in pkace for the next phase (Elaboration) |
| | 86 | * Portfolio compliance - does the scope fit will into organisation's overall project portfolio? |
| | 87 | |
