Section: Volume A
Explanation:
8.2.2.1 Quality Management and Control Tools
The Perform Quality Assurance process uses the tools and techniques of the Plan Quality Management and Control Quality processes. In addition, other tools that are available include (see also Figure 8-10):
Affinity diagrams. The affinity diagram is similar to mind-mapping techniques in that they are used to

generate ideas that can be linked to form organized patterns of thought about a problem. In project management, the creation of the WBS may be enhanced by using the affinity diagram to give structure to the decomposition of scope.
Process decision program charts (PDPC). Used to understand a goal in relation to the steps for getting to

the goal. The PDPC is useful as a method for contingency planning because it aids teams in anticipating intermediate steps that could derail achievement of the goal.
Interrelationship digraphs. An adaptation of relationship diagrams. The interrelationship digraphs provide a

process for creative problem solving in moderately complex scenarios that possess intertwined logical relationships for up to 50 relevant items. The interrelationship digraph may be developed from data generated in other tools such as the affinity diagram, the tree diagram, or the fshbone diagram.
Tree diagrams. Also known as systematic diagrams and may be used to represent decomposition

hierarchies such as the WBS, RBS (risk breakdown structure), and OBS (organizational breakdown structure).
In project management, tree diagrams are useful in visualizing the parent-to-child relationships in any decomposition hierarchy that uses a systematic set of rules that define a nesting relationship. Tree diagrams can be depicted horizontally (such as a risk breakdown structure) or vertically (such as a team hierarchy or OBS). Because tree diagrams permit the creation of nested branches that terminate into a single decision point, they are useful as decision trees for establishing an expected value for a limited number of dependent relationships that have been diagramed systematically.
Prioritization matrices. Identify the key issues and the suitable alternatives to be prioritized as a set of

decisions for implementation. Criteria are prioritized and weighted before being applied to all available alternatives to obtain a mathematical score that ranks the options.
Activity network diagrams. Previously known as arrow diagrams. They include both the AOA (Activity on

Arrow) and, most commonly used, AON (Activity on Node) formats of a network diagram. Activity network diagrams are used with project scheduling methodologies such as program evaluation and review technique (PERT), critical path method (CPM), and precedence diagramming method (PDM).
Matrix diagrams. A quality management and control tool used to perform data analysis within the

organizational structure created in the matrix. The matrix diagram seeks to show the strength of relationships between factors, causes, and objectives that exist between the rows and columns that form the matrix.

Explanation/Reference:
Explanation:
5.4.3.1 Scope Baseline
The scope baseline is the approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary, that can be changed only through formal change control procedures and is used as a basis for comparison. It is a component of the project management plan. Components of the scope baseline include:
Project scope statement. The project scope statement includes the description of the project scope,

major deliverables, assumptions, and constraints.
WBS. The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project

team to accomplish the project objectives and create the required deliverables. Each descending level of the WBS represents an increasingly detailed definition of the project work. The WBS is finalized by assigning each work package to a control account and establishing a unique identifier for that work package from a code of accounts. These identifiers provide a structure for hierarchical summation of costs, schedule, and resource information. A control account is a management control point where scope, budget, actual cost, and schedule are integrated and compared to the earned value for performance measurement. Control accounts are placed at selected management points in the WBS. Each control account may include one or more work packages, but each of the work packages should be associated with only one control account. A control account may include one or more planning packages. A planning package is a work breakdown structure component below the control account with known work content but without detailed schedule activities.
WBS dictionary. The WBS dictionary is a document that provides detailed deliverable, activity, and

scheduling information about each component in the WBS. The WBS dictionary is a document that supports the WBS. Information in the WBS dictionary may include, but is not limited to:
○ Code of account identifier,
○ Description of work,
○ Assumptions and constraints,
○ Responsible organization,
○ Schedule milestones,
○ Associated schedule activities,
○ Resources required,
○ Cost estimates,
○ Quality requirements,
○ Acceptance criteria,
○ Technical references, and
○ Agreement information
Process: 5.4 Create WBS
Definition: WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. Key Benefit: The key benefit of this process is that it provides a structured vision of what has to be delivered.
Inputs
1. Scope management plan
2. Project scope statement
3. Requirements documentation
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Decomposition
2. Expert judgment
Outputs
1. Scope baseline
2. Project documents updates

Section: Volume C
Explanation:
4.1.1.1 Project Statement of Work
The project statement of work (SOW) is a narrative description of products, services, or results to be delivered by a project. For internal projects, the project initiator or sponsor provides the statement of work based on business needs, product, or service requirements. For external projects, the statement of work can be received from the customer as part of a bid document, (e.g., a request for proposal, request for information, or request for bid) or as part of a contract. The SOW references the following:
Business need. An organization's business need may be based on a market demand, technological advance,

legal requirement, government regulation, or environmental consideration. Typically, the business need and the cost-beneft analysis are contained in the business case to justify the project.
Product scope description. The product scope description documents the characteristics of the product,

service, or results that the project will be undertaken to create. The description should also document the relationship between the products, services, or results being created and the business need that the project will address.
Strategic plan. The strategic plan documents the organization's strategic vision, goals, and objectives and

may contain a high-level mission statement. All projects should be aligned with their organization's strategic plan. Strategic plan alignment ensures that each project contributes to the overall objectives of the organization.

Explanation/Reference:
Explanation:
8.2.2 Perform Quality Assurance: Tools and Techniques
8.2.2.1 Quality Management and Control Tools
The Perform Quality Assurance process uses the tools and techniques of the Plan Quality Management and Control Quality processes. In addition, other tools that are available include (see also Figure 8-10):
Affinity diagrams. The affinity diagram is similar to mind-mapping techniques in that they are used to

generate ideas that can be linked to form organized patterns of thought about a problem. In project management, the creation of the WBS may be enhanced by using the affinity diagram to give structure to the decomposition of scope.
Process: 8.2 Perform Quality Assurance
Definition: The process of auditing the quality requirements and the results from quality control measurements to ensure that appropriate quality standards and operational definitions are used.
Key Benefit: The key benefit of this process is that it facilitates the improvement of quality processes.
Inputs
1. Quality management plan
2. Process improvement plan
3. Quality metrics
4. Quality control measurements
5. Project documents
Tools & Techniques
1. Quality management and control tools
2. Quality audits
3. Process analysis
Outputs
1. Change requests
2. Project management plan updates
3. Project documents updates
4. Organizational process assets updates