Following on from my previous post, ‘Why do we need Project Documents?‘, it is not necessary to have every piece of project documentation to be completed for every project, although there are some key documents which should ideally be applied to all.
Key PRINCE2 Project Documents
(those highlighted in bold are key)
- Project Brief
- Risk Log
- Project Approach
- Initial Business Case – Refined Business Case (IP)
- Product Descriptions
- Quality Plan/Strategy (M/L projects)
- Project Plan
- End Stage Review (M/L projects)
- Stage Plans (M/L projects)
- Change control process
- Lessons Learned Report
- End of project review (M/L projects).
BANKING AS IT WAS MEANT TO BE | Safety & Privacy Offshore + 100% Deposit Ratio + Full Online Access + Gold & Silver Backed Accounts + Managed Funds + Online Brokerage & More
The level of detail within project documents can and should be tailored to suit the project. For example, a Business Case for a small project may only contain one or two sentences for each heading, whereas a larger project may contain a much greater level of detail (or perhaps additional supporting documents).
The table below lists all the key PRINCE2 project management documents and recommends those required for Small, Medium and Large projects:
|Project Document||Small Project||Medium Project||Large Project|
|Project Brief *||yes||yes||yes|
|Risk Log *||yes||yes||yes|
|Project Approach *||yes||yes||yes|
|Business Case *||yes||yes||yes|
|Project Descriptions *||yes||yes||yes|
|Project Plan *||yes||yes||yes|
|Project Initiation Document (PID) *||yes||yes||yes|
|End Stage Review||no||recommended||yes|
|Change Control Process||no||no||yes|
|Lessons Learnt Report||recommended||yes||yes|
|End of Project Review||recommended||yes||yes|
* Core PRINCE2 project documents – should be compiled as a minimum.