Initiating a project is where it all starts in PRINCE2. This is the phase where you start working out who is going to do what. You also put in place all the required elements to make sure the project goes smoothly. The Initiating a Project process is designed to “establish solid foundations” according to the manual. Essentially, this is the part where you make sure that everyone knows what they need to do and that there is a common agreement on the project objectives and the rationale for undertaking the work.
There are a lot of items to set up in the Initiating a Project process, although if you have managed a project with PRINCE2 before you’ll just need to get out the versions you did for those projects and tweak them to suit this new one. No sense in reinventing the wheel.
In my opinion, the four most important parts of this process are putting in place the approach to deal with issues and changes as they arise. That means having:
- a Risk Management Strategy
- a Configuration Management Strategy
- a Quality Management Strategy, and;
- a Communications Management Strategy.
For each of these you need to work out who is going to:
- approve the strategy (A)
- review the strategy (R); and
- produce the strategy (P).
The responsibilities for each member of the project team are shown in the table below. Remember that the Config Management Strategy is where your issues register sits.
All the posts in the Inside PRINCE2 series:
- Inside PRINCE2: Tolerances
- Inside PRINCE2: Fixed date projects
- Inside PRINCE2: Working with APMP
- Inside PRINCE2: Closing a project
- Inside PRINCE2: Who does what in project Initiation
- Book review: Directing Successful Projects with PRINCE2
- Book review: Managing Successful Projects with PRINCE2
- 6 Reasons To Use Your pm4success Subscription
- What software works with PRINCE2?
- PMP and PRINCE2 working together