Appendix VIII: Recommended Elements of a Data Collection Instrument
The baseline IMS and the latest updated IMS, including all applicable embedded project schedules. Their format should be that of a software schedule file. PDF files and presentation slides are not valid schedule file formats. The name and version of the software used to create and maintain the schedule are provided.
A schedule dictionary or similar documentation that defines custom fields, especially those that contain information on level-of-effort activities; contractor versus government effort; and statement of work, statement of objective, work package, integrated master plan, or control account mappings.
Integrated master plan (IMP), if applicable.
Work breakdown structure (WBS) and dictionary.
A statement of work (SOW), if applicable.
A cross-walk between the WBS, contractor WBS, SOW and the schedule activities, as applicable.
An identification of the main deliverables, including a designation of the paths that the project considers critical and near-critical.
Schedule basis documentation.
Schedule narrative documentation.
A basis of estimate or other documentation for estimating activity durations and assigned resources.
Program management review briefings or similar documentation discussing schedule status and establishing traceability of reported dates to detail schedules.
Relevant scheduling guidance, such as contract line item numbers, data item descriptions, and agency directives that govern the creation, maintenance, structure, and status of the schedule.
Schedule risk analysis documentation, including the analytical approach, assumptions, and results.
A risk management plan and a copy of the current risk register.
A description of the schedule change control process.