PLANNING – QUALITY CONTROL CHECKLIST

All plans in the Program should be reviewed by the Schedule Manager and verified against the quality control checklist and quality control filter checklist.

 

A written report should be provided by the Schedule Manager to the project managers including a summary of the defects to be rectified in the plans.  Quality control reports should be developed for each Baseline of the program plan and project plans.  The Quality control reports can be filed in the project repository in line with the project configuration policy.

 

 

Item	Quality Criteria Description
1	Milestones
1.1	Is there a milestone section at the top of the plan?
1.2	Have all key milestones been included?
1.3	Do Milestone names provide unambiguous and descriptive definition?
1.4	Do dates of milestones match baseline planned dates in PMP?
1.5	Is Milestone name concise enough to appear uncluttered in Rolled up view? Abbreviations should make sense to staff in the organization not working on the project
1.6	Is there an even spread of milestones across the time periods of the project?
2	WBS
2.1	Does the WBS structure align to the project approach, methodology or standard project lifecycle?
2.2	Does the WBS evenly distribute work effort across the phases and through the WBS levels?
2.3	Is there activities or tasks which would be better placed in other WBS elements?
2.4	Do project plans roll up in an effective manner and are broken down into key work products at level 3?
2.5	Do the key Work Products match the PMP deliverables?
3	Scope
3.1	Is the project scope completely represented in the program plan?
3.2	Do individual project plans completely represent the scope in the program plan?
4	Dependencies and Constraints
4.1	Is there a dependencies section at the top of the plan?
4.2	Have all External project dependencies been included?
4.3	Do all External dependencies have a successor project task?
4.4	Constraints should be set only where absolutely necessary. The MPP should be as dynamic as possible through the use of predecessors and successor logic.
5	Progress Reporting
5.1	Actual Start date is correct if the task has started
5.2	Actual Finish date is correct if the task has finished
5.3	Forecast Start date if the task has not started (date to be populated and in the future)
5.4	Forecast Finish date if the task has not finished (date to be populated and in the future)
5.5	% Work Complete is present and maintained?
5.6	Project One page view appears reasonable (e.g. Reads well etc)?
6	Resourcing
6.1	Tasks have resourcing assigned and resourcing appears reasonably leveled?
6.2	Are there any resource conflicts across phases which could create resource issues for execution?
7	Tasks, Hours, Predecessors, Successors, Approval Points, Naming
7.1	Work hours are spread at task level and total planned hours at the product level are consistent with the earned value reporting system.
7.2	Predecessors and successors do not appear at summary level.
7.3	Tasks and milestones are linked to predecessors and successors.
7.7	Baseline has been saved in the scheduling tool
7.8	Project File Naming convention aligns to Configuration management standard?
8	Critical Path
8.1	Does the schedule tool calculate the critical path through the expected activities/tasks and align to the critical activities noted in the project brief or approach?  If the tool isn’t calculating the expected activities adjustments will be required to the network logic.