2.6. Reflection Checkpoint

Key Takeaways

• Classifying work (project/operations/program/portfolio) is a scenario-application skill on this exam, not a definitions quiz — look for what surrounds the work, not just how the work is described.
• Risk, issue, assumption, and constraint each answer a different question and get logged and managed differently; a risk that has occurred becomes an issue.
• The PMI Code of Ethics (responsibility, respect, fairness, honesty) applies to ordinary daily decisions, not just serious misconduct.
• The project management plan governs how the project is run; product-related documentation governs what the product will be — these are frequently confused.
• Milestones have zero duration and mark events; task duration measures the span of actual work.
• Registers (risk, stakeholder) are living documents updated continuously, not one-time reports.
• Qualitative risk analysis rates and ranks every risk (probability and impact matrix); quantitative risk analysis — Monte Carlo simulation, EMV, sensitivity analysis — numerically models an already-prioritized shortlist and is optional.
• Contingency reserve covers identified risks and sits inside the cost baseline; management reserve covers unknown risks, sits outside it, and needs approval to use.
• Project closure includes formal acceptance, resource release, lessons learned, and transition — even for canceled projects.
• PM vs. sponsor vs. team operate at different altitudes; a PM plays situational roles (initiator, negotiator, listener, coach, working member, facilitator).
• Leadership (inspiring people toward a vision) and management (planning/organizing/controlling processes) are distinct behaviors the exam tests by scenario, not by job title.
• Executing a documented plan or framework correctly is usually favored over improvising a new response.

Connecting Forward

Phase 3 shifts from "how project management works" to "how business analysis works" — Domain 4, at 27%, is the second-largest domain on the exam and one candidates commonly under-prepare. You'll cover BA roles and responsibilities, stakeholder communication, requirements gathering, product roadmaps, and how the BA's role itself changes depending on whether the project is predictive or adaptive — a direct callback to the approach distinction from Phase 1.

Self-Check Questions

• A team member tells you a vendor risk you've been tracking in the risk register "just happened this morning." What term now applies to it, and what should happen to your response plan?
• A scenario describes a PM personally sitting down with a struggling teammate for an hour to help them learn a new skill, rather than reassigning the task. Which of the PM's situational roles does this best demonstrate, and is this leadership, management, or both?
• A team rates every risk in its register on a 1–5 probability scale and a 1–5 impact scale, then runs a simulation on the four highest-scoring ones to produce a range of completion dates. Name each of the two analyses, and say which one every project performs.