Project Planning

The purpose of project planning is to facilitate communication and control by defining the means of delivering the products (the where and how, by whom, and estimating the when and how much).

Compliance

Yes

- There is evidence that the project complies to the criteria

- There is no evidence that the project complies to the criteria

N/A

- This criteria does not apply via the use of tailoring or other justifiable reasons

Quality

Red

- The is no evidence or the evidence does not comply with the PRINCE2 methodology

Amber

- The evidence is reasonable, but could benefit from significant improvement to comply fully with PRINCE2

Green

- The evidence complies fully with PRINCE2

N/A

- This criteria does not apply via the use of tailoring or other justifiable reasons

SU IP PL SB CS MP DP CP Report
Planning
Project Name:	Please enter a project name, this will be used to load and save your data, so please remember it!

	Criteria Question	Compliance	Quality
Pre Planning activities
	Is there a baseline project plan?
	Are stages clearly defined?
	Are there stage plans?
	Are stage plans Consistent with the project plan?
Designing a Plan
	Was a plan methodology defined? (Indicating planning approach, levels of Plan, estimating techniques and approach to contingency allowances, tool set to be used and major monitoring methods, and any relevant assumptions)
Defining and Analysing Products
	Has a product based planning technique been used?
	Is there a product breakdown structure?
	Is there a product check list of key products?
	Are there product descriptions?
	Is there a product flow diagram?
	Are there product descriptions to PRINCE 2 standard format?
	Are quality criteria explicit?
	Are quality methods defined?
	Are quality check skills defined?
	Is it clear who delivers and accepts and checks the products?
	Has each product description resulted in a documented configuration item record?
	Are product descriptions subject for QA review?
	Do assurance roles review product descriptions?
	Are product descriptions reviewed and updated to reflect authorised changes?
	Are product descriptions maintained under configuration management?
Identifying activities and dependencies
	Is there a list of activities?
	Have dependencies between activities and products been identified?
	Have external project dependencies with activities and products been identified in the plan?
Estimating
	Have activities and time scales been captured in the plan?
	Have estimating techniques and assumptions been identified?
Scheduling
	Have activities been scheduled in the plan?
	Have activates been assigned to individuals?
	Has the resource usage been levelled?
	Have project control points been identified?
	Have milestones been identified?
	Has the production of management products been included?
	Have project assurance activities been included in the plan?
	Have the resources and costs been calculated and documented?
Analysing Risks
	Have assumptions in the plan resulted in risks being documented in the risk log?
	Have Risks associated with the plan been captured in the risk log?
Completing a Plan
	Have all the planning products been consolidated into a single document?
	Has the format of the plan's presentation material been agreed with the project board?
Approvals & Quality Assurance
	Have the Plans (project or Stage) been subject to a documented QA Review?
	Have the Plans (Project or Stage) been Approved by the Project Board and authorisation given for the Project or Stage to proceed?
	Is the baseline project plan subject to configuration control and management?
	Is the current project plan up to date?
	Are Project check point reviews planned to confirm the project is on track?
	Does the plan include management products?
	Does the plan include project specialist products?
	Does the plan include QA review schedule?
	Does the plan include key communication activity?
	Does the plan include checkpoints to confirm the project is on track?

Maturity Model Rating For This Phase
Level 1 - Initial • Methodology is not being adopted • Project success very unpredictable Level 2 - Managed • Partial adoption of methodology • Project success unpredictable Level 3 - Defined • Variable adoption of methodology • Some project predictability Level 4 - Quality • Good adoption of methodology • Projects generally predictable Level 5 - Optimised • Full adoption of methodology • Project very predictable
Phase Analysis