See more
en
4 main phases of project implementation
The vast majority of the primary project management methodologies – Prince2, PMP – distinguish four main phases of project implementation:
-
initiation phase
-
planning phase
-
implementation phase
-
closure phase
Setting up a project management process in a company that considers all the phases listed makes a lot of sense and brings many benefits. Similar to the Stage-Gate methodology, when a particular phase of a project ends, there is a decision gate where a decision is made to continue the project, and a plan for the next phase is approved. In a sense, the same is true of the four main project implementation phases mentioned. Once the initiation phase has been realized, a decision is made about the project’s attractiveness to the company, and the planning phase begins. In this way, the company consciously and structurally builds its project portfolio, and only some things happen haphazardly. In the next section of this article, we will discuss each phase separately.
Phase 1–project initiation
This phase may have a different name depending on the organization. The most common names are the initiation, idea, or initiative phase. However, regardless of the name, this is virtually always the moment when an idea for a potential project begins to take shape. In many organizations, project ideas are collected. Companies make the correct assumption that the company’s employees are creative, and this potential for creativity must be used for the company’s development. Ideas are collected in very different ways. It can be a list kept in Excel, or the company has a dedicated IT program for collecting ideas. A simple form is used to describe the idea in such a system. Equally, the idea-collection process itself varies between companies. In some organizations, an employee with an idea for a potential project must first discuss it with his or her supervisor, and only after approval is given is the project idea placed in the system. Often, ideas are evaluated through appropriate scoring models. The illustration below from a project and portfolio management program shows the attractiveness of projects and ideas on a matrix.
Attractiveness of projects and ideas on a matrix in FlexiProject app
A description of a potential project idea often consists of the following elements:
- Name of the project
- What problem/challenge does the project address
- Benefits of the project
- Results after project implementation
- Proposed project manager
- Estimated project duration
- Estimated project budget
- Potential risks
- Main tasks to be carried out in the project
Phase 2–planning
The quality of the project plan developed significantly impacts the project’s outcome. The project assumptions described in the idea sheet must be clarified at this stage. The Project Charter is most often used for this purpose. The illustration below shows an example of a Project Charter from the project and portfolio management software FlexiProject.
Example of a Project Charter
The key elements that the project team should focus on when developing the Project Charter are:
- A detailed description of the problem/challenge to be addressed by the project
- A detailed description of the project’s business objective
- Requirements of the main project stakeholders
- A detailed description of the project deliverables/outputs
- A detailed description of the project scope
- Indication of the strategic objective to be addressed by the project
- What competencies are needed to realize the project
- The most crucial project risks
- The main project milestones
The Project Charter prepared in this way should be formally accepted.
Once the Project Charter is accepted, the project team can proceed to create further elements of the project plan: stakeholder analysis, description of partial and final project deliverables, project schedule, project budget, project risk register, or resource plan. There are different approaches to the creation of the elements mentioned above in the project plan, but among the most effective are the following:
- developing a Project Charter
- detailed definition of project deliverables
- development of key schedule tasks and their link to project deliverables
- refining the schedule – defining tasks, milestones, responsibilities
- development of project budget
- development of the risk register
- development of a resource plan
The following illustration shows an example of a project schedule plan.
Example of a project schedule plan in FlexiProject
When analyzing the above example of a project schedule, it is worth noting the three columns on the right, which show risks, budget, and deliverables. If a risk is associated with a particular schedule task, a triangle icon with an exclamation mark is shown in the task line in the “risks” column. The same applies by analogy to cost items or project outputs. The developed project plan should be formally accepted.
Phase 3–project implementation
The project implementation phase is when the team works to achieve the project goals and deliver the intended results. What you should pay particular attention to during the project delivery phase is:
- Ensuring adequate communication within the project team
- Delivering the main tasks and milestones of the project and assessing the level of progress of the tasks
- Regular analysis of variances from the project plan regarding both project schedule and budget
- Updating the project plan as additional information becomes available
- Changing the project plan using a Change Request document – the figure below shows an example of a Change Request document
Example of a Change Request document
- Regular project meetings to discuss project progress and emerging issues on an ongoing basis
- Regular analysis of project risks and active management of project risks
- Regular meetings and reporting on project status to the steering committee or company management
- Analysis of the workload of project resources and rapid response in cases where the workload of selected resources is excessive
- Delivery of required project deliverables
Phase 4–project closure
Despite being a very important project phase, it is often overlooked. The Project team should develop a formal project closure document called the project closure sheet. An example of a Project Closure Sheet is shown in the figure below.
Customized project Closure Sheet in FlexiProject
When completing the Project Closure Sheet, the project team should detail the post-project conclusions and analyze what went wrong. Such lessons learned are particularly useful in launching and implementing subsequent projects to make them more effective. Such post-project lessons or Lessons Learned allow an organization to build a knowledge base and achieve higher project culture levels. Elements of the Project Closure Charter worth noting are:
- Detailed description of lessons learned
- Description of key risks and problems that occurred in the project
- Description of post-project conclusions
Project implementation stages as the key to effective goal achievement
The likelihood of projects achieving success significantly increases as they are implemented using the four main phases of project execution. The range of activities carried out in each phase depends on the organization’s project maturity and the type of projects undertaken. It is worth noting that each project delivery phase ends with formal project approval.
![What is a Gantt chart, and how to create one? [EXAMPLE]](https://flexi-project.com/wp-content/uploads/2024/04/What-is-Gantt-chart-e1714048900401.png)
![What is a Project Charter and how to prepare it? [EXAMPLE]](https://flexi-project.com/wp-content/uploads/2024/04/Project-charter-flexiproject.png)
