📘 PMBOK 7 – Tools & Techniques Master Reference (ITTO Guide)

PMP Exam Ready | Eng. Ahmad Safi, PE

1. PMBOK 7 ITTO Overview

PMBOK 7 (7th Edition, 2021) represents a major shift from the process-centric, ITTO-heavy format of PMBOK 6 to a principles-based framework. Instead of 49 processes with defined Inputs → Tools & Techniques → Outputs, PMBOK 7 provides:

PMBOK 6 StructurePMBOK 7 Structure
5 Process Groups12 Project Management Principles
10 Knowledge Areas8 Performance Domains
49 ProcessesModels, Methods & Artifacts (MMA)
ITTO for each processTailoring guidance
🎯 PMP Exam Note: For the current PMP exam, both PMBOK 7 and the ECO (Examination Content Outline) are tested. Many tools from PMBOK 6 ITTO still appear. This reference covers all tools you need regardless of edition.

The 12 PMBOK 7 Principles

#PrincipleKey Focus
1StewardshipBe a diligent, respectful, and caring steward
2TeamCreate a collaborative project team environment
3StakeholdersEffectively engage with stakeholders
4ValueFocus on value delivery
5Systems ThinkingRecognize, evaluate, and respond to system interactions
6LeadershipDemonstrate leadership behaviors
7TailoringTailor based on context
8QualityBuild quality into processes and deliverables
9ComplexityNavigate complexity
10RiskOptimize risk responses
11Adaptability & ResilienceEmbrace adaptability and resiliency
12ChangeEnable change to achieve the envisioned future state

The 8 Performance Domains

DomainFocus Area
StakeholderEngagement, expectations, communication
TeamTeam culture, development, performance
Development Approach & Life CyclePredictive, adaptive, or hybrid delivery
PlanningOrganizing, elaborating, coordinating
Project WorkProcesses, communications, physical resources
DeliveryScope, requirements, quality, value
MeasurementKPIs, metrics, forecasts, performance data
UncertaintyRisk, ambiguity, volatility, complexity

2. Models, Methods & Artifacts (MMA)

PMBOK 7 replaces ITTOs with the MMA section — a practitioner toolkit organized into three categories:

CategoryDefinitionExamples
ModelsThinking strategies and frameworksTuckman, ADKAR, Cynefin, Salience
MethodsMeans for achieving an outcomeCPM, PERT, Kanban, Earned Value
ArtifactsTemplates, documents, outputsWBS, Risk Register, Project Charter

3. Brainstorming

Data Gathering Creative Group

What It Is

A creativity technique used to generate a large number of ideas quickly from a group, encouraging free thinking without criticism.

Where It Is Used

Performance DomainUse Case
Uncertainty (Risk)Identify project risks
PlanningIdentify requirements, WBS elements
DeliveryIdentify quality issues and solutions
StakeholderIdentify stakeholders

Components / Method

  • Preparation: Define the topic/problem clearly before the session
  • Facilitation: A neutral facilitator manages the session
  • Idea Generation: All ideas recorded without judgment (5–20 min)
  • Consolidation: Ideas grouped using affinity diagrams
  • Evaluation: Ideas evaluated for feasibility after session

Variants

  • Nominal Group Technique (NGT): Individual idea generation first, then group sharing
  • Reverse Brainstorming: Identify what could cause failure instead of success
  • Brainwriting: Written ideas passed around silently
  • Round-Robin: Each participant takes a turn

Key Outputs / Artifacts

  • Risk register entries
  • Requirements list
  • Stakeholder list
  • Lessons learned

4. Interviews

Data Gathering Individual

What It Is

A formal or informal approach to elicit information from stakeholders through direct conversation — one-on-one or in small groups.

Where It Is Used

Domain / ProcessUse
PlanningCollect requirements, assumptions
UncertaintyIdentify risks from expert opinion
StakeholderUnderstand stakeholder needs and concerns
MeasurementGather performance feedback

Components / Method

  • Structured: Pre-defined questions, consistent across interviews
  • Unstructured: Open-ended, conversational, exploratory
  • Semi-structured: Mix of both (most common in PM)
  • Steps: Prepare questions → Conduct interview → Document responses → Analyze and validate

5. Focus Groups

Data Gathering Group

What It Is

A moderated discussion with pre-qualified stakeholders and subject matter experts to learn about expectations, attitudes, and opinions on a product, service, or result.

Where Used

  • Requirements collection (Delivery domain)
  • Stakeholder engagement assessment
  • Quality expectations gathering

Method

  • Trained moderator leads 6–12 participants
  • Session typically 1–2 hours
  • More interactive than surveys, less structured than interviews

6. Questionnaires & Surveys

Data Gathering Large Group

What It Is

Written sets of questions designed to quickly accumulate information from a large number of respondents.

Where Used

  • Requirements elicitation from large stakeholder groups
  • Risk identification across distributed teams
  • Lessons learned collection
  • Stakeholder satisfaction measurement

Method

  • Closed-ended: Yes/No, multiple choice, Likert scale (easy to analyze)
  • Open-ended: Free text (more insight, harder to analyze)
  • Best used when: many respondents, need statistical analysis, geographically dispersed

7. Benchmarking

Data Gathering Data Analysis

What It Is

Comparing actual or planned practices, processes, or quality levels to comparable projects or industry standards to identify best practices and opportunities for improvement.

Where Used

  • Quality planning and quality control
  • Schedule and cost baseline development
  • Risk planning
  • Performance measurement

Method

  • Internal: Compare to similar internal projects
  • Competitive: Compare to competitors
  • Functional: Compare same function across industries
  • Generic: Compare best-in-class regardless of industry

8. Document Analysis

Data Gathering

What It Is

Reviewing and analyzing existing documentation to extract relevant information for the project.

Where Used

  • Requirements development
  • Risk identification
  • Stakeholder identification
  • Procurement planning
  • Lessons learned

Documents Reviewed

Agreements, business plans, marketing literature, RFPs, feasibility studies, SOWs, regulatory requirements, policies, procedures, prior project files, and industry standards.

9. Checklists

Data Gathering Quality

What It Is

A structured list of required steps or items to be completed or verified. Used to ensure consistency and completeness.

Where Used

  • Quality control inspections
  • Risk identification
  • Project closeout
  • Procurement

Method

  • Items listed in logical order of execution
  • Each item checked off upon completion/verification
  • Often derived from historical project data or industry standards

10. Check Sheets

Data Gathering Quality

What It Is

A tally sheet used to collect and organize data about potential quality problems. Helps identify frequency of defects, issues, or other events.

Where Used

  • Quality control (counting defects)
  • Root cause analysis preparation

Example Structure

Defect TypeMonTueWedTotal
CrackIIIIIIIII9
Missing rebarIIIII5
Wrong specIIIII5

11. Earned Value Analysis (EVA)

Data Analysis Measurement

What It Is

An integrated method that combines scope, schedule, and cost data to objectively measure project performance and forecast completion.

Where Used

  • Measurement Domain: Primary performance measurement tool
  • Planning Domain: Establish baselines (PV)
  • Project Work Domain: Monitor and control performance

Key Components

TermFormulaMeaning
PV – Planned ValueBaselineBudgeted cost of work scheduled
EV – Earned Value% Complete × BACBudgeted cost of work performed
AC – Actual CostActual spendActual cost incurred
BAC – Budget at CompletionTotal budgetTotal planned budget
CV – Cost VarianceEV – AC+ve = under budget
SV – Schedule VarianceEV – PV+ve = ahead of schedule
CPI – Cost Performance IndexEV / AC>1 = efficient
SPI – Schedule Performance IndexEV / PV>1 = ahead
EAC – Estimate at CompletionBAC / CPIExpected total cost
ETC – Estimate to CompleteEAC – ACCost remaining
VAC – Variance at CompletionBAC – EACExpected over/under run
TCPI – To Complete PI(BAC–EV)/(BAC–AC)Efficiency needed to meet BAC
Rule of Thumb: CPI < 0.9 is a serious warning. Once a project is 20% complete, the CPI rarely improves significantly.

12. Variance Analysis

Data Analysis

What It Is

Reviewing differences between planned and actual performance to determine their cause and decide corrective or preventive actions.

Where Used

  • Cost control (Cost Variance)
  • Schedule control (Schedule Variance)
  • Scope control
  • Quality control

Method

  • Compare baseline to actual
  • Calculate variance (absolute or %)
  • Determine if within threshold
  • If outside threshold → root cause analysis → corrective action

13. Trend Analysis

Data Analysis

What It Is

Examining project performance over time to determine if performance is improving or deteriorating, and forecasting future performance.

Where Used

  • Schedule performance tracking
  • Cost performance tracking
  • Quality metrics over iterations
  • Risk exposure trends

Tools Used

  • Run charts (data plotted over time)
  • Burndown/burnup charts (Agile)
  • S-curves
  • EV trend lines

14. Root Cause Analysis (RCA)

Data Analysis Quality

What It Is

A structured method to identify the fundamental cause of a defect, problem, or risk — not just the symptoms.

Where Used

  • Quality control and improvement
  • Risk management (preventing recurrence)
  • Issue resolution in Project Work domain
  • Lessons learned

Common RCA Methods

MethodDescription
5 WhysAsk "Why?" repeatedly (5 times) to drill down to root cause
Fishbone (Ishikawa)Cause-and-effect diagram showing categories of causes
Fault Tree AnalysisTop-down deductive analysis using logic gates
Pareto Analysis80/20 rule — identify the 20% of causes producing 80% of problems

5 Whys Example

Problem: Bridge inspection report was late

Why 1: Inspector didn't have access to inspection software → Why 2: License expired → Why 3: IT wasn't notified → Why 4: No renewal process existed → Why 5: No software asset management policy

Root Cause: Lack of software asset management policy

15. SWOT Analysis

Data Analysis Strategic

What It Is

Analysis of Strengths, Weaknesses, Opportunities, and Threats — used to identify internal and external factors affecting the project or organization.

Where Used

  • Risk identification (Uncertainty domain)
  • Project initiation / business case
  • Strategic planning

Method

InternalExternal
PositiveStrengths (S)Opportunities (O)
NegativeWeaknesses (W)Threats (T)

After identification: develop SO strategies (use strengths to exploit opportunities), WO strategies (overcome weaknesses using opportunities), ST strategies, and WT strategies (defensive).

16. Risk Probability & Impact Assessment

Data Analysis Risk

What It Is

A qualitative risk analysis method that assesses each identified risk for its likelihood of occurring (Probability) and the effect it would have on project objectives (Impact).

Where Used

  • Uncertainty domain — qualitative risk analysis
  • Risk prioritization

Method

  • Assign probability: Very Low (0.1) → Very High (0.9)
  • Assign impact: scale 0.05 → 0.80
  • Risk Score = Probability × Impact
  • Plot on Probability & Impact Matrix (P×I Matrix)
  • High scores → red zone → priority response needed
Risk ScorePriorityResponse
0.54 – 0.72HIGHImmediate response required
0.18 – 0.36MEDIUMMonitor, contingency plan
0.01 – 0.12LOWAccept, watch list

17. Sensitivity Analysis

Data Analysis Risk

What It Is

A quantitative risk analysis method that determines which risks have the most potential impact on the project by examining the effect of varying one variable at a time while keeping others constant.

Where Used

  • Uncertainty domain — quantitative risk analysis
  • Cost risk assessment
  • Schedule risk assessment

Output: Tornado Diagram

A horizontal bar chart where risks are ranked from highest impact (top) to lowest (bottom), creating a tornado shape. The widest bar represents the greatest uncertainty source.

18. Monte Carlo Simulation

Data Analysis Risk Quantitative

What It Is

A computer-based simulation that runs thousands of "what-if" scenarios using probability distributions for uncertain inputs (cost, duration) to produce a range of possible outcomes with probabilities.

Where Used

  • Quantitative risk analysis (Uncertainty domain)
  • Schedule risk (determining probability of on-time completion)
  • Cost risk (probability of within-budget completion)

Method

  • Assign probability distributions (triangular, beta, normal) to uncertain inputs
  • Run 1,000–10,000 iterations randomly sampling each distribution
  • Compile results into an S-curve showing cumulative probability
  • Read off: "80% confident we'll finish by [date]" or "spend less than $X"
Example Output: "There is a 70% probability of completing within 12 months, and a 90% probability of completing within 15 months."

19. Regression Analysis

Data Analysis

What It Is

A statistical method that examines the relationship between variables to understand how one variable changes in response to another, used for forecasting and estimating.

Where Used

  • Parametric cost estimating
  • Schedule forecasting
  • Quality metrics prediction

Types

  • Simple Linear Regression: One independent variable
  • Multiple Regression: Multiple independent variables

20. Reserve Analysis

Data Analysis Cost & Schedule

What It Is

A technique used to determine how much contingency and management reserve to include in the project budget and schedule.

Types of Reserve

TypeForControlled ByIn Baseline?
Contingency ReserveKnown unknowns (identified risks)Project ManagerYes (in cost baseline)
Management ReserveUnknown unknownsManagementNo (above baseline)

Methods for Determining Contingency

  • Percentage of estimate (e.g., 10% of total cost)
  • Expected monetary value (EMV) of risk events
  • Monte Carlo simulation output at desired confidence level

21. Cost-Benefit Analysis (CBA)

Data Analysis Financial

What It Is

A systematic process of calculating and comparing benefits and costs of a project or decision to determine whether and how to proceed.

Where Used

  • Project selection and authorization
  • Quality planning (cost of quality)
  • Change request evaluation
  • Risk response planning

Key Metrics

MetricFormulaDecision Rule
Benefit-Cost Ratio (BCR)Benefits / CostsBCR > 1 = acceptable
Net Present Value (NPV)PV(benefits) – PV(costs)NPV > 0 = acceptable
Return on Investment (ROI)(Benefit–Cost)/Cost × 100%Higher is better
Payback PeriodCost / Annual BenefitShorter is better
IRRRate where NPV = 0IRR > WACC = accept

22. Assumption & Constraint Analysis

Data Analysis

What It Is

The process of exploring the validity of assumptions and constraints to identify risks arising from inaccurate, inconsistent, or incomplete assumptions.

Where Used

  • Planning domain — project initiation
  • Uncertainty (risk identification)

Method

  • Assumptions: Factors believed to be true but not yet confirmed → test for validity
  • Constraints: Binding conditions (budget cap, regulatory deadline) → identify limitations
  • Invalid assumptions become risk triggers
  • Record in Assumption Log

23. Alternatives Analysis

Data Analysis

What It Is

A technique used to evaluate identified options or approaches in order to select which approaches will be used to perform project work.

Where Used

  • Scope definition (delivery approach)
  • Resource planning
  • Schedule development (schedule compression)
  • Procurement strategy selection

24. Process Analysis

Data Analysis Quality

What It Is

A technique that examines problems, constraints, and non-value-added activities that occur during a process, identifying opportunities for improvement.

Where Used

  • Quality management
  • Continuous improvement (kaizen)
  • Process tailoring

Includes

  • Root cause analysis of process failures
  • Value stream mapping
  • Lean waste identification

25. Forecasting

Data Analysis Measurement

What It Is

Estimating or predicting future project performance and conditions based on information and knowledge available at the time of the forecast.

Types

TypeMethodBest For
Time-seriesMoving average, trend linesSchedule forecasts
Causal/econometricRegression analysisCost drivers
JudgmentalExpert opinion, DelphiNovel projects
EV-based (EAC)BAC/CPI, AC+ETCCost forecasting

26. Affinity Diagrams

Data Representation

What It Is

A method for organizing and grouping a large number of ideas, issues, or facts by their natural affinity or relationship. Commonly used after brainstorming.

Where Used

  • Requirements grouping and prioritization
  • Risk categorization
  • Lessons learned organization

Method

  • Write each idea on a separate card/sticky note
  • Group related ideas together (silently)
  • Name each group with a header card
  • Result: organized categories of information

27. Cause-and-Effect Diagrams (Fishbone / Ishikawa)

Data Representation Quality

What It Is

A visual tool that shows the relationship between a problem (effect) and its potential causes, organized into categories along a horizontal "fish spine."

Where Used

  • Quality control — identify causes of defects
  • Root cause analysis
  • Risk analysis

The 6M Categories (Manufacturing)

  • Man (People)
  • Machine (Equipment)
  • Method (Process)
  • Material
  • Measurement
  • Mother Nature (Environment)

The 4S Categories (Service)

  • Suppliers, Systems, Surroundings, Skills

28. Control Charts

Data Representation Quality

What It Is

A statistical process control chart that displays process data over time with control limits, used to determine whether a process is stable and predictable.

Where Used

  • Quality control (Delivery domain)
  • Process performance monitoring

Key Components

ComponentMeaning
UCL – Upper Control LimitMean + 3σ (not a spec limit)
LCL – Lower Control LimitMean – 3σ
MeanCenter line
Data PointsMeasurements over time

Rule of 7 (Western Electric Rules)

Out of control (special cause) if:
  • Any point beyond UCL or LCL
  • 7 consecutive points on same side of mean
  • 7 consecutive points trending up or down

29. Flowcharts

Data Representation

What It Is

A graphical depiction of a sequence of steps and decisions needed to perform a process.

Where Used

  • Process documentation and quality planning
  • Risk analysis (process failure points)
  • Stakeholder communication
  • Change control process mapping

Common Symbols

  • Oval = Start/End (Terminator)
  • Rectangle = Process/Activity
  • Diamond = Decision
  • Parallelogram = Input/Output
  • Arrow = Flow direction

30. Histograms

Data Representation Quality

What It Is

A vertical bar chart showing the frequency distribution of data, revealing patterns in distribution (normal, skewed, bimodal).

Where Used

  • Quality control analysis
  • Risk frequency analysis

Interpretation

  • Bell-shaped: Normal, stable process
  • Skewed right: Most data at low values, tail to right
  • Bimodal: Two peaks → possible two different processes mixed
  • Comb: Measurement error or grouping issue

31. Scatter Diagrams

Data Representation Quality

What It Is

A graph showing the relationship between two variables. Used to test if a cause-and-effect relationship exists or to verify a correlation.

Where Used

  • Quality control (prove/disprove cause)
  • Risk correlation analysis

Correlation Types

  • Positive correlation: Both variables increase together
  • Negative correlation: One increases as other decreases
  • No correlation: Scattered randomly — no relationship

32. Matrix Diagrams

Data Representation

What It Is

A quality management tool showing relationships between two sets of data using a grid format, with relationship strength shown at intersections.

Where Used

  • Requirements traceability matrix
  • Responsibility Assignment Matrix (RAM / RACI)
  • Stakeholder engagement matrix
  • Quality management tool

Common Matrix Types

MatrixPurpose
RACI MatrixResponsible, Accountable, Consulted, Informed
RTM – Requirements TraceabilityLinks requirements to deliverables and tests
P×I MatrixRisk probability × impact prioritization
L-shapedTwo-row/column comparison
T-shapedCompare two groups to a third

33. Hierarchical Charts

Data Representation

What It Is

Charts that display data in a hierarchical structure, breaking complex information into organized levels.

Types

ChartUse
WBS – Work Breakdown StructureHierarchical decomposition of project scope
OBS – Organizational Breakdown StructureShows org hierarchy linked to work packages
RBS – Resource Breakdown StructureCategorizes resources by type
Risk Breakdown StructureCategories and sub-categories of risk

34. Multicriteria Decision Analysis (MCDA)

Decision Making

What It Is

A structured approach to evaluate and prioritize options against multiple criteria simultaneously, assigning weights based on importance.

Where Used

  • Source selection (procurement)
  • Resource selection
  • Risk response option selection
  • Project selection/prioritization

Method

  • List all options (rows) and criteria (columns)
  • Assign weight to each criterion (totaling 100%)
  • Score each option against each criterion (1–5 or 1–10)
  • Weighted Score = Weight × Score for each cell
  • Sum weighted scores per option — highest score wins
Example Criteria: Cost, Technical Capability, Experience, Schedule, Risk, References

35. Decision Tree Analysis

Decision Making Risk

What It Is

A diagrammatic analysis tool used to evaluate multiple decision paths and their possible outcomes, incorporating probabilities and costs/benefits.

Where Used

  • Quantitative risk analysis
  • Make-or-buy decisions
  • Contract type selection

Key Concept: Expected Monetary Value (EMV)

EMV = Probability × Impact (monetary value)

Example: 30% chance of $100K loss = EMV of –$30K

Decision Node (square): points where a choice is made

Chance Node (circle): points where outcomes depend on probability

36. Voting Methods

Decision Making

Types

MethodDescriptionBest For
UnanimityAll agreeCritical decisions needing full commitment
Majority>50% agreeGeneral team decisions
PluralityLargest group wins (no majority needed)Multi-option decisions
DictatorshipOne person decidesTime-critical; clear authority
Fist-to-FiveShow fingers 0(fist)–5 for support levelAgile teams, quick consensus
Dot VotingEach person gets dots to allocate to optionsPrioritizing lists

37. Force Field Analysis

Decision Making

What It Is

A technique for analyzing forces driving and restraining a change, helping to decide whether the change is feasible and how to improve chances of success.

Where Used

  • Change management
  • Risk response planning
  • Stakeholder management

Method

  • State the change/decision in the center
  • List driving forces (pushing toward change) on the left
  • List restraining forces (pushing against) on the right
  • Score each force (1–5)
  • If driving > restraining → proceed; strengthen drivers and weaken restraints

38. Analogous Estimating

Estimating

What It Is

Using historical data from a similar previous project to estimate the current project's cost, duration, or other parameters.

Characteristics

AttributeDetails
Accuracy–25% to +75% (rough)
CostLow
TimeFast
Best usedEarly project phases, limited information
RequiresExpert judgment; historical data

39. Parametric Estimating

Estimating

What It Is

A technique that uses statistical relationships between historical data and other variables (e.g., cost per unit, hours per function point) to calculate estimates.

Characteristics

AttributeDetails
Accuracy–10% to +25%
Best usedWhen unit rates are well-established
Example$200/linear foot of steel beam × 500 LF = $100,000

40. Bottom-Up Estimating

Estimating

What It Is

Estimating individual work packages at the lowest level of the WBS and then rolling up (aggregating) the estimates to obtain project totals.

Characteristics

AttributeDetails
Accuracy–5% to +10% (most accurate)
CostHigh (time-consuming)
Best usedDetailed planning phase
RequiresComplete WBS, detailed scope

41. Three-Point Estimating (PERT)

Estimating Schedule

What It Is

An estimating technique that uses three scenarios (optimistic, most likely, pessimistic) to improve accuracy by accounting for estimation uncertainty.

Formulas

MethodFormulaNotes
PERT / Beta DistributionE = (O + 4M + P) / 6Weights most likely 4×; most used
Triangular DistributionE = (O + M + P) / 3Equal weight to all three
Standard Deviation (σ)σ = (P – O) / 6PERT only
Varianceσ² = [(P – O) / 6]²

Example

O = 4 days, M = 6 days, P = 14 days

PERT E = (4 + 4×6 + 14) / 6 = (4 + 24 + 14) / 6 = 42 / 6 = 7 days

σ = (14 – 4) / 6 = 10 / 6 = 1.67 days

68% confidence range: 7 ± 1.67 = 5.33 to 8.67 days

95% confidence range: 7 ± 2(1.67) = 3.66 to 10.34 days

42. Story Points & Relative Sizing

Estimating Agile

What It Is

An agile estimating technique using relative sizing (story points) rather than absolute time to estimate the effort/complexity of user stories.

Methods

MethodDescription
Planning PokerEach team member privately selects a card, reveals simultaneously — discuss outliers
T-Shirt SizingXS, S, M, L, XL — quick relative sizing
Affinity MappingSort stories by relative size on a scale
Fibonacci Sequence1, 2, 3, 5, 8, 13, 21 — reflects uncertainty of larger items

Velocity

After several sprints, team velocity (average story points per sprint) is used for release planning: Release Date ≈ Total Story Points / Velocity

43. Active Listening

Interpersonal

What It Is

A communication skill where the listener fully concentrates, understands, responds, and then remembers what is being said.

Techniques

  • Paraphrasing: Restate what was said in your own words
  • Clarifying: Ask questions to understand
  • Reflecting: Mirror the speaker's feelings
  • Summarizing: Review key points at the end
  • Non-verbal cues: Eye contact, nodding, open posture

44. Conflict Management

Interpersonal

What It Is

A set of techniques used to resolve disagreements and conflict among project team members, stakeholders, or other parties.

5 Conflict Resolution Techniques (Thomas-Kilmann)

TechniqueAlso CalledResultWhen to Use
Collaborate / Problem SolveConfrontingWin-Win ✅Most situations — best result
CompromiseReconcilingLose-LoseTemporary solution; equal power
Smooth / AccommodateHarmonizingYieldPreserving relationship short-term
Force / DirectDirectingWin-LoseEmergency, power authority
Withdraw / AvoidRetreatingLose-Lose ❌Cool-down only; least effective
PMP Key: Collaboration/Problem Solving is ALWAYS the preferred technique. Withdrawal is NEVER a good long-term solution.

45. Emotional Intelligence (EI)

Interpersonal

What It Is

The ability to identify, assess, and manage one's own emotions and the emotions of others — essential for project leadership.

Goleman's 5 Components

ComponentDescription
Self-awarenessKnow your own emotions, strengths, weaknesses
Self-regulationControl emotions; think before acting
MotivationInner drive to achieve; optimistic under failure
EmpathyUnderstand others' feelings; serve others
Social SkillsBuild networks, influence, collaborate

46. Facilitation

Interpersonal

What It Is

The ability to guide a group effectively through a process or discussion to reach conclusions, make decisions, or solve problems.

Where Used

  • Requirements workshops
  • Risk workshops
  • Retrospectives
  • Team development sessions

Facilitator Skills

  • Neutral stance (no personal agenda)
  • Active listening and paraphrasing
  • Managing dominant/quiet participants
  • Timeboxing discussions
  • Visual recording (flip charts, whiteboards)

47. Leadership Styles

Interpersonal Team Domain

Leadership Models on PMP Exam

StyleDescriptionBest For
Servant LeadershipLeader serves the team; removes impedimentsAgile/Scrum; PMBOK 7 preferred
TransformationalInspire change; articulate visionInnovation, culture change
TransactionalReward/punishment based performanceRoutine, stable environments
Laissez-faireHands-off; team self-directsExpert teams only
AutocraticLeader decides aloneCrisis, emergencies
DemocraticTeam input in decisionsCreative, collaborative work

Situational Leadership (Hersey-Blanchard)

QuadrantStyleTeam Maturity
S1 – DirectingHigh task, low relationshipM1: Low competence, high commitment
S2 – CoachingHigh task, high relationshipM2: Some competence, low commitment
S3 – SupportingLow task, high relationshipM3: High competence, variable commitment
S4 – DelegatingLow task, low relationshipM4: High competence, high commitment

48. Negotiation

Interpersonal

What It Is

A discussion aimed at reaching a mutually acceptable agreement when parties have different or conflicting interests.

Negotiation Approaches

ApproachResult
Principled / IntegrativeWin-Win (best; interests-based)
Positional / DistributiveWin-Lose (zero sum; fixed pie)
BATNA – Best Alternative to Negotiated AgreementWalk-away option

49. Team Building

Interpersonal Team Domain

Tuckman's Team Development Model

StageCharacteristicsPM Action
1. FormingTeam assembles; polite, uncertainDirect; set clear expectations
2. StormingConflict, competing ideasCoach; facilitate conflict resolution
3. NormingConsensus, cohesion developingSupport; encourage collaboration
4. PerformingHigh productivity, trustDelegate; remove impediments
5. AdjourningProject ends; team dispersesRecognize; capture lessons learned

50. Motivation Theories

Interpersonal Team Domain

Key Theories for PMP

TheoryTheoristKey Concept
Hierarchy of NeedsMaslow5 levels: Physiological → Safety → Social → Esteem → Self-actualization
Hygiene / MotivationHerzbergHygiene factors prevent dissatisfaction; motivators create satisfaction
Theory X / YMcGregorX: people dislike work; Y: people are self-motivated
Theory ZOuchiJob security and collective decision-making motivate
Expectancy TheoryVroomEffort → Performance → Reward linkage motivates
Achievement TheoryMcClellandPeople motivated by Achievement, Power, or Affiliation

Herzberg's Factors

Hygiene Factors (Prevent Dissatisfaction)Motivating Factors (Create Satisfaction)
Salary, working conditions, supervision, policyAchievement, recognition, responsibility, advancement

51. Kickoff Meeting

Meetings

What It Is

A formal meeting held at the start of a project (or phase) to align all stakeholders and team members on objectives, expectations, roles, and communication.

Key Agenda Items

  • Project overview and charter review
  • Team introductions
  • Roles and responsibilities
  • Communication plan and reporting
  • Project schedule and milestones
  • Q&A

52. Daily Standup (Daily Scrum)

Meetings Agile

What It Is

A short (15-minute max) daily synchronization meeting for the development team to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.

Three Questions

  • What did I do yesterday?
  • What will I do today?
  • Are there any impediments/blockers?
Rules: Same time, same place. Timeboxed to 15 min. Standing recommended. Scrum Master removes impediments raised.

53. Iteration / Sprint Planning

Meetings Agile

What It Is

A meeting at the start of each sprint where the team selects items from the Product Backlog, commits to a Sprint Goal, and decomposes backlog items into tasks.

Outputs

  • Sprint Goal
  • Sprint Backlog
  • Task breakdown (hours)

54. Retrospectives

Meetings Agile

What It Is

A meeting held at the end of each iteration for the team to inspect itself and create a plan for improvements in the next iteration. Also used in predictive projects (lessons learned).

Classic Format: What Went Well / What Didn't / What to Improve

ColumnQuestion
😊 KeepWhat went well? (continue)
😞 DropWhat didn't work? (stop doing)
💡 TryWhat should we try next sprint?

55. Change Control Board (CCB) Meeting

Meetings

What It Is

A formal review meeting of the Change Control Board to evaluate change requests and decide to approve, defer, or reject them.

Process

  • Change request submitted (CR Form)
  • Impact analysis performed (scope, schedule, cost, quality, risk)
  • CCB reviews and votes
  • Decision communicated
  • If approved: update baseline, project plan, stakeholders

56. Critical Path Method (CPM)

Schedule

What It Is

A schedule network analysis technique that calculates the longest path through the network of activities — determining the minimum project duration and activities with zero float.

Key Calculations

TermFormulaMeaning
ES – Early StartForward passEarliest an activity can start
EF – Early FinishES + Duration – 1Earliest an activity can finish
LS – Late StartLF – Duration + 1Latest an activity can start without delay
LF – Late FinishBackward passLatest an activity can finish without delay
Total FloatLS – ES or LF – EFHow long can be delayed without delaying project
Free FloatES(next) – EF(current)Delay without delaying successor
Critical PathFloat = 0Longest path; any delay = project delay

Schedule Compression Techniques

TechniqueMethodCost ImpactRisk Impact
CrashingAdd resources to critical path activitiesIncreases costMay increase risk
Fast TrackingOverlap sequential activities (parallel)Minimal costIncreases risk/rework

57. Critical Chain Method (CCM)

Schedule

What It Is

A schedule network analysis technique that modifies the project schedule to account for resource constraints and incorporates buffers rather than float to protect the delivery date.

Key Buffers

  • Project Buffer: Added to end of critical chain (protects project end date)
  • Feeding Buffers: Added where non-critical chains feed into critical chain
  • Resource Buffers: Signals that key resources will be needed soon

CCM removes individual activity padding and concentrates it into strategic buffers. Based on Theory of Constraints (TOC).

58. Precedence Diagramming Method (PDM)

Schedule

What It Is

The most common method for constructing a project schedule network diagram, using boxes (nodes) to represent activities and arrows to show dependencies.

Dependency Types

TypeDescriptionMost Common?
FS – Finish-to-StartA must finish before B starts✅ Most common
SS – Start-to-StartA must start before B starts
FF – Finish-to-FinishA must finish before B finishes
SF – Start-to-FinishA must start before B finishesRarely used

Leads and Lags

  • Lead: Overlap between activities (negative lag) — acceleration
  • Lag: Waiting time between activities — delay

59. Resource Leveling & Smoothing

Schedule

What It Is

Techniques used to optimize resource allocation across the project schedule.

TechniqueDefinitionImpact on Schedule
Resource LevelingAdjust schedule so resources are never over-allocated; may delay projectOften extends schedule
Resource SmoothingAdjust within existing float; project end date NOT changedNo extension

60. Decomposition & WBS

Planning

What It Is

A technique for dividing and subdividing project scope and deliverables into smaller, more manageable components.

WBS Rules

  • 100% Rule: WBS must capture 100% of the project scope
  • Mutually Exclusive: No overlap between work packages
  • Lowest level = Work Package (can be estimated, assigned, monitored)
  • Work packages → decompose into → Activities (for schedule)
  • WBS Dictionary: Detailed description of each WBS element

Types of WBS Structures

  • Deliverable-based: (most common) — organized by what will be delivered
  • Phase-based: organized by project phases
  • Functional-based: organized by department

61. Rolling Wave Planning

Planning

What It Is

A form of progressive elaboration planning where work in the near future is planned in detail while work further out is planned at a high level and refined as more information becomes available.

Where Used

  • Projects with evolving scope
  • R&D projects
  • Hybrid approaches
  • Long-duration infrastructure projects
Construction Example: Design-Build bridge project — detailed plan for design phase, high-level plan for construction phase that gets detailed as design progresses.

62. Communication Models

Models

Basic Communication Model

Sender → Encode → Transmit (via medium) → Decode → Receiver → Feedback

Noise

Anything that distorts or interferes with the message (language barriers, technical jargon, physical noise, distractions, cultural differences).

Communication Channels Formula

N = n(n–1)/2 where n = number of stakeholders
Example: 10 stakeholders → 10(9)/2 = 45 channels

Communication Methods

MethodDescription
InteractiveReal-time exchange (meetings, calls) — most effective
PushInformation sent to recipients (email, reports) — sender not sure it's received
PullRecipients access info themselves (intranet, repository)

63. Change Models

Models

ADKAR Model (Prosci)

LetterStands ForMeaning
AAwarenessKnow why change is needed
DDesireWant to participate and support
KKnowledgeKnow how to change
AAbilityImplement the required skills
RReinforcementSustain the change

Kotter's 8-Step Model

  • Create urgency → Build guiding coalition → Form vision → Communicate vision → Remove obstacles → Short-term wins → Consolidate gains → Anchor in culture

Virginia Satir Change Model

Status Quo → Foreign Element (trigger) → Chaos → Practice & Integration → New Status Quo

64. Complexity Models

Models

Cynefin Framework (Dave Snowden)

DomainSituationApproach
Clear (Simple)Known cause-effect; best practiceSense → Categorize → Respond
ComplicatedExpert analysis needed; good practiceSense → Analyze → Respond
ComplexEmerging patterns; no clear cause-effectProbe → Sense → Respond (Agile)
ChaoticCrisis; no patternsAct → Sense → Respond
DisorderUnknown which domain appliesBreak into components

Stacey Matrix

Plots projects on two axes — Requirements certainty (x-axis) and Technology certainty (y-axis) — to recommend Simple, Complicated, Complex, or Chaotic management approaches.

65. Tuckman's Team Development

Models

See Section 49 – Team Building for the full Tuckman's model with all 5 stages.

Drexler-Sibbet Team Performance Model

StageQuestionState
1. OrientationWhy am I here?Creating
2. Trust BuildingWho are you?Resolving
3. Goal ClarificationWhat are we doing?Creating
4. CommitmentHow will we do it?Resolving
5. ImplementationWho does what?Sustaining
6. High PerformanceWOW!Renewing
7. RenewalWhy continue?Sustaining

66. Servant Leadership Model

Models

What It Is

A leadership philosophy in which the leader's primary goal is to serve others — the team, organization, and community — rather than to exercise power or authority. Heavily emphasized in PMBOK 7 and Agile.

Key Servant Leader Behaviors

  • Remove impediments from team's path
  • Facilitate (not dictate) decision-making
  • Create a psychologically safe environment
  • Actively listen and show empathy
  • Develop team members' capabilities
  • Focus on team needs before personal agenda
  • Share credit; accept blame

67. Tools & Techniques by Performance Domain

Performance DomainPrimary Tools & Techniques
StakeholderInterviews, Surveys, Stakeholder Mapping (Power/Interest Grid, Salience Model), Brainstorming, Document Analysis, Communication Models
TeamEmotional Intelligence, Conflict Management, Negotiation, Leadership Models, Tuckman's Model, Motivation Theories, Team Building, Active Listening
Development Approach & Life CycleCynefin Framework, Stacey Matrix, Tailoring techniques, Agile methods (Scrum, Kanban)
PlanningDecomposition/WBS, Rolling Wave Planning, CPM, PERT, PDM, Analogous/Parametric/Bottom-Up/Three-Point Estimating, RACI Matrix, Risk Register
Project WorkAudits, Meetings, Change Control, Document Control, Issue Log, Assumption Log, Procurement
DeliveryRequirements Traceability Matrix, User Stories, Definition of Done, Acceptance Criteria, Quality Audits, Control Charts, Flowcharts, Checklists
MeasurementEVA (EV, PV, AC, CPI, SPI, EAC), KPIs, Variance Analysis, Trend Analysis, Forecasting, Dashboards, Burndown Charts
UncertaintySWOT, Risk Register, P×I Matrix, Decision Tree / EMV, Monte Carlo, Sensitivity Analysis / Tornado Diagram, Risk Response Strategies

68. EVA Formulas Quick Reference

MetricFormulaGood Result
Cost Variance (CV)EV – ACPositive (+)
Schedule Variance (SV)EV – PVPositive (+)
Cost Performance Index (CPI)EV / AC> 1.0
Schedule Performance Index (SPI)EV / PV> 1.0
Estimate at Completion (EAC) – typicalBAC / CPI
EAC – if future at budget rateAC + (BAC – EV)
EAC – if future at different rate (c)AC + (BAC – EV) / c
Estimate to Complete (ETC)EAC – AC
Variance at Completion (VAC)BAC – EACPositive (+)
TCPI (to meet BAC)(BAC – EV) / (BAC – AC)≤ 1.0 achievable
TCPI (to meet EAC)(BAC – EV) / (EAC – AC)≤ 1.0 achievable

69. PERT Formula Reference

FormulaEquation
PERT Expected DurationE = (O + 4M + P) / 6
Standard Deviationσ = (P – O) / 6
Varianceσ² = [(P – O) / 6]²
68% confidence rangeE ± 1σ
95% confidence rangeE ± 2σ
99.7% confidence rangeE ± 3σ

Sigma Levels (Process Quality)

Sigma LevelDefects per MillionQuality %
690,00068.27%
45,50095.45%
2,70099.73%
3.499.9997%

70. Complete Tools & Techniques Master Matrix

#Tool / TechniqueCategoryPrimary Domain(s)Key Output
1BrainstormingData GatheringUncertainty, PlanningRisk list, Requirements
2InterviewsData GatheringPlanning, StakeholderRequirements, Risk data
3Focus GroupsData GatheringDelivery, StakeholderRequirements
4Questionnaires/SurveysData GatheringPlanning, StakeholderRequirements data
5BenchmarkingData Gathering/AnalysisDelivery, MeasurementBest practices, metrics
6Document AnalysisData GatheringAll domainsRequirements, risks
7ChecklistsData GatheringDelivery, UncertaintyQuality metrics, risk IDs
8Check SheetsData GatheringDeliveryDefect data
9Earned Value AnalysisData AnalysisMeasurementEV metrics, forecasts
10Variance AnalysisData AnalysisMeasurementCV, SV
11Trend AnalysisData AnalysisMeasurementForecasts
12Root Cause AnalysisData AnalysisDelivery, UncertaintyCorrective actions
13SWOT AnalysisData AnalysisUncertainty, PlanningRisk/opportunity list
14Risk P&I AssessmentData AnalysisUncertaintyRisk register updates
15Sensitivity AnalysisData AnalysisUncertaintyTornado diagram
16Monte Carlo SimulationData AnalysisUncertaintyS-curve, confidence %
17Reserve AnalysisData AnalysisPlanning, MeasurementContingency reserve
18Cost-Benefit AnalysisData AnalysisPlanning, DeliveryBCR, NPV, ROI
19Assumptions AnalysisData AnalysisPlanning, UncertaintyAssumption log
20Alternatives AnalysisData AnalysisPlanningSelected approach
21ForecastingData AnalysisMeasurementEAC, ETC, completion date
22Affinity DiagramsData RepresentationPlanning, DeliveryGrouped requirements/risks
23Cause-Effect DiagramsData RepresentationDelivery, UncertaintyRoot cause categories
24Control ChartsData RepresentationDeliveryProcess stability info
25FlowchartsData RepresentationDelivery, Project WorkProcess maps
26HistogramsData RepresentationDeliveryDistribution charts
27Scatter DiagramsData RepresentationDeliveryCorrelation charts
28Matrix DiagramsData RepresentationPlanning, DeliveryRACI, RTM
29Hierarchical ChartsData RepresentationPlanningWBS, OBS, RBS
30MCDADecision MakingProcurement, PlanningWeighted scores
31Decision Tree/EMVDecision MakingUncertaintyEMV, selected strategy
32Voting MethodsDecision MakingAllTeam decisions
33Force Field AnalysisDecision MakingPlanning, StakeholderChange readiness
34Analogous EstimatingEstimatingPlanningHigh-level estimates
35Parametric EstimatingEstimatingPlanningUnit-based estimates
36Bottom-Up EstimatingEstimatingPlanningDetailed cost/schedule
37Three-Point/PERTEstimatingPlanning, UncertaintyExpected values, ranges
38Story PointsEstimatingPlanning (Agile)Velocity, release plan
39Active ListeningInterpersonalAll domainsShared understanding
40Conflict ManagementInterpersonalTeamResolved conflict
41Emotional IntelligenceInterpersonalTeam, StakeholderTeam cohesion
42FacilitationInterpersonalAll domainsMeeting outcomes
43Leadership StylesInterpersonal/ModelsTeamTeam performance
44NegotiationInterpersonalTeam, ProcurementAgreements
45Team BuildingInterpersonalTeamHigh-performing team
46Motivation TheoriesModelsTeamMotivated team
47CPMSchedulePlanning, MeasurementCritical path, float
48Critical ChainSchedulePlanningBuffer-based schedule
49PDMSchedulePlanningNetwork diagram
50Resource Leveling/SmoothingSchedulePlanningOptimized schedule
51Decomposition/WBSPlanningPlanning, DeliveryWBS
52Rolling Wave PlanningPlanningPlanningProgressive plan
53Kickoff MeetingMeetingsTeam, StakeholderAligned team
54Daily StandupMeetingsProject WorkImpediment list
55RetrospectivesMeetingsTeam, DeliveryImprovement actions
56CCB MeetingMeetingsProject WorkChange decisions
57Communication ModelsModelsStakeholder, TeamEffective communication
58Change Models (ADKAR, Kotter)ModelsStakeholderChange adoption
59Cynefin / Stacey MatrixModelsDev ApproachApproach selection
60Servant LeadershipModelsTeamEmpowered team