- Phase 1: Initiating
It is recommended that a Project Initiation Document (PID) is created, that outlines what´s the purpose of the project, as well the main requirements. The truth is that this phase also works to create the right mindset towards the project: you should not start something going deep into the technical issues, rather you should start creating and overview that helps identifying if the project is feasible or not. Because Project Phases are so important, you will not be able to jump to the Planning phase until the project has been officially authorised (in Phase 1, Initiating). Most of the actions within the App are blocked during the phase of initiating. This will help the user to get acquainted with this section of the App from the very beginning.
- Phase 2: Planning
This phase might be considered the most important, since it contains all the work to be carried out, together with the necessary resources, so that the project can be accomplished. The goals of the project are defined here (there are many different methodologies to set up goals, such as SMART or OKR). The scope is also defined in this phase. Ultimately, the baseline of the project is set to track the performance of the project in the next phase. If you do a further research about this specific phase, you will find plenty of literature, where the following is recommended:
- Scope Statement.
- Work Breakdown Structure
- Project Timeline.
- Phase 3: Execution
It is time to get your hands dirty, and make it happen. All the different stakeholders should be aware of their responsibilities, which are shared in the so-called “kick-off meetings”. A list of items that are executed during this phase:
- Tasks assignments.
- Modify project plans (when required).
- Phase 4: Monitoring & Controlling
Although listed as a different phase, it normally occurs simultaneously to Execution phase. It is of extreme importance that the project is monitored, and output values must be compared with those produced during the Planning phase. Any change in the scope must be added as a change order, with the repercussion on task assignments, budgets, etc.
- Phase 5: Closing
Like the Initiating phase, this is also an underestimated phase. The final outcome should be evaluated, analysing project failures as well successes, and putting this together in the learnt lessons for future reference. Final reports can be produced, comparing the planned project with the executed project, metrics, listing changing orders, etc.