1. Activity attributes
Described in Section 6.2.3.2. Activity attributes may describe a necessary sequence of events or defined predecessor or successor relationships, as well as defined lead and lag and logical relationships between the activities.
2. Activity list
Described in Section 6.2.3.1. The activity list contains all schedule activities required on the project that are to be sequenced. Dependencies and other constraints for these activities can influence the sequencing of the activities.
3. Assumption log
Described in Section 4.1.3.2. Assumptions and constraints recorded in the assumption log may influence the way activities are sequenced, the relationship between activities, and the need for leads and lags, and may give rise to individual project risks that may impact the project schedule.
4. Basis of estimates
Described in Sections 6.4.3.2 and 7.2.3.2. The basis of estimates is used to evaluate how the estimation of durations, cost, resources, and cost control compared to the actual results.
5. Change log
Described in Section 4.6.3.3. The change log contains the status of all change requests throughout the project or phase.
6. Cost estimates
Described in Section 7.2.3.1. Cost estimates for each activity within a work package are aggregated to obtain a cost estimate for each work package.
7. Cost forecasts
Described in Section 7.4.3.2. Forecasts such as the project’s estimate to complete (ETC), estimate at completion (EAC), budget at completion (BAC), and to-complete performance index (TCPI) may be compared to the results of a quantitative cost risk analysis to determine the confidence level associated with achieving these targets.
8. Duration estimates
Described in Section 6.4.3.1. Duration estimates provide the starting point from which schedule variability is evaluated.
9. Issue log
Described in Section 4.3.3.3. The issue log is used to check that there is no open issue.
10. Lessons learned register
Described in Section 4.3.3.1. The lessons learned in the phase or project will be finalized before being entered into the lessons learned repository.
11. Milestone list
Described in Section 6.2.3.3. The milestone list may have scheduled dates for specific milestones, which may influence the way activities are sequenced.
12. Physical resource assignments
Described in Section 9.3.3.1. The physical resource assignments describe the expected resource utilization along with
13. Project calendars
Described in Section 6.5.3.4. A schedule model may require more than one project calendar to allow for different work periods for some activities to calculate the schedule forecasts.
14. Project communications
Described in Section 10.2.3.1. Project communications include any and all communications that have been created throughout the project.
15. Project schedule
Described in Section 6.5.3.2. Project schedule refers to the most recent version with notations to indicate updates, completed activities, and started activities as of the indicated date.
16. Project schedule network diagram
Described in Section 6.3.3.1. The project schedule network diagrams contain the logical relationships of predecessors and successors that will be used to calculate the schedule.
17. Project scope statement
Described in Section 5.3.3.1. The project scope statement describes the work that will be performed and the work that is excluded.
18. Project team assignments
Described in Section 9.3.3.1. The project team assignments specify which resources are assigned to each activity.
19. Quality control measurements
Described in Section 8.3.3.1. The quality control measurements document the results of Control Quality activities and demonstrate compliance with the quality requirements.
20. Quality metrics
Described in Section 8.1.3.2. Quality metrics are verified as part of the Control Quality process. The Manage Quality process uses these quality metrics as a basis for the development of test scenarios for the project and its deliverables and as a basis for improvement initiatives.
21. Quality report
Described in Section 8.2.3.1. The information presented in the quality report may include all quality assurance issues managed or escalated by the team, recommendations for improvement, and the summary of findings from the Control Quality process.
22. Requirements documentation
Described in Section 5.2.3.1. Requirements documentation is used to demonstrate compliance with the project scope.
23. Requirements traceability matrix
Described in Section 5.2.3.2. Where quality requirements are specified by this process, they are recorded in the requirements traceability matrix.
24. Resource breakdown structure
Described in Section 9.2.3.3. The resource breakdown structure provides a reference in case any resource needs to be replaced or reacquired during the course of the project.
25. Resource calendars
Described in Section 9.2.1.2. Resource calendars show the availability of team and physical resources.
26. Resource requirements
Described in Section 9.2.3.1. Resource requirements identify the needed material, equipment, supplies, and other resources.
27. Risk register
Described in Section 11.2.3.1. The risk register provides information on risks that have occurred throughout the project.
28. Risk report
Described in Section 11.2.3.2. The risk report provides information on the risk status and is used to check that there are no open risks at the end of the project.
29. Schedule data
Described in Section 6.5.3.3. Schedule data will be reviewed and updated in the Control Schedule process.
30. Schedule forecasts
Described in Section 6.6.3.2. Forecasts may be compared to the results of a quantitative schedule risk analysis to determine the confidence level associated with achieving these targets.
31. Stakeholder register
Described in Section 13.1.3.1. Where additional information on existing or new stakeholders is gathered as a result of this process, it is recorded in the stakeholder register.
32. Team charter
Described in Section 9.1.3.2. The team charter is where the team operating guidelines are documented. The team values and operating guidelines provide the structure that describes how the team will operate together.
33. Test and evaluation documents
Described in Section 8.2.3.2. Test and evaluation documents are used to evaluate achievement of the quality objectives.
