In order to make informed decisions and exercise control over a project the project manager needs to know what has happened and be able to compare this against what was planned to happen. It is vital that there is a steady, accurate and regular flow of information from the work streams to the project manager. The template we have provided can enable the project manager to do this.
To provide the project board with a summary of the stage status within a project at intervals as defined in the project initiation document.The report could provide details on the: current status of the schedule, the budget status, summary of issues, problems and risks, status of work completed to date and work to being completed during the next period.
This plan is used to track the realisation of benefits across the project or programme.
Many of the anticipated benefits will not start to materialise until after the project has been delivered. It is therefore essential that the ownership of the benefits realisation plan is maintained beyond project delivery through to complete realisation. The project or programme should allow time to include a post implementation review, thereby allowing time for analysis of the management of benefits realisation and a proper comparison to the original business case.
The Project Quality plan is usually part of the Project Initiation Document (PID).
The purpose is to define the quality techniques and standards to be applied and the various responsibilities for achieving the required quality levels, during the project.
The Risk log is used to list all the identified risks against a project or programme and the results of their analysis and evaluation. Information on the status of the risk is also included. The Risk log can also be known as the risk register. These details can then be used to track and monitor their successful management as part of the activity to deliver the required, anticipated benefits.
The Stakeholder Map identifies all interested parties both inside and outside the programme and may also include individuals or groups outside the business.
The purpose of the map is to ensure that all stakeholder interests are catered for by the programme, including keeping them informed and receiving feedback.
In PRINCE2 project issues are any matter that has brought to the attention of the project and requires an answer. Issues should be allocated a unique reference number and evaluated in terms of impact on that which is being produced, effort, costs and risks. , project plan and business case. Issues may have a positive or negative impact on the project and may need to be referred to the Project Board. Keeping an issue log means that you have a handle on all the issues that arise during the project.
There will often be changes to a project and it is advisable to implement a system that logs any potential changes, and ensures that, where necessary, you assess the effect it might have on delivery. Following a process means that the changes and their impact will be communicated and, hopefully, understood by the project sponsor, stakeholders and other members of the project team.
The End of Project Report is the Project Manager's report to the SRO/Project Owner detailing how well the project has performed against its Project Initiation Document (PID). It should also contain information on how it compares to the original planned cost, schedule and risk allowances, the revised business case and final version of the project plan.
Risk management is key to successful delivery. A risk is any event that could cause the project to be thrown off course. To manage and mitigate risks, you need to try and identify them, assess the likelihood of them happening and the impact they might have on your project. Creating and completing a Risk Register can help identify, manage mitigate or eliminate the risks.