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:
4.1.2.1 Expert Judgment
Expert judgment is often used to assess the inputs used to develop the project charter. Expert judgment is applied to all technical and management details during this process. Such expertise is provided by any group or individual with specialized knowledge or training and is available from many sources, including:
Other units within the organization,

Consultants,

Stakeholders, including customers or sponsors,

Professional and technical associations,

Industry groups,

Subject matter experts (SME), and

Project management office (PMO).

4.1.3.1 Project Charter
The project charter is the document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. It documents the business needs, assumptions, constraints, the understanding of the customer's needs and high-level requirements, and the new product, service, or result that it is intended to satisfy, such as:
Project purpose or justification,

Measurable project objectives and related success criteria,

High-level requirements,

Assumptions and constraints,

High-level project description and boundaries,

High-level risks,

Summary milestone schedule,

Summary budget,

Stakeholder list,

Project approval requirements (i.e., what constitutes project success, who decides the project is

successful, and who signs off on the project),
Assigned project manager, responsibility, and authority level, and

Name and authority of the sponsor or other person(s) authorizing the project charter.

Process: 4.1. Develop Project Charter
Definition: The process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Key Benefit: The key benefit of this process is a well-defined project start and project boundaries, creation of a formal record of the project, and a direct way for senior management to formally accept and commit to the project.
Inputs
1. Project statement of work
2. Business case
3. Agreements
4. Enterprise environmental factors
5. Organizational process assets
Tools & Techniques
1. Expert judgment
2. Facilitation techniques
Outputs
1. Project charter