Project documents updates
“Project Documents Updates” is an output for the process “Direct and Manage Project Work “.
Project documents that may be updated include, but are not limited to:
– Requirements documentation,
– Project logs (issues, assumptions, etc.),
– Risk register, and – Stakeholder register.
“Project Documents Updates” is an output for the process “Monitor and Control Project Work “.
Project documents that may be updated include, but are not limited to:
– Schedule and cost forecasts,
– Work performance reports, and – Issue log.
“Project Documents Updates” is an output for the process “Perform Integrated Change Control”.
Project documents that may be updated as a result of the Perform Integrated Change Control process include all documents specified as being subject to the project?s formal change control process.
“Project Documents Updates” is an output for the process “Define Scope”.
Project documents that may be updated include, but are not limited to:
– Stakeholder register,
– Requirements documentation, and – Requirements traceability matrix.
“Project Documents Updates” is an output for the process “Create WBS”.
Project documents that may be updated include, but are not limited to, requirements documentation, which may need to be updated to include approved changes. If approved change requests result from the Create WBS process, then the requirements documentation may need to be updated to include approved changes.
“Project Documents Updates” is an output for the process “Validate Scope”.
Project documents that may be updated as a result of the Validate Scope process include any documents that define the product or report status on product completion. Verified project documents may require approvals from the customer or sponsor in the form of signatures or signoffs.
“Project Documents Updates” is an output for the process “Control Scope”.
Project documents that may be updated include, but are not limited to:
– Requirements documentation, and – Requirements traceability matrix.
“Project Documents Updates” is an output for the process “Sequence Activities”.
Project documents that may be updated include, but are not limited to:
– Activity lists,
– Activity attributes,
– Milestone list, and – Risk register.
“Project Documents Updates” is an output for the process “Estimate Activity Resources”.
Project documents that may be updated include, but are not limited to:
– Activity list,
– Activity attributes, and – Resource calendars.
“Project Documents Updates” is an output for the process “Estimate Activity Durations”.
Project documents that may be updated include, but are not limited to:
– Activity attributes; and – Assumptions made in developing the activity duration estimate, such as skill levels and availability, as well as a basis of estimates for durations.
“Project Documents Updates” is an output for the process “Develop Schedule”.
Project documents that may be updated include, but are not limited to: – Activity resource requirements. Resource leveling can have a significant effect on preliminary estimates for the types and quantities of resources required. If the resource-leveling analysis changes the project
resource requirements, then the project resource requirements are updated.
– Activity attributes. Activity attributes are updated to include any revised resource
requirements and any other revisions generated by the Develop Schedule process.
– Calendars. The calendar for each project may consist of multiple calendars, project calendars, individual
resource calendars etc., as the basis for scheduling the project.
– Risk register. The risk register may need to be updated to reflect opportunities or threats perceived through scheduling assumptions.
“Project Documents Updates” is an output for the process “Control Schedule”.
Project documents that may be updated include, but are not limited to: – Schedule Data. New project schedule network diagrams may be developed to display approved remaining durations and approved modifications to the schedule. In some cases, project schedule delays can be so severe that development of a new target schedule with forecasted start and finish dates is needed to
provide realistic data for directing the work, measuring performance, and measuring progress.
– Project Schedule. An updated project schedule will be generated from the schedule model populated
with updated schedule data to reflect the schedule changes and manage the project.
– Risk Register. The risk register, and risk response plans within it, may also be updated based on the risks that may arise due to schedule compression techniques.
“Project Documents Updates” is an output for the process “Estimate costs”.
Project documents that may be updated include, but are not limited to, the risk register.
“Project Documents Updates” is an output for the process “Determine budget”.
Project documents that may be updated include, but are not limited to:
– Risk register,
– Activity cost estimates, and – Project schedule.
“Project Documents Updates” is an output for the process “Control costs”.
Project documents that may be updated include, but are not limited to:
– Cost estimates, and – Basis of estimates.
“Project Documents Updates” is an output for the process “Plan quality management”.
Project documents that may be updated include, but are not limited to:
– Stakeholder register; and
– Responsibility assignment matrix; and – WBS and WBS Dictionary.
“Project Documents Updates” is an output for the process “Perform Quality assurance”.
Project documents that may be updated include, but are not limited to:
– Quality audit reports,
– Training plans, and – Process documentation.
“Project Documents Updates” is an output for the process “Control Quality “.
Project documents that may be updated include, but are not limited to,
– Quality standards;
– Agreements;
– Quality audit reports and change logs supported with corrective action plans;
– Training plans and assessments of effectiveness; and – Process documentation, such as information obtained using the seven basic quality tools or the quality management and control tools.
“Project Documents Updates” is an output for the process “Manage project team”.
Project documents that may indirectly be updated include, but are not limited to:
– Issue log,
– Roles description, and – Project staff assignments.
“Project Documents Updates” is an output for the process “Plan communications management”.
Project documents that may be updated include, but are not limited to:
– Project schedule, and – Stakeholder register.
“Project Documents Updates” is an output for the process “Manage communications “.
Project documents that may be updated include, but are not limited to:
– Issue log,
– Project schedule, and – Project funding requirements.
“Project Documents Updates” is an output for the process “Control communications “.
Project documents may be updated as a result of the Control Communications process. These updates may
include, but are not limited to:
– Forecasts,
– Performance reports, and – Issue log.
“Project Documents Updates” is an output for the process “Perform Qualitative Risk Analysis “.
Project documents that may be updated include, but are not limited to: – Risk register updates. As new information becomes available through the qualitative risk assessment, the risk register is updated. Updates to the risk register may include assessments of probability and impacts for each risk, risk ranking or scores, risk urgency information or risk
categorization, and a watch list for low probability risks or risks requiring further analysis.
– Assumptions log updates. As new information becomes available through the qualitative risk assessment, assumptions could change. The assumptions log needs to be revisited to accommodate this new information. Assumptions may be incorporated into the project scope statement or in a separate assumptions log.
“Project Documents Updates” is an output for the process “Perform Quantitative Risk Analysis “.
Project documents are updated with information resulting from quantitative risk analysis. For example, risk
register updates could include: – Probabilistic analysis of the project. Estimates are made of potential project schedule and cost outcomes listing the possible completion dates and costs with their associated confidence levels.
This output, often expressed as a cumulative frequency distribution, is used with stakeholder risk tolerances to permit quantification of the cost and time contingency reserves. Such contingency reserves are needed to bring the risk of overrunning stated project objectives to a level acceptable to
the organization.
– Probability of achieving cost and time objectives. With the risks facing the project, the probability of achieving project objectives under the current plan can be estimated using quantitative risk analysis results. For instance, in Figure 11-17, the likelihood of achieving the cost estimate of US$41 million is
about 12%.
– Prioritized list of quantified risks. This list includes those risks that pose the greatest threat or present the greatest opportunity to the project. These include the risks that may have the greatest effect on cost contingency and those that are most likely to influence the critical path. These risks may be evaluated, in
some cases, through a tornado diagram generated as a result of the simulation analysis.
– Trends in quantitative risk analysis results. As the analysis is repeated, a trend may become apparent that leads to conclusions affecting risk responses. Organizational historical information on project schedule, cost, quality, and performance should reflect new insights gained through the Perform Quantitative Risk Analysis process. Such history may take the form of a quantitative risk analysis report. This report may be separate from, or linked to, the risk register.
“Project Documents Updates” is an output for the process “Plan Risk Responses”.
In the Plan Risk Responses process, several project documents are updated as needed. For example, when appropriate risk responses are chosen and agreed upon, they are included in the risk register. The risk register should be written to a level of detail that corresponds with the priority ranking and the planned response. Often, the high and moderate risks are addressed in detail. Risks judged to be of low priority are included in a watch list for
periodic monitoring. Updates to the risk register can include, but are not limited to:
– Risk owners and assigned responsibilities;
– Agreed-upon response strategies;
– Specific actions to implement the chosen response strategy;
– Trigger conditions, symptoms, and warning signs of a risk occurrence;
– Budget and schedule activities required to implement the chosen responses;
– Contingency plans and triggers that call for their execution;
– Fallback plans for use as a reaction to a risk that has occurred and the primary response proves to be
inadequate;
– Residual risks that are expected to remain after planned responses have been taken, as well as those that
have been deliberately accepted;
– Secondary risks that arise as a direct outcome of implementing a risk response; and – Contingency reserves that are calculated based on the quantitative risk analysis of the project and the organization?s risk thresholds.
Other project documents updated could include: – Assumptions log updates. As new information becomes available through the application of risk responses, assumptions could change. The assumptions log needs to be revisited to accommodate this
new information.
– T echnical documentation updates. As new information becomes available through the application of risk responses, technical approaches and physical deliverables may change. Any supporting
documentation needs to be revisited to accommodate this new information.
– Change requests. Planning for possible risk responses can often result in recommendations for changes to the resources, activities, cost estimates, and other items identified during other planning processes.
When such recommendations are identified, change requests are generated and processed through the Perform Integrated Change Control process.
“Project Documents Updates” is an output for the process “Control Risks”.
Project documents that may be updated as a result of the Control Risk process include, but are not limited to the
risk register. Risk register updates may include: – O utcomes of risk reassessments, risk audits, and periodic risk reviews. These outcomes may include identification of new risks, updates to probability, impact, priority, response plans, ownership, and other elements of the risk register. Outcomes can also include closing risks that are no longer applicable
and releasing their associated reserves.
– Actual outcomes of the project?s risks and of the risk responses. This information can help project managers to plan for risk throughout their organizations, as well as on future projects.
“Project Documents Updates” is an output for the process “Plan Procurement management”.
Project documents that may be updated include, but are not limited to:
– Requirements documentation,
– Requirements traceability matrix, and – Risk register.
“Project Documents Updates” is an output for the process “Conduct Procurements “.
Project documents that may be updated include, but are not limited to:
– Requirements documentation,
– Requirements traceability documentation,
– Risk register, and – Stakeholder register.
“Project Documents Updates” is an output for the process “Control Procurements “.
Project documents that may be updated include, but are not limited to, procurement documentation.
Procurement documentation may include the procurement contract with all supporting schedules, requested unapproved contract changes, and approved change requests. Procurement documentation also includes any seller-developed technical documentation and other work performance information, such as deliverables, seller performance reports and warranties, financial documents including invoices and payment records, and the results of contract-related inspections.
“Project Documents Updates” is an output for the process “Plan Stakeholder Management”.
Project documents that may be updated include, but are not limited to:
– Project schedule, and – Stakeholder register.
“Project Documents Updates” is an output for the process “Manage Stakeholder Engagement”.
Project documents that may be updated include, but are not limited to, the stakeholder register. This is updated as information on stakeholders change, when new stakeholders are identified, or if registered stakeholders are no longer involved in or impacted by the project, or other updates for specific stakeholders are required.
“Project Documents Updates” is an output for the process “Control Stakeholder Engagement”.
Project documents that may be updated include, but are not limited to: – Stakeholder register. This is updated as information on stakeholders change, when new stakeholders are identified, or if registered stakeholders are no longer involved in or impacted by the project, or other
updates for specific stakeholders are required.
– Issue log. This is updated as new issues are identified and current issues are resolved.
This definition was found in the PMBOK V5
Go back to the Glossary or to the Mapping