📊 PMP Visual Mastery: Every Chart, Graph & Table Explained

• The Critical Path is the LONGEST path through the network, NOT necessarily the path with the most activities.
• If a question asks "what happens to the project end date if Task X is delayed by 2 days?" — check if Task X is on the critical path. If yes → project delays 2 days.
• LeadNegative lag. B starts BEFORE A finishes. e.g. Lead = -2d means B starts 2 days early. compresses the schedule; LagPositive waiting time between tasks. e.g. Lag = 2d means wait 2 days after A finishes before B starts. adds waiting time.
• Free Float = how much a task can be delayed without affecting the NEXT task.
• Total Float = how much a task can be delayed without affecting PROJECT END.

• Gantt Chart = Bar Chart — they are the SAME thing on the exam.
• When asked which tool is BEST for communicating schedule to stakeholders → Gantt Chart.
• When asked which tool shows dependencies → Network Diagram.
• Milestone Chart = Gantt with only diamond-shaped milestones (no bars).

• Milestone = zero duration event. Never confuse with a task/activity.
• Used for high-level tracking with executives — not for day-to-day team management.
• A delayed milestone with no float = schedule risk requiring immediate corrective action.

• PERT gives MORE weight to M (×4) because it's the most realistic estimate.
• If O=4, M=6, P=14 → E = (4+24+14)/6 = 42/6 = 7 days. Practice this!
• σ = (P−O)/6: If O=2, P=14 → σ = 12/6 = 2 days
• The exam LOVES asking which estimate type uses 3 points → Three-Point or PERT.

• Critical Path tasks have Float = 0. Any delay = project delay.
• Forward Pass: Add durations left to right (EF = ES + Duration).
• Backward Pass: Subtract durations right to left (LS = LF − Duration).
• If two paths converge on a node, the LARGEST EF value is used in forward pass; SMALLEST LF value is used in backward pass.
• Negative Float = project is already behind schedule.

• The S-Curve represents the Cost Baseline (PV line) — it's the approved budget.
• If EV is BELOW PV at today → SV is negative → behind schedule.
• If AC is ABOVE EV at today → CV is negative → over budget.
• BAC = highest point of PV line = total project budget.

• MEMORIZE: EV is the hero — it compares to PV (schedule) and AC (cost).
• CPI < 1 = spending MORE than the value earned. CPI = 0.8 means every $1 spent earns $0.80 of value.
• Most reliable EAC forecasting formula = BAC / CPI.
• If asked "what is the most important EVM metric?" → CPI, because cost overruns are harder to recover than schedule delays.
• TCPI > 1 = need to be MORE efficient going forward to finish on budget (harder target).

Remember: All variances start with EV (SV = EV−PV, CV = EV−AC). If EV is first and result is POSITIVE = good news. All performance indices: EV is numerator (SPI=EV/PV, CPI=EV/AC). Index >1 = good. Index <1 = bad.

• Control Chart is used to Control Quality — monitoring an ongoing process.
• Rule of Seven: 7 or more consecutive data points on SAME SIDE of mean = out of control (even if within limits).
• ±3σ control limits = 99.73% of data falls inside when process is in control.
• Do NOT confuse UCL/LCL (statistical) with USL/LSL (specification limits set by customer).

• Pareto Chart = ranked bar chart with cumulative line — used to PRIORITIZE quality improvement.
• If asked "which tool helps identify the most impactful quality issues?" → Pareto Chart.
• The 80/20 rule: 80% of defects come from 20% of causes — fix the 20%!

• Used in Plan Quality Management and Control Quality for root cause analysis.
• The EFFECT is always at the fish HEAD (right side).
• Used AFTER identifying a defect to find WHY it happened (root cause).
• Goes with: 5 Whys technique — ask "why" 5 times to drill to root cause.

• Scatter Diagram shows correlation, NOT causation.
• Used in Quality Management to test if a suspected cause relates to the defect.
• Example: "Does heat correlate with concrete curing defects?" → Use scatter diagram.

• Run Chart = NO control limits (unlike Control Chart). Shows raw data over time.
• Used to identify TRENDS (steady improvement/decline) and SHIFTS (sudden jump).
• Run Chart comes BEFORE Control Chart in quality evolution.

• Used during Perform Qualitative Risk Analysis — NOT quantitative.
• Qualitative = subjective (expert judgment). Quantitative = numerical (Monte Carlo, Decision Tree).
• Red zone risks get priority for detailed quantitative analysis and response planning.
• Risk appetite defines where you draw the red/yellow/green thresholds.

• Tornado = Quantitative risk tool (not qualitative).
• The TOP bar = the risk with the MOST impact on project objectives — address FIRST.
• Wide bar = high uncertainty. Narrow bar = low variability.

• Decision Tree = Quantitative risk analysis tool.
• □ Square node = Decision point (you choose). ● Circle node = Chance event (probability).
• Always calculate ALL branches. Choose the HIGHEST expected monetary value.
• For threats: EMV is negative. For opportunities: EMV is positive.

• RBS = hierarchical decomposition of risk categories (like WBS for scope).
• Used in Identify Risks as a prompt/checklist for finding risks.
• Common categories: Technical, External, Organizational, Project Management.

• Also called Power/Influence Grid (replaces Interest with Influence).
• The sponsor = typically HIGH POWER / HIGH INTEREST.
• A regulator = HIGH POWER / LOW INTEREST (keep satisfied).
• End users = LOW POWER / HIGH INTEREST (keep informed).

• The goal is always to close the gap between C (current) and D (desired) level.
• Created during Plan Stakeholder Engagement and updated throughout.
• If the exam shows C<D → engagement strategy needed. If C=D → good.

• WBS is deliverable-oriented (nouns), NOT activity-oriented (verbs).
• WBS DictionaryDocument describing each WBS element – includes description, responsible party, cost account, schedule milestones, quality requirements. defines each element in detail.
• Scope BaselineScope Statement + WBS + WBS Dictionary = Scope Baseline. Used to measure scope performance. = Scope Statement + WBS + WBS Dictionary.
• Gold plating = adding unauthorized features → BAD — even if helpful!

• Only ONE A (Accountable) per activity — two Accountables creates confusion!
• RACI = type of RAMResponsibility Assignment Matrix – maps project roles to WBS elements. RACI is the most common format. (Responsibility Assignment Matrix).
• Used in Resource Management to clarify who does what.

• Burndown chart = primary Agile/Scrum progress tracking tool.
• Reviewed daily in stand-up meeting (Daily Scrum15-minute daily meeting where team discusses: What did I do yesterday? What will I do today? Any blockers?).
• Burndown shows remaining work; Burnup shows completed work — both are valid.

• Velocity = story points completed per sprint. Used to forecast how many sprints needed.
• If backlog = 200 points and average velocity = 42 → need about 5 more sprints.
• A new team has LOW velocity initially; it increases as team gels (TuckmanForming-Storming-Norming-Performing-Adjourning model of team development. Velocity improves in Performing stage. Performing stage).

• Highest cost/staffing = Executing Process Group.
• Initiating and Closing = lowest cost and staffing.
• Risk is HIGHEST early (beginning of project) but cost to fix problems is LOWEST then too.

• "The cost of change increases as the project progresses" — TRUE. This justifies thorough planning upfront.
• Stakeholder influence is HIGHEST during Initiating and LOWEST during Closing.
• This curve supports the importance of requirements gathering early.

• These two curves always appear together on the PMP exam.
• Message: front-load decisions, requirements, and planning to minimize cost and maximize influence.
• In Agile, this is addressed by continuous delivery and early feedback loops.

• FFP = most common; buyer loves it, seller takes risk.
• CPFF = seller's favorite; buyer takes ALL cost risk.
• T&M = hybrid; used for staff augmentation. Buyer risk if no limit (add NTENot-to-Exceed clause added to T&M contracts to cap buyer's cost exposure. clause!).
• Cost-reimbursable contracts require auditing of seller's actual costs.
• All cost-reimbursable = BUYER pays actual costs PLUS a fee.

• Formula: n(n-1)/2 where n = total number of stakeholders (including PM).
• Adding one person = you add n NEW channels (where n is the ORIGINAL team size).
• "Team grows from 10 to 13 members" → Original=45, New=13×12/2=78, Change=+33 channels.
• This justifies why large project teams need formal Communication Management Plans.

• Only 2 processes in Initiating: Develop Project Charter + Identify Stakeholders.
• Only 1 process in Closing: Close Project or Phase.
• Planning has the MOST processes — this is where PM earns their keep!
• M&C monitors EVERY knowledge area — "Monitor and Control Project Work" is the umbrella.
• Quality is the only area with DIFFERENT verbs: Plan → Manage (Executing) → Control.