What are PMBOK 7 Common Tools? The PMBOK® Guide 7th Edition organizes tools and techniques into four major categories used across all performance domains and project types — predictive, agile, and hybrid alike.
Techniques for collecting raw information from stakeholders, documents, and environments. 7 tools.
Methods to examine, interpret, and derive meaning from collected data. 15 tools.
Visual and structural techniques to present data for understanding and communication. 12 tools.
Structured approaches to choose among alternatives. 3 tools.
Data Gathering tools are used when a project manager or team needs to collect raw inputs from people, documents, or market conditions before any analysis or decisions can happen.
| Tool | Primary Use | Output | When in Project |
|---|---|---|---|
| Brainstorming | Idea generation, risk ID | Ideas list, risk register input | Initiation, Planning |
| Checklists | Quality, completeness verification | Verified checklist | Planning, Execution, Monitoring |
| Focus Groups | Requirements, stakeholder attitudes | Documented expectations | Initiation, Planning |
| Interviews | Requirements, risks, expert opinions | Requirements docs, risk inputs | All phases |
| Market Research | Vendor capability, pricing, trends | Procurement inputs | Planning (Procurement) |
| Questionnaires & Surveys | Large group data collection | Statistical data, ratings | Planning, Closure |
| Benchmarking | Comparing to best practices/competitors | Performance targets | Planning, Monitoring |
Definition: A group creativity technique used to rapidly generate a large number of ideas, options, or solutions by encouraging free thinking and deferring judgment.
| Technique | How It Works | Best For |
|---|---|---|
| Classic Brainstorming | Open verbal session, facilitator captures ideas on whiteboard | Collocated teams, quick sessions |
| Nominal Group Technique (NGT) | Silent writing first, then round-robin sharing, then voting | Quieter team members, reduces dominance |
| Brainwriting (6-3-5) | 6 people write 3 ideas in 5 min, pass sheet, build on others' ideas | Remote teams, introverts |
| SCAMPER | Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse | Product innovation, solutions |
| Mind Mapping (as gathering) | Central topic, branch out associated ideas | Risk identification, WBS development |
Your team is identifying risks for a new highway bridge project. You have 12 team members including structural engineers, surveyors, traffic planners, and a community liaison. You run a 90-minute brainstorming session. The structural engineer mentions "foundation settlement" — this triggers the geotechnical engineer to add "variable soil bearing capacity," and the community liaison adds "public opposition to construction noise." Result: 67 risk ideas in 90 minutes vs. an estimated 12 from individual review.
Definition: A structured list of items, activities, or considerations used to verify completeness, consistency, and compliance. Checklists are derived from historical data, lessons learned, or standards.
| Type | Description | Example |
|---|---|---|
| Quality Checklist | Verifies work meets standards | Code review checklist, concrete pour inspection |
| Risk Checklist | Common risk categories to review | Technical, external, organizational, PM risks |
| Closure Checklist | Confirms all close-out activities done | Final payment, lessons learned, archiving |
| Procurement Checklist | Bid evaluation criteria | Vendor qualifications, insurance, capacity |
| Scope Checklist | Confirms all deliverables produced | 100% rule verification for WBS |
An inspector performing a routine bridge deck inspection uses a standardized IDOT checklist. Items include: deck cracking, spalling, delamination, joint condition, bearing condition, scour, drainage. Because every inspector uses the same checklist, results are consistent and comparable across all 10,000+ bridges in Illinois. The checklist was built from 40 years of lessons learned and FHWA standards.
Definition: A moderated discussion with a selected group of stakeholders (6–12 people) to gather opinions, expectations, attitudes, and ideas about a product, service, or result. Different from interviews (one-on-one) and brainstorming (idea generation without moderation focus).
| Attribute | Focus Group | Interview | Brainstorming |
|---|---|---|---|
| Group size | 6–12 people | 1 person (or small) | Any size |
| Purpose | Gather opinions/attitudes | Gather requirements/expertise | Generate ideas |
| Moderation | Trained facilitator (neutral) | Interviewer (active) | Facilitator |
| Output | Qualitative insights, themes | Specific requirements, risks | List of ideas |
| Cost | Medium | High (per person) | Low |
| Bias risk | Group dynamics / dominant voices | Interviewer bias | Anchoring |
A PM software company is launching a new scheduling module. Before development begins, they run 3 focus groups: one with construction PMs, one with IT PMs, one with agile coaches. Each group of 8 participants discusses pain points in current tools. The construction PMs emphasize Gantt-based views; the agile coaches want Kanban boards; the IT PMs want API integration. These distinct perspectives shape the product roadmap before a single line of code is written.
Definition: A formal or informal approach of eliciting information from stakeholders, subject matter experts, or sponsors through direct conversation. Can be structured (set questions), semi-structured, or unstructured.
Predetermined questions, consistent format. Best for comparing multiple interviewees.
Core questions with flexibility to probe deeper. Most common in PM practice.
Open conversation. Best for exploring unknown territory with true experts.
A PM for a $45M Tollway bridge rehabilitation project interviews: (1) The bridge engineer for technical constraints, (2) the Tollway traffic operations manager for lane closure restrictions, (3) the community liaison for noise concerns, (4) the utility coordinator for underground conflicts. Each interview is 90 minutes. The outputs feed directly into the scope statement, risk register, and schedule constraints. The interview with traffic operations reveals a critical constraint: no full-span closure on weekdays — this single insight saves 3 schedule re-works.
Definition: The process of examining industry capabilities, vendors, products, and services to determine what is available in the marketplace to meet project needs. Primarily used in procurement planning.
| Method | Description | Best Use |
|---|---|---|
| RFI (Request for Information) | Formal request to market to understand capabilities | Before writing RFP/RFQ |
| Industry conferences | Attend vendor presentations and demos | Technology, innovation landscape |
| Desk research | Review published reports, trade journals | Cost benchmarks, market trends |
| Vendor day | Host vendors to present capabilities | Complex systems procurement |
| Internet searches | Explore product catalogs, company profiles | Quick initial survey |
Before issuing an RFP for an $8M Intelligent Transportation System (ITS) upgrade on the Tollway, the PM conducts market research. She issues an RFI to 22 vendors, reviews 3 industry reports, and attends the ITS World Congress. The market research reveals: (1) only 4 vendors can meet the fiber-optic integration requirement, (2) prices range $5.2M–$9.8M, (3) a new cloud-based ATMS platform reduces hardware costs by 30%. This shapes a much more targeted RFP and realistic budget estimate.
Definition: Written sets of questions designed to quickly accumulate information from a large number of respondents. Can be paper-based, electronic, or online. Efficient for geographically dispersed stakeholders.
| Principle | Description | Bad Example | Good Example |
|---|---|---|---|
| Clear language | No jargon or double meanings | "Rate the project's synergistic value proposition" | "Rate the project's benefit to your team (1-5)" |
| One idea per question | Avoid double-barreled questions | "Was the meeting useful and was the PM responsive?" | Two separate questions |
| Avoid leading questions | Don't suggest the answer | "Don't you agree the schedule is too tight?" | "How would you rate the schedule timeline?" |
| Right scale | Match scale to data type | Yes/No for nuanced satisfaction | Likert scale (1-5) for satisfaction |
| Logical flow | Group related topics | Random order | General → specific |
Easy to analyze statistically. Best for large samples.
Richer qualitative data. Harder to analyze. Best for small samples or discovery.
At closure of a 2-year highway construction project with 340 stakeholders (contractors, inspectors, community members, agency staff), the PM sends a 15-question online survey via Microsoft Forms. 287 responses received (84% response rate). Key findings: 91% satisfied with communication frequency, 62% felt scope changes were poorly communicated, 78% would recommend the contractor again. These quantitative results directly feed the lessons learned register and improve future project communications plans.
Definition: Comparing actual or planned project practices, quality, processes, or performance to those of comparable projects or industry best practices to identify improvement opportunities and establish performance targets.
| Type | Compare Against | Example |
|---|---|---|
| Internal | Other projects in same org | Compare bridge project costs across 5 similar projects |
| Competitive | Direct competitors | Compare construction schedule to industry leaders |
| Functional | Similar function in different industry | Compare PM reporting processes to aerospace industry |
| Generic/Best-in-Class | World-class performers in any industry | Adopt Toyota's lean practices in construction |
Data Analysis tools are used to examine, model, and interpret information once it has been gathered. They transform raw data into actionable insights and project decisions.
| Tool | Primary Purpose | Key Output |
|---|---|---|
| Alternatives Analysis | Compare options/solutions | Recommended option |
| Assumption & Constraint Analysis | Validate project foundation | Risk register inputs, plan adjustments |
| Cost-Benefit Analysis | Justify project/decision financially | BCR, NPV, break-even |
| Decision Tree Analysis | Choose under uncertainty with probabilities | Expected Monetary Value (EMV) |
| Earned Value Analysis | Measure schedule and cost performance | CPI, SPI, EAC, ETC, VAC |
| Make-or-Buy Analysis | Build vs. procure decision | Procurement decision |
| Performance Reviews | Compare actual vs. planned | Variance reports |
| Process Analysis | Identify inefficiencies in processes | Process improvements |
| Root Cause Analysis | Find underlying causes of problems | Corrective/preventive actions |
| Reserve Analysis | Assess contingency and management reserve | Reserve adjustments |
| Sensitivity Analysis | Find which variables affect outcomes most | Tornado diagram, priority risk list |
| SWOT Analysis | Strategic assessment | Risks, opportunities |
| Trend Analysis | Project future performance from past data | ETC, forecasts |
| Variance Analysis | Measure deviation from plan | CV, SV, corrective actions |
| What-If Scenario Analysis | Model alternative futures | Contingency plans, schedule options |
Definition: A technique used to evaluate identified options and select which approaches or methods to use to accomplish the work of the project. Applied whenever there are multiple ways to achieve an objective.
The most common tool within alternatives analysis. Each criterion is weighted; alternatives are scored; weighted scores are summed to identify the best option.
| Criteria | Weight | Option A (Steel) | Wt×A | Option B (Concrete) | Wt×B | Option C (Hybrid) | Wt×C |
|---|---|---|---|---|---|---|---|
| Cost | 30% | 7 | 2.1 | 9 | 2.7 | 8 | 2.4 |
| Durability | 25% | 9 | 2.25 | 8 | 2.0 | 9 | 2.25 |
| Construction Speed | 20% | 8 | 1.6 | 6 | 1.2 | 7 | 1.4 |
| Maintenance | 15% | 6 | 0.9 | 9 | 1.35 | 8 | 1.2 |
| Aesthetics | 10% | 8 | 0.8 | 6 | 0.6 | 9 | 0.9 |
| TOTAL | 100% | 7.65 | 7.85 | 8.15 ✓ |
A project is 3 weeks behind schedule at the 50% completion milestone. The PM performs alternatives analysis and identifies 4 options: (1) Crash — add resources, costs +$180K; (2) Fast-track — overlap phases, adds risk; (3) Reduce scope — removes a feature, sponsor may reject; (4) Accept delay — renegotiate deadline. Using weighted scoring against criteria of cost, risk, sponsor approval, and feasibility, fast-tracking scores highest. Decision documented and approved.
Definition: Explores the accuracy of assumptions and the reality of constraints to identify risks from any that are inaccurate, incomplete, unstable, or inconsistent. Every project starts with assumptions — validating them is critical.
Factors held to be true, real, or certain without proof. Examples:
Limiting factors that affect project execution. Examples:
| ID | Assumption | Category | Owner | Probability of Invalidity | Impact if False | Risk ID |
|---|---|---|---|---|---|---|
| A-01 | Geotechnical conditions match preliminary boring data | Technical | Geotech Engr | Medium | High – cost & schedule | R-012 |
| A-02 | IDOT will approve traffic control plan in 30 days | External | PM | Low | Medium – 3 week delay | R-018 |
| A-03 | Steel prices stable for next 6 months | Market | Procurement | High | High – +$240K | R-005 |
Definition: A financial analysis tool used to determine the strengths and weaknesses of alternatives in terms of costs and benefits. Used to evaluate whether a project or decision is worth pursuing.
| Metric | Formula | Decision Rule | Exam Focus |
|---|---|---|---|
| BCR (Benefit-Cost Ratio) | Benefits ÷ Costs | BCR > 1 → viable; choose highest BCR | High frequency |
| NPV (Net Present Value) | PV of benefits − PV of costs | NPV > 0 → viable; choose highest NPV | Very high frequency |
| IRR (Internal Rate of Return) | Rate where NPV = 0 | IRR > cost of capital → viable | Medium frequency |
| Payback Period | Cost ÷ Annual benefit | Shorter is better | Medium frequency |
| ROI | (Benefits − Costs) ÷ Costs × 100% | Higher % = better | Medium frequency |
Scenario: Should we install automated bridge monitoring sensors? Cost: $2.4M. Annual savings in manual inspection: $420K. Benefit life: 10 years. Discount rate: 8%.
Definition: A diagramming and calculation technique for evaluating the implications of a chain of multiple options in the presence of uncertainty. Uses Expected Monetary Value (EMV) to choose the best decision path.
EMV = Probability × Impact (monetary value)
For a decision node: Choose the path with the highest EMV (or lowest negative EMV for costs)
| Symbol | Name | Description |
|---|---|---|
| ■ (Square) | Decision Node | A choice the PM makes — we control this |
| ● (Circle) | Chance Node | An uncertain event — probability-driven |
| ▷ (Triangle) | End Node | Final outcome with monetary value |
Decision: Build internally or buy COTS software?
Build Option:
- 60% chance project succeeds: gain $800K
- 40% chance project fails: lose $200K (rework costs)
- EMV = (0.60 × $800K) + (0.40 × −$200K) = $480K − $80K = $400K
Buy Option:
- 80% chance meets needs: gain $500K
- 20% chance requires customization: net $150K
- EMV = (0.80 × $500K) + (0.20 × $150K) = $400K + $30K = $430K
Decision: BUY COTS software (EMV $430K > $400K)
Definition: An integrated method that combines scope, schedule, and cost baselines to assess project performance and progress. It answers: "Are we getting the work we're paying for?" and "Will we finish on time and budget?"
BCWS: Budgeted Cost of Work Scheduled. What should have been done by now?
BCWP: Budgeted Cost of Work Performed. What did we actually accomplish?
ACWP: Actual Cost of Work Performed. What did we actually spend?
| Metric | Formula | Meaning | Good | Bad |
|---|---|---|---|---|
| CV (Cost Variance) | EV − AC | Over/under budget | Positive (+) | Negative (−) |
| SV (Schedule Variance) | EV − PV | Ahead/behind schedule | Positive (+) | Negative (−) |
| CPI (Cost Perf. Index) | EV ÷ AC | Cost efficiency per dollar | >1 | <1 |
| SPI (Schedule Perf. Index) | EV ÷ PV | Schedule efficiency | >1 | <1 |
| BAC (Budget at Completion) | Original total budget | What was planned to spend total | — | — |
| EAC (Est. at Completion) | AC + (BAC−EV)/CPI | Projected final cost | ≤ BAC | > BAC |
| ETC (Est. to Complete) | EAC − AC | Cost to finish remaining work | — | — |
| VAC (Variance at Completion) | BAC − EAC | Over/under at project end | Positive (+) | Negative (−) |
| TCPI (To-Complete PI) | (BAC−EV)÷(BAC−AC) | CPI needed to finish on budget | ≤1 | >1 |
A project has: BAC = $500,000 | Project is 40% complete | PV = $220,000 | EV = $200,000 | AC = $240,000
Definition: A general management technique used to determine whether particular work can best be accomplished internally or externally. Considers total cost of ownership, capability, capacity, confidentiality, and control.
Formula: Break-even units = Fixed Cost ÷ (Buy price per unit − Variable Make cost per unit)
Example: Fixed cost to set up manufacturing = $120,000. Cost per unit if made = $8. Buy price = $14 per unit.
Break-even = $120,000 ÷ ($14−$8) = 20,000 units
If you need >20,000 units → MAKE. If <20,000 units → BUY.
Definition: Structured meetings and analyses used to assess, evaluate, and compare actual project performance against the performance measurement baseline. Includes schedule reviews, budget reviews, quality reviews, and risk reviews.
| Type | Focus | Key Metrics Reviewed | Participants |
|---|---|---|---|
| Status Review | Overall project health | RAG status, milestones, issues | PM + team |
| Progress Meetings | Work completion this period | % complete, activities done | PM + team leads |
| Gate Reviews | Phase-end quality gate | Go/no-go criteria | Steering committee |
| Sprint Reviews (Agile) | Increment demonstration | Velocity, backlog burndown | Team + product owner |
| Earned Value Reviews | Cost/schedule performance | CPI, SPI, EAC, VAC | PM + sponsor + finance |
On track. No significant issues. CPI/SPI ≥ 0.95
At risk. Corrective action planned. CPI/SPI 0.85–0.95
Off track. Escalation needed. CPI/SPI < 0.85
Definition: Examines problems, constraints, and non-value-added activities identified during process operation. Includes process improvement techniques from Lean, Six Sigma, and other methodologies. Also known as value stream mapping analysis.
| Concept | Definition | Example in PM |
|---|---|---|
| Value-Added Activity | Work that transforms deliverable in a way the customer pays for | Writing code, installing bridge deck |
| Non-Value-Added (Waste) | Work that consumes resources but adds no customer value | Waiting for approvals, unnecessary meetings |
| Process Waste (8 types – Lean) | DOWNTIME: Defects, Overproduction, Waiting, Non-utilized talent, Transportation, Inventory, Motion, Extra processing | See table below |
| Cycle Time | Total time from start to finish of a process | Time from RFI submission to response |
| Bottleneck | Constraint that limits throughput of entire process | Single permit issuer for all work orders |
| Waste | Description | PM Example |
|---|---|---|
| D – Defects | Rework, errors, non-conformances | Design errors requiring re-drawings |
| O – Overproduction | Producing more than needed | Generating reports nobody reads |
| W – Waiting | Idle time waiting for input/approval | Waiting for client approval on submittals |
| N – Non-utilized talent | Underusing people's skills | PE doing tasks an inspector could do |
| T – Transportation | Unnecessary movement of information/materials | Sending documents through 5 approval layers unnecessarily |
| I – Inventory | Excess materials, WIP, documentation | Too many open RFIs clogging the system |
| M – Motion | Unnecessary movement of people | Team members traveling across site for every meeting |
| E – Extra processing | More work than customer requires | Gold-plating: adding unrequested features |
Definition: A specific technique used to identify the fundamental reason (root cause) for a problem, defect, or risk occurrence. Goes beyond symptoms to find the underlying cause so corrective/preventive actions are truly effective.
Ask "Why?" five times to drill down to root cause.
Problem: Project is 3 weeks late
Why? → Design drawings delivered late
Why? → Engineer had insufficient information
Why? → Client didn't provide geotechnical report
Why? → Client didn't know it was needed
Why? → Requirements not clearly communicated
Root Cause: Poor requirements communication → preventive: checklist of client deliverables at kick-off
Also called Ishikawa or Cause-and-Effect diagram. Visual tool showing multiple cause categories feeding into an effect (problem).
The 6M categories: Man, Machine, Method, Material, Measurement, Mother Nature (Environment)
(See Section 3.2 for full diagram)
A bridge project has 12% of concrete cylinder tests failing. The PM applies RCA using 5 Whys. Why failing? → Concrete strength below spec. Why? → Water-cement ratio too high. Why? → Water added on-site without testing. Why? → No procedure for on-site water addition. Why? → Quality plan didn't address field adjustments. Root Cause: Gap in Quality Management Plan. Corrective action: Revise QMP to require slump testing before every pour; train inspectors; no water additions without engineer approval. Result: Zero failures in next 200 tests.
Definition: A technique used to assess the amount of contingency reserves and management reserves appropriate for a project. Applied to both schedule and cost dimensions.
| Method | Description | Example |
|---|---|---|
| Percentage of estimate | Fixed % applied to total cost estimate | 10% contingency on $2M project = $200K reserve |
| Risk-based EMV | Sum of (probability × impact) for all risks | 15 risks analyzed; total EMV = $340K reserve |
| Monte Carlo simulation | Statistical model of all uncertainties; use P80 for reserve | P80 result = $2.8M; estimate = $2.5M; reserve = $300K |
Definition: Examines the degree to which the uncertainty in each project element affects the overall project objective when all other uncertain elements are held at their baseline values. Identifies which risks or variables have the greatest potential impact.
The primary visual output of sensitivity analysis. Variables are sorted by magnitude of their impact on the project objective (cost, NPV, duration). The most impactful variable is at the top — creating a "tornado" shape.
A $12M bridge project runs sensitivity analysis on 8 variables. The tornado diagram shows: #1 = Steel price volatility (±$1.8M impact), #2 = Foundation depth variability (±$900K), #3 = Weather delays (±$600K), #4 = Permit delays (±$300K). The PM allocates 60% of risk management attention to steel price risk (hedging contracts, price escalation clauses) and foundation variability (additional borings). The bottom 3 risks receive monitoring only — no active response needed.
Definition: Analyzes a project, organization, or situation by examining Strengths, Weaknesses, Opportunities, and Threats. Used to develop strategies and identify risks and opportunities.
SWOT: S: Licensed PE in 3 states, deep Tollway/IDOT expertise, established relationships. W: Small team (capacity limits), no federal highway certification yet. O: IIJA (Infrastructure Act) funding surge → 40% increase in bridge inspection needs; only 12 NBI-certified firms in Indiana. T: Large national firms entering Indiana market; INDOT may consolidate contracts to fewer large firms. Strategy: Pursue NBI certification to close capability gap; partner with larger firm as sub for federal work while building track record.
Definition: Mathematical technique that uses historical data points to project future performance, outcomes, or results. Establishes whether performance is improving, stable, or deteriorating over time.
| Pattern | What It Means | Action |
|---|---|---|
| 7 consecutive points in one direction | Non-random trend (process shift) | Investigate and act |
| 7 consecutive points above/below mean | Process has shifted | Identify cause |
| Upward trend in defects | Quality deteriorating | Root cause analysis |
| Stable line | Process in control, predictable | Monitor only |
Definition: A technique for determining the cause and degree of difference between the baseline and actual performance. Analyzes WHY a variance occurred, not just THAT it occurred.
| Variance Type | Formula | Positive = Good? | Domain |
|---|---|---|---|
| Cost Variance (CV) | EV − AC | Yes (under budget) | Cost |
| Schedule Variance (SV) | EV − PV | Yes (ahead) | Schedule |
| Budget Variance | Planned budget − Actual spend | Yes | Finance |
| Scope Variance | Baseline scope − Delivered scope | Context-dependent | Scope |
| Quality Variance | Target metric − Actual metric | Context-dependent | Quality |
Definition: A technique used to assess the feasibility of a project schedule (or cost) under adverse conditions and to prepare contingency and response plans for such risks occurring. Models alternative futures.
| Scenario | Variable Changed | Impact Measured | Contingency Plan |
|---|---|---|---|
| Key resource leaves | Remove critical resource | Schedule delay (days) | Pre-approved backup resource |
| Material price spike 30% | Increase material unit costs | Budget overrun ($) | Contingency reserve release trigger |
| Permit delays 6 weeks | Shift activities dependent on permit | Project end date slip | Use float; parallel-track other work |
| Scope addition | Add work package to schedule | Duration + cost increase | Fast-track or reduce elsewhere |
| Extreme weather (winter) | Add non-working calendar days | Critical path extension | Schedule seasonal work earlier |
The schedule shows a June 15 completion date with 12 days of float. The PM runs three what-if scenarios: (1) If utility relocation takes 3 extra weeks → project misses deadline. Response: Add utility locating to critical path, issue RFI to all utilities on Day 1. (2) If steel delivery delays 2 weeks → still have 2 days float. Response: No action but monitor. (3) If both occur simultaneously → 33-day slip. Response: Develop fast-track option to overlap girder installation and deck forming.
Data Representation tools take analyzed data and present it in visual, structural, or graphical formats to aid understanding, communication, and decision-making.
| Tool | Type | Primary Use |
|---|---|---|
| Affinity Diagrams | Grouping | Organize large amounts of ideas into categories |
| Cause-and-Effect (Fishbone) | Causal diagram | Root cause analysis visualization |
| Control Charts | Statistical chart | Monitor process stability over time |
| Flowcharts | Process diagram | Map process steps and decision points |
| Hierarchical Charts (WBS/OBS/RBS) | Hierarchy diagram | Decompose scope, organization, or risk |
| Histograms | Bar chart | Show frequency distribution of data |
| Matrix Diagrams | Grid | Show relationships between two sets of data |
| Mind Maps | Radial diagram | Visual brainstorming and organization |
| Probability & Impact Matrix | Grid | Prioritize risks by P×I scoring |
| Scatter Diagrams | Correlation chart | Show relationship between two variables |
| S-Curves | Cumulative chart | Show cumulative cost/progress over time |
| Stakeholder Engagement Matrix | Assessment grid | Compare current vs. desired engagement levels |
Definition: A technique for organizing a large number of ideas, opinions, or issues into their natural groupings based on their affinity (similarity or relationship) to allow patterns to emerge. Also called the KJ Method (Kawakita Jiro).
Definition: A visual tool that displays a sorted list of causes leading to a specific effect (problem). The diagram looks like a fish skeleton — effect on the right (head), causes as bones on the left. Used in root cause analysis and quality management.
Human error, training gaps, fatigue, communication failures
Equipment failure, calibration, maintenance, technology
Procedure gaps, workflow issues, work instructions
Defective materials, wrong specifications, supplier quality
Inaccurate instruments, test errors, measurement systems
Weather, humidity, temperature, external conditions
Definition: A graphic display of process data over time, showing the variation of a characteristic against control limits. Used to determine whether a process is stable (in control) and performing predictably.
| Component | Description | Typical Rule |
|---|---|---|
| UCL (Upper Control Limit) | Upper statistical boundary (+3σ) | Points above UCL = out of control |
| Mean (CL) | Process average | Center line |
| LCL (Lower Control Limit) | Lower statistical boundary (−3σ) | Points below LCL = out of control |
| Specification Limits | Customer requirements (not statistical) | Different from control limits! |
| Data points | Individual measurements over time | Should be randomly distributed |
A process is OUT OF CONTROL (non-random) when:
Definition: A graphical representation of a process showing the sequence of steps, decision points, inputs, outputs, and process flows. Also called process flow diagrams or process maps.
| Shape | Name | Use |
|---|---|---|
| Oval/Ellipse | Terminator | Start/End of process |
| Rectangle | Process/Activity | A step or action |
| Diamond | Decision | Yes/No question, branch point |
| Parallelogram | Input/Output | Data entering or leaving |
| Arrow | Flow | Direction of process flow |
| Cylinder | Data store | Database or file |
Definition: Visual hierarchical decomposition structures that break down project scope, organization, or risks into manageable components. The most powerful is their cross-referencing through the Responsibility Assignment Matrix (RAM).
Decomposes PROJECT SCOPE (deliverables) into work packages. "100% Rule" — captures all project work. Basis for scheduling and cost estimating.
Decomposes the PROJECT ORGANIZATION into departments/teams. Cross-referenced with WBS to assign accountability. Used in RAM/RACI creation.
Decomposes PROJECT RISKS by category. Helps ensure comprehensive risk identification. Used in Identify Risks process.
| WBS Work Package | PM | Struct. Engr | Contractor | Inspector | Client |
|---|---|---|---|---|---|
| 3.1 Bridge Deck Demolition | A | C | R | I | I |
| 3.2 Concrete Deck Pour | A | R | R | C | I |
| Design Approval | I | R | I | I | A |
| R=Responsible, A=Accountable, C=Consulted, I=Informed | |||||
Definition: A bar chart showing the frequency distribution of data. Used to understand the distribution and variation of a process or quality characteristic. Unlike a regular bar chart, histogram bars are adjacent (no gaps) representing continuous data ranges.
| Shape | What It Indicates | PM Action |
|---|---|---|
| Bell curve (normal) | Process is stable and in control | Monitor; maintain process |
| Skewed right | Most data low; outliers high | Investigate the high outliers |
| Skewed left | Most data high; outliers low | Investigate the low outliers |
| Bimodal (two peaks) | Two different processes or populations mixed | Separate and analyze each |
| Flat (uniform) | No single dominant value; possible measurement issue | Check measurement system |
Definition: A visual tool showing the relationships between groups of data. Uses a grid format where relationships between row items and column items are marked. Strength of relationship can be shown with symbols or numbers.
| Matrix Type | Shape | Use | PM Example |
|---|---|---|---|
| L-Matrix | 2D grid | Relate 2 groups | Requirements vs. Test cases |
| T-Matrix | 3 groups, 2 L-matrices | Relate 3 groups | Req's, Design, Test |
| Y-Matrix | 3 L-matrices in triangle | Relate 3 groups circularly | Stakeholders, Risks, Activities |
| RACI Matrix | Activity vs. Role | Assign responsibilities | WBS vs. Team roles |
| Traceability Matrix | Requirements vs. Source/Test | Track requirement coverage | Req ID vs. WBS/Test case |
| Req ID | Requirement | Source | Priority | WBS Ref | Test Case | Status |
|---|---|---|---|---|---|---|
| R-001 | Load capacity ≥ HS-25 | IDOT Std Specs | High | 3.2.1 | TC-014 | ✅ Verified |
| R-002 | Deck waterproofing membrane | Client req. | High | 3.3.2 | TC-022 | ⏳ In Progress |
| R-003 | LED lighting ≥ 2fc minimum | AASHTO | Medium | 4.1.3 | TC-031 | ❌ Not Started |
Definition: A diagram starting from a central concept, with associated topics and sub-topics radiating outward. Used to visually organize information, show connections between ideas, and stimulate creative thinking.
| Attribute | Mind Map | WBS |
|---|---|---|
| Structure | Radial/organic | Hierarchical/top-down |
| Purpose | Brainstorm, explore connections | Define project scope formally |
| Format | Freeform; hand-drawn or digital | Standardized; numbered elements |
| Use in PM | Risk ID, requirements gathering, planning sessions | Scope baseline, cost estimation, scheduling |
| Formality | Informal tool | Formal project document |
Definition: A grid used in qualitative risk analysis to prioritize risks by multiplying the probability (likelihood) of occurrence by the potential impact (consequence) on project objectives. Creates a risk priority score for each identified risk.
Definition: A graph that shows the relationship between two variables. Used in quality management to determine whether there is a correlation (relationship) between a potential cause and an effect. Also called a scatter plot or X-Y graph.
| Correlation | Pattern | What It Means | PM Action |
|---|---|---|---|
| Strong Positive | Points rise left to right | X increases → Y increases | More training → more defects (bad) |
| Strong Negative | Points fall left to right | X increases → Y decreases | More training → fewer defects (good!) |
| No Correlation | Random cloud of points | No relationship between variables | Look for a different cause |
| Curvilinear | Curved pattern | Non-linear relationship | Model with curve fitting |
⚠️ Correlation ≠ Causation: A scatter diagram shows correlation (statistical relationship), not causation. Even if training hours and defect rates are strongly correlated, training might not be causing the reduction — another variable could be responsible. Further analysis (RCA, experiments) is needed to confirm causation.
Definition: A display of cumulative costs, labor hours, percentage of work, or other quantities plotted against time. The resulting curve is S-shaped because projects typically start slow, accelerate during peak activity, and slow down at completion.
| Usage | What It Shows |
|---|---|
| Cost baseline vs. actuals | Are we spending as planned? |
| Resource loading | When is peak demand for labor/equipment? |
| Cash flow forecasting | When will the project need maximum funding? |
| Progress reporting | Visual confirmation of earned value status |
| Contractor invoicing | Expected payment curve for contract management |
Definition: A matrix tool that compares current engagement levels of stakeholders against desired engagement levels. Used to identify gaps and design targeted engagement strategies.
| Level | Description | Example Behavior |
|---|---|---|
| Unaware | Not aware of project or its potential impacts | Never attended meetings, doesn't respond |
| Resistant | Aware but opposed; actively working against project | Raising objections, blocking decisions |
| Neutral | Aware but neither supporting nor resisting | Attends meetings, takes no position |
| Supportive | Aware and supportive of project goals | Provides resources, attends voluntarily |
| Leading | Actively engaged; championing the project | Advocates to others, removes barriers |
Decision Making tools provide structured methods for choosing among alternatives, especially when multiple stakeholders are involved and options are complex.
Systematic scoring of alternatives against weighted criteria. Best for complex technical or vendor decisions.
Group agreement through plurality, majority, or unanimity. Best for team decisions requiring buy-in.
One person decides, often using data gathered from others. Best for urgent decisions or clear authority situations.
| Situation | Best Tool | Reason |
|---|---|---|
| Multiple criteria, multiple vendors | Multicriteria Analysis | Objective scoring prevents bias |
| Team needs ownership of decision | Voting | Builds commitment through participation |
| Crisis requiring immediate action | Autocratic | Speed; no time for consensus |
| Expert disagreement on technical solution | Multicriteria + Voting | Combine systematic scoring with group validation |
| Selecting software tool for team | Multicriteria | Objective evaluation prevents politics |
Definition: A technique that uses a decision matrix to provide a systematic analytical approach for establishing criteria — such as risk levels, uncertainty, and valuation — to evaluate and rank many ideas. Also known as Weighted Scoring Model or Decision Matrix.
| Criteria | Weight | MS Project | Wt×Score | Primavera P6 | Wt×Score | Asana | Wt×Score |
|---|---|---|---|---|---|---|---|
| Cost / Licensing | 20% | 6 | 1.20 | 4 | 0.80 | 9 | 1.80 |
| Schedule Mgmt Capability | 25% | 8 | 2.00 | 10 | 2.50 | 5 | 1.25 |
| Ease of Use | 20% | 7 | 1.40 | 5 | 1.00 | 9 | 1.80 |
| Integration with existing tools | 20% | 8 | 1.60 | 6 | 1.20 | 7 | 1.40 |
| Vendor Support | 15% | 8 | 1.20 | 9 | 1.35 | 7 | 1.05 |
| TOTAL | 100% | 7.40 | 6.85 | 7.30 |
Winner: MS Project (7.40) — despite Primavera's superior scheduling capability, its cost and ease-of-use weaknesses pull it below MS Project overall.
Definition: A collective decision-making approach where team members vote to reach a decision. Builds commitment through participation. Three main forms based on how agreement is defined.
All members agree. Strongest buy-in. Very hard to achieve. Best for: critical, high-stakes decisions requiring full commitment (safety policies, major scope changes).
>50% agreement. Most common. Creates losers who may resist. Best for: standard team decisions, preference selection, retrospective actions.
Largest block wins (even if < 50%). Useful with 3+ options. No one fully loses. Best for: multi-option selections, low-stakes preferences, agile team choices.
| Technique | How It Works | Best Use |
|---|---|---|
| Roman Voting (Thumbs) | 👍 Agree, 👎 Disagree, ✊ Need more info | Quick team pulse check |
| Dot Voting | Each person gets N dots to place on preferences | Prioritizing a long list of options |
| Delphi Technique | Anonymous rounds of voting/estimation; shares results; repeat | Expert estimation, avoiding anchoring bias |
| Planning Poker | Simultaneous card reveal; discuss outliers; re-vote | Agile story point estimation |
| Fist of Five | Show 1–5 fingers: 5=fully support, 1=strong opposition | Consensus gauge in agile |
A PM needs to estimate the probability and impact of 30 risks. She brings together 8 experts anonymously using the Delphi technique. Round 1: Each expert estimates probability and impact for each risk. Facilitator shares statistics (mean, range) but NOT who said what. Round 2: Experts revise estimates seeing the group data. Round 3: Consensus emerges for 28 of 30 risks. The two outliers receive additional discussion. Result: Unbiased risk estimates free from groupthink, anchoring, and dominant personality effects.
Definition: One individual takes on the responsibility for making the decision for the entire group. Also known as "Dictatorship" in decision-making literature. Often used with data or information gathered from others but the final call rests with one person.
| Dimension | Autocratic | Collaborative/Voting |
|---|---|---|
| Speed | Fast ✅ | Slower ❌ |
| Buy-in | Low ❌ | High ✅ |
| Quality | Depends on individual | Leverages group knowledge |
| Accountability | Clear ✅ | Diffuse ❌ |
| Risk of bias | High ❌ | Lower ✅ |
| Team morale | Can decrease ❌ | Improves ✅ |
During a routine inspection, an inspector identifies a catastrophic fatigue crack in a bridge girder. The PM (licensed PE) immediately makes an autocratic decision: close the bridge to traffic NOW, before any committee review or stakeholder consultation. The decision is made unilaterally, documented, and implemented within 30 minutes. Later review confirmed the decision was correct and likely prevented a collapse. Time for collaboration: ZERO. Time for autocratic decision: 5 minutes.
| Exam Scenario | Tool to Use | Category |
|---|---|---|
| Need to identify risks quickly from a large group | Brainstorming | Data Gathering |
| Need input from geographically dispersed stakeholders | Questionnaires/Surveys | Data Gathering |
| Need expert opinion from one or two specialists | Interviews | Data Gathering |
| Need to understand stakeholder attitudes and feelings | Focus Groups | Data Gathering |
| Need to verify nothing was missed | Checklists | Data Gathering |
| Need to compare project to best practices | Benchmarking | Data Gathering |
| Need to know what vendors exist and their capabilities | Market Research | Data Gathering |
| Need to choose between multiple solutions/vendors | Alternatives Analysis or Multicriteria | Analysis / Decision |
| Need to justify a project financially | Cost-Benefit Analysis | Data Analysis |
| Need to choose under uncertainty with probabilities | Decision Tree / EMV | Data Analysis |
| Need to measure cost and schedule performance | Earned Value Analysis | Data Analysis |
| Need to find root cause of a problem | Root Cause Analysis / 5 Whys | Data Analysis |
| Need to prioritize which risks get the most attention | Sensitivity Analysis (Tornado) | Data Analysis |
| Need to see if project is viable and what risks exist | SWOT Analysis | Data Analysis |
| Need to forecast future cost at project completion | EAC = AC + (BAC-EV)/CPI | Data Analysis |
| Need to model impact of possible future events | What-If Scenario Analysis | Data Analysis |
| Need to show whether to build or buy | Make-or-Buy Analysis | Data Analysis |
| Need to visually show causes of a quality defect | Fishbone/Ishikawa Diagram | Data Representation |
| Need to show whether process is statistically in control | Control Chart | Data Representation |
| Need to organize large numbers of ideas into themes | Affinity Diagram | Data Representation |
| Need to map all project work to deliverables | WBS Hierarchical Chart | Data Representation |
| Need to show risk priority visually | Probability & Impact Matrix | Data Representation |
| Need to show relationship between two variables | Scatter Diagram | Data Representation |
| Need to show cumulative cost over time | S-Curve | Data Representation |
| Need to check stakeholder engagement gaps | Stakeholder Engagement Matrix | Data Representation |
| Need objective multi-factor decision | Multicriteria Decision Analysis | Decision Making |
| Need team commitment to a decision | Voting (majority/unanimity) | Decision Making |
| Need anonymous expert estimation | Delphi Technique (Voting) | Decision Making |
| Emergency requiring immediate decision | Autocratic Decision Making | Decision Making |
CV = EV − AC | SV = EV − PV
CPI = EV/AC | SPI = EV/PV
EAC = AC + (BAC−EV)/CPI [most common]
EAC = BAC/CPI [when all remaining work = CPI rate]
EAC = AC + ETC [when re-estimating from scratch]
ETC = EAC − AC
VAC = BAC − EAC
TCPI = (BAC−EV)/(BAC−AC) [to complete on BAC]
TCPI = (BAC−EV)/(EAC−AC) [to complete on new EAC]
OUT OF CONTROL = 7 consecutive points on one side of mean OR 7 consecutive points trending in one direction — EVEN if all points are within UCL/LCL bounds.
| Process Group | Commonly Tested Tools |
|---|---|
| Initiating | Brainstorming, Interviews, Focus Groups, SWOT, Expert Judgment |
| Planning | WBS, Alternatives Analysis, CBA, Decision Tree, Benchmarking, Surveys, Make-or-Buy, Reserve Analysis |
| Executing | Multicriteria Decision Analysis, Flowcharts, Checklists, Voting |
| Monitoring & Controlling | EVA, Control Charts, Variance Analysis, Trend Analysis, S-Curves, P×I Matrix |
| Closing | Surveys, Interviews, Trend Analysis, Lessons Learned |
| Traditional PM Tool | Agile Equivalent |
|---|---|
| Earned Value Analysis | Burndown Charts, Velocity Tracking |
| Voting (Majority) | Planning Poker, Fist of Five |
| Performance Reviews | Sprint Reviews, Retrospectives |
| Trend Analysis | Velocity trend, Cumulative Flow Diagram |
| WBS | Product Backlog |
| What-If Scenario | Sprint simulation, Release planning |
| Fishbone / RCA | 5 Whys in Retrospective |
Final Exam Strategy: Read each question carefully for KEY WORDS: "identify" → gathering tools; "evaluate/choose" → analysis or decision tools; "display/show/visualize" → representation tools. "Probability × Impact" → P×I Matrix. "7 consecutive" → Control Chart. "EV−AC" → Cost Variance. "Anonymous estimation" → Delphi. Always select the tool that BEST fits the scenario — not just one that could work.
Eng. Ahmad Safi, PE