PROJECT IMPLEMENTATION PHASES
This phase includes:
Defining project scope. This includes defining, at a high level, what the system will do. Equally important is to define what the system will not do. This establishes the boundaries within which the team will operate. This usually tales the form of a list of high-level features and/or point form use cases.
Estimate cost and schedule. At a high level, the schedule and cost of the project are estimated. General estimates are used for iterations in later phases, more specificity is used for the early iterations in Elaboration. This should not be construed as meaning that the entire project is planned out at this point. As with all planning, those tasks that are to be completed in the near future are detailed more accurately and with greater confidence while tasks further down the line are understood to be estimates with larger margins of error. It has (finally) been recognized by most in the industry that it is not possible to schedule an entire project at its kick-off with any acceptable degree of confidence. The best that can be done is to plan for the near term accurately and the longer term as best as you can.
Define risks. The risks to the project are first defined here. The list of risks is a living compilation that will change over time as risks are identified, mitigated, avoided and/or materialize and dealt with. Risks drive the management of the project, as the highest priority risks drive the scheduling of iterations.
The purpose of this phase is to establish the baseline of the architecture of the system and provide a stable basis for the bulk of the development effort in the next phase.
There are objectives for the Elaboration phase that helps to address risks associated with requirements, architecture, costs, and schedule:
Get a more detailed understanding of the requirements. Having a good understanding of the majority of requirements enables us to create a more detailed plan and to get buy-in from stakeholders. We ensure to gain an in-depth understanding of the most critical requirements to be validated by the project.
Design, implement, validate, and establish the baseline for the project. Design, implement and rest a skeleton structure of the system. Although the functionality is not complete yet, most of the interfaces between the building blocks are implemented and tested.
Mitigate essential risks, and produce accurate schedule and cost estimates. Many technical risks are addressed as a result of detailing the requirements and of designing, implementing, and testing the project/promotion. Refine and detail the high-level promotion plan.
Project Planning Phase involves creating a set of plans to help guide the team through the execution and closure phases of the project. The plans created during this phase will help you to manage time, cost, quality, change, risk and issues. They will also help you manage staff and external suppliers, to ensure that you deliver the project on time and within budget.
The Project Execution Phase is usually the longest phase of the project lifecycle and it typically consumes the most energy and the most resources. To enable monitor and control the project during this phase, we implement a range of management processes. These processes help you to manage time, cost, quality, change, risks and issues. They also help you to manage procurement, customer acceptance and communications.
This Project feedback Phase helps to:
- Document the results of the Project Management Review.
- Clearly, communicate the progress of your project to the sponsor.
- List any risks or issues which have impacted the project.
- Shows the sponsor the deliverables produced to date.
- Seek approval to proceed to the next phase i.e the technical phase.