Pmi Performance Domain 2: Planning The Project - Part One

Front 1

Project Management Plan

Back 1

This is a plan that details how a project will be executed to achieve its objectives.

Front 2

Subsidiary Plan:
Scope Management Plan

Back 2

Provides guidance on how project scope will be defined, documented, verified, managed and controlled

Front 3

Subsidiary Plan:
Requirements Management Plan

Back 3

Documents how requirements will be analyzed, documented, verified, managed and controlled.

Front 4

Subsidiary Plan:
Schedule Management Plan

Back 4

Describes the scheduling methodology, the scheduling tools to be used, and the format and established criteria for developing and controlling the project schedule.

Front 5

Subsidiary Plan:
Cost Management Plan

Back 5

Describes the format and establishes the criteria for planning, structuring, estimating, budgeting and controlling project costs.

Front 6

Subsidiary Plan:
Quality Management Plan

Back 6

Describes how the performing organization's quality policy will be implemented by the project management team throughout the project.

Front 7

Subsidiary Plan:
Process Improvement Plan

Back 7

Details the steps for analyzing processes to identify the activities that enhance their value.

Front 8

Subsidiary Plan:
Human Resource Plan

Back 8

Provides guidance on how the human resources required for a project should be defined, staffed, managed, controlled and eventually released.

Front 9

Subsidiary Plan:
Communications Management Plan

Back 9

Provides details that document the approach to communicate efficiently and effectively with the stakeholders.

Front 10

Subsidiary Plan:
Risk Management Plan

Back 10

Describes how risk management is structured and performed on the project.

Front 11

Subsidiary Plan:
Procurement Management Process

Back 11

Describes how the procurement processes will be managed from developing procurement documents through contract closure.

Front 12

Project Management Plan Inputs:
Project Charter

Back 12

This formally authorizes the project, provides authority to the project manager to commit resources, and is the starting point for the project management plan.

Front 13

Project Management Plan Inputs:
Outputs From Planning Process

Back 13

These are the baselines and subsidiary management plans that are outputs from other planning processes

Front 14

Project Management Plan Inputs:
Enterprise Environmental Factors

Back 14

These are factors that may influence the project's success such as existing assets (like information systems, human resources) and external factors (such as governmental regulations, marketplace conditions).

Front 15

Project Management Plan Inputs:
Organizational Process Assets

Back 15

These are processes that already exist that may impact the success of a project such as policies, guidelines, historical information and previous project knowledge.

Front 16

Collect Requirements Process

Back 16

This is where the project manager defines and documents the stakeholders' needs and expectations to meet the project objectives.

Front 17

Collect Requirements - Tools & Techniques:
Interviews

Back 17

This is used to get information from stakeholders by talking to them directly.

Front 18

Collect Requirements - Tools & Techniques:
Focus Groups

Back 18

This is a trained moderator guided interactive discussion that includes stakeholders and subject matter experts (SME's) to elicit their expectations and attitudes towards the proposed product, service or result of the project.

Front 19

Collect Requirements - Tools & Techniques:
Facilitated Workshops

Back 19

These are interactive group focused sessions that bring together key cross-functional stakeholders to define the project or product requirements.

Front 20

Collect Requirements - Tools & Techniques:
Group Creativity Techniques

Back 20

These are group activities that are organized to identify project and product requirements and include brainstorming and the Delphi technique.

Front 21

Collect Requirements - Tools & Techniques:
Group Decision Making Techniques

Back 21

This is an assessment process of multiple alternatives to generate, classify and prioritize project or product requirements.

Front 22

Collect Requirements - Tools & Techniques:
Questionnaires & Surveys

Back 22

These are written sets of questions designed to quickly accumulate information from a broad audience.

Front 23

Collect Requirements - Tools & Techniques:
Observation

Back 23

This is a direct way of viewing individuals in their work environment or while using the product to identify the project or product requirements.

Front 24

Collect Requirements - Tools & Techniques:
Prototypes

Back 24

This is a method of obtaining feedback on requirements by providing a working model of the expected product.

Front 25

Collect Requirements Outputs:
Requirements Documentation

Back 25

This describes how the individual requirements would meet the business need for the project

Front 26

Collect Requirements Outputs:
Requirements Management Plan

Back 26

This documents how the project requirements will be analyzed, documented and managed throughout the project life cycle.

Front 27

Collect Requirements Outputs:
Requirements Traceability Matrix

Back 27

This is a table that links the requirements to their origin and tracks them throughout the project life cycle.

Front 28

Group Creativity Techniques:
Brainstorming

Back 28

This is used to generate and create multiple ideas related to project and product requirements.

Front 29

Group Creativity Techniques:
Nominal Group Technique

Back 29

This is when a voting process is used to rank the most useful ideas obtained through brainstorming and then to prioritize them.

Front 30

Group Creativity Techniques:
Delphi Technique

Back 30

This is a group technique that extracts and summarizes anonymous group input to choose among various alternatives.

Front 31

Group Creativity Techniques:
Idea or Mind Mapping

Back 31

This is when ideas created through brainstorming are consolidated into a map that reflects the commonality, differences in understanding, and generation of new ideas.

Front 32

Group Creativity Techniques:
Affinity diagram

Back 32

This technique enables the sorting of a large number of ideas collected during brainstorming into distinct categories for review and analysis.

Front 33

Group Decision Making Techniques:
Unanimity

Back 33

This is when everyone in the group agrees on a single course of action.

Front 34

Group Decision Making Techniques:
Majority

Back 34

This requires support from more than 50% of the members of a group to indicate the selected decision.

Front 35

Group Decision Making Techniques:
Plurality

Back 35

This is when the largest batch in a group decides for the group even if a majority is not achieved.

Front 36

Group Decision Making Techniques:
Dictatorship

Back 36

This is when one individual makes the decision for an entire group.

Front 37

Requirements Documentation

Back 37

This describes how individual requirements meet the business requirements of the project.

Front 38

Requirements Management Plan

Back 38

This is a plan that describes how the project requirements will be analyzed, documented and managed throughout the project life cycle.

Front 39

Scope Statement

Back 39

This defines the project and what it does and does not need to accomplish.

Front 40

Scope Statement Components:
Project Objectives

Back 40

These are the measurable success criteria for the project.

Front 41

Scope Statement Components:
Product Description

Back 41

These are the characteristics of the product, service or result of the project undertaken.

Front 42

Scope Statement Components:
Project Requirements

Back 42

These are the conditions or capabilities the deliverables of the project must meet to satisfy a standard, contract, specification or government or industry regulation.

Front 43

Scope Statement Components:
Project Deliverables

Back 43

This is any tangible, measurable result or outcome required to complete a project or portion of a project.

Front 44

Scope Statement Components:
Project Boundaries

Back 44

These are the parameters of what is or what is not included within a project.

Front 45

Scope Statement Components:
Product Acceptance Criteria

Back 45

This is the process and criteria for accepting finished products or services resulting from a project.

Front 46

Scope Statement Components:
Project Constraints

Back 46

These are factors that limit the way that the project can be approached and may concern time, cost, scope, quality, resources and others.

Front 47

Scope Statement Components:
Project Assumptions

Back 47

These are statements that must be taken to be true in order for the planning to begin.

Front 48

Define Scope Process

Back 48

This is when the project manager defines the scope of the project and finalizes the project scope statement

Front 49

Triple Constraints

Back 49

These are limitations that concern scope, time and cost. They are interrelated and exist in a state of equilibrium.

Front 50

Define Scope Tools & Techniques:
Expert Judgement

Back 50

This is when experts in different areas across the project may contribute to the project scope statement

Front 51

Define Scope Tools & Techniques:
Product Analysis

Back 51

This is the process of translating project objectives into tangible deliverables and requirements.

Front 52

Define Scope Tools & Techniques:
Alternatives Identification

Back 52

This is the process of creating different plans to achieve project goals.

Front 53

Define Scope Tools & Techniques:
Facilitated Workshops

Back 53

These help to quickly define the cross-functional project or product requirements of various stakeholders.