Section: Volume E

Section: Volume B
Explanation:
5.2.3.1 Requirements Documentation
Requirements documentation describes how individual requirements meet the business need for the project.
Requirements may start out at a high level and become progressively more detailed as more about the requirements is known. Before being baselined, requirements need to be unambiguous (measurable and testable), traceable, complete, consistent, and acceptable to key stakeholders. The format of a requirements document may range from a simple document listing all the requirements categorized by stakeholder and priority, to more elaborate forms containing an executive summary, detailed descriptions, and attachments.
Components of requirements documentation can include, but, are not limited to:
Business requirements, including:

○ Business and project objectives for traceability;
○ Business rules for the performing organization; and
○ Guiding principles of the organization
* Stakeholder requirements, including:
○ Impacts to other organizational areas;
○ Impacts to other entities inside or outside the performing organization; and
○ Stakeholder communication and reporting requirements.
* Solution requirements, including:
○ Functional and nonfunctional requirements;
○ Technology and standard compliance requirements;
○ Support and training requirements;
○ Quality requirements; and
○ Reporting requirements, etc. (solution requirements can be documented textually, in models, or both).
Project requirements, such as:

○ Levels of service, performance, safety, compliance, etc.; and
○ Acceptance criteria.
Transition requirements.

Requirements assumptions, dependencies, and constraints.

Explanation/Reference:
Explanation:
13.1.2.1 Stakeholder Analysis
Stakeholder analysis is a technique of systematically gathering and analyzing quantitative and qualitative information to determine whose interests should be taken into account throughout the project. It identifies the interests, expectations, and influence of the stakeholders and relates them to the purpose of the project. It also helps to identify stakeholder relationships (with the project and with other stakeholders) that can be leveraged to build coalitions and potential partnerships to enhance the project's chance of success, along with stakeholder relationships that need to be influenced differently at different stages of the project or phase.
Stakeholder analysis generally follows the steps described below:
Identify all potential project stakeholders and relevant information, such as their roles, departments,

interests, knowledge, expectations, and influence levels. Key stakeholders are usually easy to identify.
They include anyone in a decision-making or management role who is impacted by the project outcome, such as the sponsor, the project manager, and the primary customer. Identifying other stakeholders is usually done by interviewing identified stakeholders and expanding the list until all potential stakeholders are included.
Analyze the potential impact or support each stakeholder could generate, and classify them so as to

define an approach strategy. In large stakeholder communities, it is important to prioritize the stakeholders to ensure the efficient use of effort to communicate and manage their expectations.
Assess how key stakeholders are likely to react or respond in various situations, in order to plan how to

influence them to enhance their support and mitigate potential negative impacts.
There are multiple classification models used for stakeholders analysis, such as:
Power/interest grid, grouping the stakeholders based on their level of authority ("power") and their level

or concern ("interest") regarding the project outcomes;
Power/influence grid, grouping the stakeholders based on their level of authority ("power") and their

active involvement ("influence") in the project;
Influence/impact grid, grouping the stakeholders based on their active involvement ("influence") in the

project and their ability to effect changes to the project's planning or execution ("impact"); and Salience model, describing classes of stakeholders based on their power (ability to impose their will),

urgency (need for immediate attention), and legitimacy (their involvement is appropriate).

Section: Volume A
Explanation:
Process: 6.5 Estimate Activity Durations
Definition: The process of estimating the number of work periods needed to complete individual activities with estimated resources.
Key Benefit: The key benefit of this process is that it provides the amount of time each activity will take to complete, which is a major input into the Develop Schedule process.
Inputs
1. Schedule management plan
2. Activity list
3. Activity attributes
4. Activity resource requirements
5. Resource calendars
6. Project scope statement
7. Risk register
8. Resource breakdown structure
9. Enterprise environmental factors
10.Organizational process assets
Tools & Techniques
1. Expert judgment
2. Analogous estimating
3. Parametric estimating
4. Three-point estimating
5. Group decision-making techniques
6. Reserve analysis
Outputs
1. Activity duration estimates
2. Project documents updates
6.5.2.6 Reserve Analysis
Duration estimates may include contingency reserves, sometimes referred to as time reserves or buffers, into the project schedule to account for schedule uncertainty. Contingency reserves are the estimated duration within the schedule baseline, which is allocated for identified risks that are accepted and for which contingent or mitigation responses are developed. Contingency reserves are associated with the "known-unknowns," which may be estimated to account for this unknown amount of rework.
As more precise information about the project becomes available, the contingency reserve may be used, reduced, or eliminated. Contingency should be clearly identified in schedule documentation.
[..]
Estimates may also be produced for the amount of management reserve of time for the project. Management reserves are a specified amount of the project duration withheld for management control purposes and are reserved for unforeseen work that is within scope of the project. Management reserves are intended to address the "unknown-unknowns" that can affect a project. Management reserve is not included in the schedule baseline, but it is part of the overall project duration requirements. Depending on contract terms, use of management reserves may require a change to the schedule baseline.

Section: Volume E