Schedule Reporting


Typical shcedule reports are:

Table of Contents

Management Summary

Each project should develop and make available a one page, top level, Gantt-type summary document with PBS elements identified. This document should reflect all contract and controlled milestones, major project phases (i.e., design, build, test etc.) and all end item deliveries.

Logic Network and critical path

Each project should develop and make available a logic network consisting of schedule data for all PBS elements. The entire scope of work should be broken into schedule tasks and milestones at a consistent level of detail to allow discrete progress measurement and visibility into the overall progress of each end item deliverable. It is also useful to report separately tasks/activities that are on the critical path so appropriate attention can be put on these key activities.

Total Slack and Schedule reserve

Reporting the consumption of total Slack and schedule reserve is also useful and helps identify issues early.

Performance Trends

Reports that show performance trends relating to schedule performance, also help monitor project health. Typical trends include accomplishments (planned finishes versus actual finishes), forecasts (planned starts versus actual starts), and workloads (cumulative starts and finishes, planned versus actual). Any change between reporting periods should also be clearly explained.

25 January 2009 (5)