INSTRUCTIONS:

(1.) Place a single "x" in the boxes under YES, NO or N/A to answer each schedule
quality assessment. An "x" under YES indicates that the schedule passes the quality
assessment. A NO indicates that some or all of the schedule (a significant portion)
does not pass the quality assessment. An N/A answer indicates that the quality
assessment does not apply to the schedule.
(2.) Only one answer is needed for each quality assessment. There is no validation
routine to prevent multiple answers.
(3.) N/A answers will cause the row to be shaded. This is only used to visually
indicate that the quality assessments was not evaluated.

Project Schedule Quality Control Checklist

The following Quality Control Checklist will help project managers identify all of the ingredients
of a healthy, flexible and dependable project schedule. A "YES" response indicates the
schedule passes the Quality check.
Place an "X" in the appropriate column.
CHECKLIST TOTALS:
1.0 TASKS vs. WBS
Sub-totals:
The schedule's high-level tasks match the Work Breakdown Structure (WBS). The defined WBS
must be reflected in the project schedule. Low-level tasks may be at a detail greater than defined in
the WBS.
2.0 DEPENDENCIES (PREDECESSORS)
Sub-totals:
External dependencies are identified as milestones. Tasks external to the project, thus external to
the control of the project managers, must be listed as external dependencies in the project schedule.
Date constraints should be used to reflect the timing of the external dependency. Other tasks may then
be dependent on the completion of the external dependencies.

Project Name: Project Release 7.00

Project Team:
QC Reviewer:
Review Date:
Green (0-2 No's); Yellow (3-4 No's); Red (>4 No's)
0
0

YES

NO

N/A

YES

NO

N/A

YES

NO

N/A

YES

NO

N/A

YES

NO

N/A

YES

NO

N/A

YES

NO

N/A

YES

NO

N/A

YES

NO

N/A

REVIEWER'S COMMENTS
Green (0 No's); Red (1 No)

REVIEWER'S COMMENTS
Green (0 No's); Yellow (1 No); Red (>1 No)

Every task has a dependency. Excluding date constrained tasks (e.g., weekly meetings) or external
dependencies, tasks must be triggered by the end of a preceding task. This is important for tracking
the "critical path" of the project. The critical path is the chain of task dependencies which have the
longest overall duration. A task may have more than one dependency. High-level tasks do not need
dependencies if the lower-level tasks have them.
Dependencies are linked between sub-project files. Tasks dependant upon another project team's
task are linked to the other project team's sub-project file. This is important for tracking the "critical
path" of the project. The critical path is the chain of task dependencies which have the longest overall
duration.
3.0 CRITICAL MILESTONES
Sub-totals:
Critical milestone dates are identified. Currently, critical milestone dates are identified in the WBS.
Milestones must be dependent upon the completion of at least one scheduled task. Critical milestones
mark the progress of the project plan. Milestones should be highlighted in color for the benefit of the
reader.

REVIEWER'S COMMENTS
Green (0 No's); Yellow (1 No); Red (>1 No)

Milestone tasks have zero duration. Milestones must not have work assigned or a duration other
than zero. Milestone tasks are placeholders that indicate progress or critical points in the schedule.
4.0 RESOURCES
Sub-totals:
Resources are assigned to every subtask. Resources must be entered on every subtask. All low
level tasks that have a defined amount of effort required must have a Resource assigned to perform
the work.

REVIEWER'S COMMENTS
Green (0 No's); Yellow (1 No); Red (>1 No)

Resources are not assigned to Summary tasks or Milestones. Resources are never entered on
Summary tasks or Milestones. Summary tasks have work defined at a lower level task. The
Resources are assigned at that lower level.
5.0 WORK (HOURS)
Sub-totals:
Work (effort) is estimated for every resource/subtask. Enter the Work estimate per subtask,
allowing MS Project to compute the start or finish date for the release.
6.0 DURATION (DAYS)
Sub-totals:
Duration is estimated for every task. A duration is necessary if the work to be performed is not
equivalent to the number of work days for the task. Tasks with resources assigned at less than 100%
requires work spread across an increased duration. Duration estimates allow MS Project to calculate
the total duration of the Summary (high-level) tasks.
7.0 START AND FINISH DATES
Sub-totals:
Tasks have accurate Start and Finish dates. If Start and Finish dates are not correctly scheduled
based on accurate work estimates, durations, and predecessors, then use a date constraint to assign
the task a start or finish date. Identification of start and finish dates will help determine the critical path
from the outset of the project.

REVIEWER'S COMMENTS
Green (0 No's); Red (1 No)

REVIEWER'S COMMENTS
Green (0 No's); Red (1 No)

REVIEWER'S COMMENTS
Green (0 No's); Yellow (1 No); Red (>1 No)

Tasks have accurate Actual Start and Actual Finish dates. When progress (Percent Complete) is
recorded for a task, the Actual Start date will be recorded automatically by MS Project. When the
Percent Complete is 100%, the Actual Finish date will be entered automatically by MS Project. At the
beginning of a task, verify the Actual Start date and record if different than the planned Start date. At
the completion of a task, verify the Actual Finish date of the task and record if different than the
planned Finish date. Identification of Actual Start and Actual Finish dates will help determine the critical
path of the project.
8.0 BASELINE
Sub-totals:
The project schedule is "Baselined." Once the project schedule is completed and deemed "final" by
the schedule owners, the schedule must be Baselined. As the project schedule is maintained, the
revised schedule is compared against the Baselined schedule to identify Schedule Variance. If actual
hours are tracked during the course of the project, Cost Variance can be identified on a timely basis.
New tasks are "Baselined." Once the project schedule is baselined, any new tasks added to the
schedule must be baselined individually.
9.0 NO BLANK TASKS
Sub-totals:
The project schedule does not contain blank task lines. During creation and maintenance of the
schedule, every blank line should be removed. Blank lines are counted as tasks in calculations of
project performance.

332165403.xls

REVIEWER'S COMMENTS
Green (0 No's); Yellow (1 No); Red (>1 No)

REVIEWER'S COMMENTS
Green (0 No's); Yellow (1 No)

10/04/2016 18:15:13