PMP — PMI Project Management Professional Quick Review
Quick Review for PMI Project Management Professional (PMP) candidates: high-yield concepts, traps, decision rules, and practice focus.
Quick Review purpose
This Quick Review is for candidates preparing for the real PMI Project Management Professional (PMP) exam, code PMP, from PMI. It is PM Mastery review support designed to help you refresh high-yield concepts before using topic drills, mock exams, original practice questions, and detailed explanations.
The PMP exam is not mainly a memorization exam. Many questions test whether you can choose the best project-management action in a realistic situation. Expect scenario wording that asks what the project manager should do first, next, best, or to prevent a problem.
High-yield PMP mindset
Use this mindset when answer choices look similar.
| PMP scenario principle | What it usually means in an answer choice |
|---|---|
| Assess before acting | Understand the situation, review data, and identify root cause before making major changes. |
| Communicate early | Use direct, collaborative communication before escalating. |
| Escalate last | Escalate only when the project manager cannot resolve the issue within authority or process. |
| Follow the plan | Use the project management plan, governance process, change process, risk plan, communication plan, and procurement terms. |
| Protect value | Prioritize customer value, benefits, outcomes, and business alignment—not just activity completion. |
| Tailor the approach | Predictive, agile, and hybrid projects handle change, scope, planning, and delivery differently. |
| Lead the team | Remove impediments, coach, facilitate, build trust, and support team ownership. |
| Manage stakeholders | Identify interests, expectations, influence, engagement level, and communication needs. |
| Be ethical | Be transparent, fair, truthful, responsible, and respectful. Do not hide issues or manipulate data. |
| Prevent recurrence | After solving an issue, update lessons learned, processes, risk responses, or working agreements as appropriate. |
Fast scenario-question decision path
When a PMP question feels vague, slow down and classify it.
Identify the delivery approach
- Predictive: formal baselines, integrated change control, phase planning.
- Agile: backlog prioritization, iterative delivery, servant leadership, team collaboration.
- Hybrid: predictive governance plus iterative or agile delivery components.
Identify the real problem
- Stakeholder disagreement?
- Requirement or scope change?
- Risk becoming an issue?
- Team conflict or performance problem?
- Vendor or contract issue?
- Schedule, cost, quality, or value concern?
Look for the correct level of action
- First: assess, review, meet, analyze, confirm.
- Next: implement the agreed process.
- Best: choose the answer that solves the root cause and supports value.
- Prevent: plan, engage, clarify, document, communicate, or improve process.
Eliminate weak answers
- Ignoring the issue.
- Immediately escalating.
- Forcing a decision without collaboration.
- Bypassing approved process.
- Making unilateral scope, budget, or schedule changes.
- Blaming a person instead of addressing the system or root cause.
Delivery approaches: predictive, agile, and hybrid
| Approach | Common cues | Good PMP response | Common trap |
|---|---|---|---|
| Predictive | Stable requirements, defined scope, baselines, formal approvals | Plan thoroughly, control changes, manage baselines, use approved governance | Accepting scope changes without impact analysis and approval |
| Agile | Evolving requirements, short iterations, backlog, product owner, self-organizing team | Prioritize value, refine backlog, remove impediments, inspect and adapt | Treating the project manager as a command-and-control task assigner |
| Hybrid | Some fixed constraints plus adaptive delivery | Use formal governance where needed and agile practices where useful | Applying only predictive or only agile logic to every part of the project |
| Iterative | Repeated refinement of solution | Learn from feedback and improve the product | Expecting complete requirements before learning starts |
| Incremental | Deliver usable parts over time | Deliver value in slices | Waiting until the end to validate value |
Predictive change control vs. agile change handling
| Situation | Predictive logic | Agile logic |
|---|---|---|
| Stakeholder requests new feature | Document change request, analyze impact, follow change control | Add to backlog, refine, prioritize with product owner/customer |
| Approved baseline is affected | Evaluate scope, schedule, cost, quality, risk, resources, procurement impacts | Reprioritize backlog and adjust future work while protecting iteration commitments |
| Team discovers missed requirement | Determine whether it changes baseline; process accordingly | Clarify value, acceptance criteria, and priority |
| Customer changes priority | Use change process if baselines are affected | Product owner/customer reorders backlog based on value |
| Work in current iteration is disrupted | Avoid uncontrolled changes during iteration unless urgent | Discuss with product owner/team; protect focus while adapting responsibly |
Core artifacts to recognize
| Artifact | Purpose | Exam cue |
|---|---|---|
| Project charter | Formally authorizes the project and names high-level objectives, authority, and stakeholders | New project lacks authority or unclear purpose |
| Business case | Explains business need, justification, and expected value | Question asks why the project should exist |
| Benefits management plan | Tracks intended benefits and realization | Question asks about value after delivery |
| Project management plan | Integrated plan for how the project is managed | Question asks what process or plan to follow |
| Scope baseline | Approved scope statement, WBS, and WBS dictionary | Question involves scope control in predictive work |
| Requirements traceability matrix | Links requirements to business needs and deliverables | Requirement is unclear, missing, or disputed |
| Product backlog | Ordered list of product work in agile | Agile priority or requirement change question |
| Stakeholder register | Identifies stakeholders and key information | New stakeholder or missed expectation |
| Stakeholder engagement plan | Strategy for engaging stakeholders | Resistant or disengaged stakeholder |
| Communications management plan | Who needs what information, when, how, and why | Communication breakdown or wrong audience |
| Risk register | Identified risks, owners, responses, status | Uncertain future event |
| Issue log | Current problems requiring action | Risk has already occurred |
| Change log | Tracks change requests and decisions | Approved/rejected/pending change confusion |
| Lessons learned register | Captures learning during the project | Preventing repeat problems |
| Procurement documents | RFPs, statements of work, contracts, evaluation criteria | Vendor selection or contract issue |
| Team charter / working agreement | Team norms, values, decision rules, behavior expectations | Team conflict, norms, or collaboration issue |
People domain quick review
Leadership style
PMP scenarios often reward leadership that is collaborative, ethical, and situational.
| Situation | Best leadership tendency |
|---|---|
| Team is blocked | Remove impediments and help the team proceed |
| Team lacks skill | Coach, train, pair, mentor, or arrange support |
| Team conflict | Facilitate discussion and seek collaborative problem solving |
| Team is mature and capable | Empower the team and support self-organization |
| Stakeholder is resistant | Understand concerns, engage, communicate value, and manage expectations |
| Urgent safety or compliance concern | Act promptly and responsibly; do not ignore or conceal |
Conflict management
| Conflict response | When it may fit | PMP caution |
|---|---|---|
| Collaborate / problem solve | Important issue, time to address root cause | Usually the strongest long-term answer |
| Compromise | Need an acceptable middle ground | May not solve root cause |
| Smooth / accommodate | Preserve relationship or minor issue | Can hide real problems |
| Withdraw / avoid | Cooling-off period or trivial issue | Usually weak if the issue is important |
| Force / direct | Emergency, safety, or urgent authority decision | Often wrong if used just to avoid discussion |
Stakeholder engagement
High-yield steps:
- Identify all stakeholders early and continuously.
- Analyze interest, influence, expectations, impact, and communication needs.
- Plan engagement strategies.
- Communicate in the right format and frequency.
- Monitor engagement and adapt.
Common PMP trap: choosing an answer that sends more status reports when the real issue requires a conversation, expectation alignment, or stakeholder engagement strategy.
Communication methods
| Method | Best use | Trap |
|---|---|---|
| Interactive communication | Complex, sensitive, urgent, or ambiguous topics | Avoiding conversation by sending a document |
| Push communication | Sending information to specific recipients | Assuming it was understood |
| Pull communication | Large audience, self-service information | Using it for urgent conflict or negotiation |
| Face-to-face / live discussion | Conflict, trust, negotiation, sensitive issues | Overusing formal escalation before direct engagement |
| Information radiator / dashboard | Visibility and transparency | Treating dashboard data as a substitute for stakeholder management |
Process domain quick review
Integration management logic
Integration is about keeping the whole project aligned. On the exam, integration questions often involve tradeoffs across scope, schedule, cost, quality, risk, resources, procurement, and stakeholders.
| If the question says… | Think… |
|---|---|
| A change affects scope, schedule, or cost | Analyze impact and follow change control |
| Different plans conflict | Integrate and reconcile; do not manage in silos |
| Team is doing unapproved work | Confirm scope and change status |
| Multiple problems are emerging | Identify root cause and coordinate response |
| Sponsor asks for a major change | Respect governance; sponsor influence does not bypass process |
| Project no longer supports business value | Reassess alignment and communicate with appropriate stakeholders |
Scope and requirements
| Concept | Quick review |
|---|---|
| Product scope | Features and functions of the product, service, or result |
| Project scope | Work needed to deliver the product, service, or result |
| WBS | Decomposition of project scope into manageable work packages |
| Scope baseline | Approved scope statement, WBS, and WBS dictionary |
| Scope creep | Uncontrolled expansion of scope without approved change |
| Acceptance criteria | Conditions that determine whether deliverable is acceptable |
| Definition of Done | Shared understanding of completion, especially common in agile contexts |
Common trap: approving “small” extra work without evaluating cumulative impact.
Schedule management
Know the reasoning more than the math.
| Term | Meaning | Exam cue |
|---|---|---|
| Critical path | Longest path through the schedule; determines shortest project duration | Delay on critical path delays project unless corrected |
| Total float | Time an activity can slip without delaying project finish | Zero float often indicates critical path |
| Free float | Time an activity can slip without delaying successor | Useful for local scheduling flexibility |
| Lead | Acceleration; successor can start before predecessor fully finishes | “Start early” relationship |
| Lag | Waiting time between activities | “Wait three days after” |
| Fast tracking | Perform work in parallel | Adds risk and rework potential |
| Crashing | Add resources to shorten duration | Adds cost; not always possible |
| Rolling wave planning | Plan near-term work in detail, future work at higher level | Useful when details emerge over time |
Cost and earned value
Memorize the direction of the core indicators.
| Metric | Formula | Interpretation |
|---|---|---|
| Planned Value | PV | Budgeted value of scheduled work |
| Earned Value | EV | Budgeted value of completed work |
| Actual Cost | AC | Actual cost of completed work |
| Cost Variance | CV = EV - AC | Positive is under budget; negative is over budget |
| Schedule Variance | SV = EV - PV | Positive is ahead; negative is behind |
| Cost Performance Index | CPI = EV / AC | Greater than 1 is favorable; less than 1 is unfavorable |
| Schedule Performance Index | SPI = EV / PV | Greater than 1 is favorable; less than 1 is unfavorable |
| Estimate at Completion | EAC = BAC / CPI | Common forecast if current cost performance continues |
| Estimate to Complete | ETC = EAC - AC | Forecast remaining cost |
| Variance at Completion | VAC = BAC - EAC | Positive is favorable; negative is unfavorable |
Fast interpretation:
- CPI below 1: getting less value per unit of cost than planned.
- SPI below 1: progressing slower than planned.
- Negative CV: over budget.
- Negative SV: behind schedule.
- If a question asks what to do after seeing bad performance, do not just report the number. Analyze cause and plan corrective action.
Quality management
| Concept | Quick review |
|---|---|
| Quality | Degree to which requirements are met |
| Grade | Category or rank; low grade is not automatically low quality |
| Prevention over inspection | Build quality in rather than finding defects late |
| Cost of quality | Prevention, appraisal, internal failure, external failure |
| Quality assurance | Process-focused confidence that quality practices are followed |
| Quality control | Product/deliverable-focused inspection and testing |
| Continuous improvement | Incremental process improvement based on learning |
| Root cause analysis | Identify the underlying cause, not just the symptom |
| Retrospective | Agile inspect-and-adapt event for process improvement |
Common trap: adding inspection after defects appear when the better answer is to improve the process causing defects.
Resource and team management
| Situation | Better PMP action |
|---|---|
| Functional manager will not release a resource | Discuss needs, negotiate, review resource plan, escalate only if needed |
| Team member lacks skill | Provide training, coaching, pairing, or mentoring |
| Team member is underperforming | Discuss privately, understand cause, support improvement |
| Team is demotivated | Address impediments, clarify purpose, empower, recognize contributions |
| Team members disagree technically | Facilitate decision using evidence, acceptance criteria, and team norms |
| Remote team has confusion | Improve communication channels, working agreements, and shared understanding |
Risk management
Distinguish risk from issue.
| Item | Meaning | Response |
|---|---|---|
| Risk | Uncertain future event | Plan response before it occurs |
| Issue | Current problem or event that has occurred | Actively resolve and track |
| Risk owner | Person responsible for monitoring and response | Assign clearly |
| Contingency reserve | Budget/time for known identified risks | Used according to risk plan |
| Management reserve | Reserve for unknown-unknowns | Usually controlled outside routine project use |
| Secondary risk | New risk caused by a response | Identify and manage |
| Residual risk | Remaining risk after response | Monitor |
Threat responses:
| Response | Meaning |
|---|---|
| Avoid | Change plan to eliminate threat |
| Mitigate | Reduce probability or impact |
| Transfer | Shift some impact to third party, often through contract or insurance |
| Accept | Acknowledge and monitor; active acceptance may include contingency |
Opportunity responses:
| Response | Meaning |
|---|---|
| Exploit | Ensure opportunity happens |
| Enhance | Increase probability or impact |
| Share | Partner to capture opportunity |
| Accept | Take advantage if it occurs without proactive pursuit |
Common trap: treating every risk as something to escalate. The project manager should manage risks through the risk process, owners, responses, and monitoring.
Procurement management
| Contract type | Cost risk tendency | Best fit | PMP caution |
|---|---|---|---|
| Fixed-price | More seller risk if scope is clear | Well-defined deliverables | Scope changes still need formal handling |
| Cost-reimbursable | More buyer risk | Uncertain or evolving work | Requires strong oversight |
| Time and materials | Mixed risk | Staff augmentation or unclear duration | Use caps and controls where appropriate |
| Incentive contracts | Shared performance motivation | Cost, schedule, or quality targets | Incentives must be measurable |
| Procurement statement of work | Defines seller work | Vendor clarity | Ambiguity leads to disputes |
Vendor-related traps:
- Do not directly manage seller employees as if they are internal team members.
- Use contract terms, procurement procedures, and documented communication.
- For disputes, follow the contract’s dispute or claims process.
- For seller performance issues, document facts and work through the agreed procurement process.
Business environment quick review
Value and benefits
The PMP exam often asks whether the project still supports organizational value.
| Concept | Exam meaning |
|---|---|
| Business value | Net benefit delivered to the organization or customer |
| Benefits realization | Confirming intended benefits are achieved over time |
| Product success | Not just “delivered on time”; must satisfy need and value |
| Project alignment | Work should remain aligned with strategy and business case |
| Change adoption | Users and stakeholders must be ready to use the outcome |
| Transition planning | Moving deliverables into operations or customer use |
Common trap: focusing only on schedule performance when the real problem is that the product no longer delivers the intended benefit.
Compliance, governance, and organizational change
| Situation | Better response |
|---|---|
| New regulation or compliance requirement affects project | Assess impact, engage appropriate stakeholders, update plans through process |
| Organization changes strategy | Revalidate project alignment and business case |
| New executive sponsor joins | Brief sponsor, confirm expectations, review objectives and governance |
| Users resist the new solution | Plan change management, training, communication, and feedback |
| Benefits are unclear | Revisit business case, success criteria, and stakeholder expectations |
Agile and hybrid quick review
Agile roles and responsibilities
| Role or function | High-yield responsibility |
|---|---|
| Product owner / customer representative | Prioritizes backlog based on value and stakeholder needs |
| Agile lead / servant leader | Facilitates, removes impediments, supports team performance |
| Development team / delivery team | Self-organizes to deliver increments |
| Stakeholders | Provide feedback, clarify needs, validate value |
| Project manager in hybrid context | Integrates governance, delivery, stakeholder, risk, and organizational needs |
Agile events and artifacts
| Item | Purpose |
|---|---|
| Product backlog | Ordered list of desired product work |
| Backlog refinement | Clarify, split, estimate, and reorder work |
| Iteration / sprint planning | Decide work for the upcoming iteration |
| Daily coordination | Inspect progress and surface impediments |
| Review / demo | Get feedback on completed product increment |
| Retrospective | Improve team process and collaboration |
| Increment | Usable completed product portion |
| Definition of Done | Shared completion standard |
| Acceptance criteria | Conditions for accepting a backlog item |
Common trap: choosing an answer that has the agile lead assign all tasks. Agile teams usually plan and organize their own work, while the leader facilitates and removes impediments.
Agile metrics and interpretation
| Metric | What it helps answer | Trap |
|---|---|---|
| Velocity | How much work the team completes per iteration | Do not use it to compare different teams mechanically |
| Burn-down chart | Work remaining over time | A chart is a signal, not a root-cause explanation |
| Burn-up chart | Work completed and scope trend | Useful when scope changes |
| Cumulative flow diagram | Flow, bottlenecks, work in progress | Do not ignore visible bottlenecks |
| Cycle time | Time from work start to completion | Useful for flow improvement |
| Lead time | Time from request to delivery | Useful for customer responsiveness |
Common PMP traps
| Trap answer | Why it is usually wrong |
|---|---|
| “Escalate to the sponsor immediately” | Often skips project-manager responsibility and direct resolution |
| “Tell the team exactly how to do the work” | Often violates empowerment or servant leadership |
| “Approve the customer’s change because they asked” | Ignores impact analysis and change process |
| “Reject all changes because the scope is baselined” | Ignores legitimate change control or backlog reprioritization |
| “Update the schedule immediately” | May skip analysis, approval, or root-cause review |
| “Add more resources” | May not solve the cause; can increase cost and communication complexity |
| “Send an email to resolve conflict” | Sensitive conflict often needs interactive communication |
| “Wait until the next status meeting” | Weak if the issue is urgent or high impact |
| “Remove the team member” | Usually premature before coaching, understanding, or performance management |
| “Gold-plate the deliverable” | Adds unapproved work and risk |
| “Ignore a low-probability risk” | Risks still need appropriate analysis and monitoring |
| “Hide bad news until there is a solution” | Violates transparency and stakeholder trust |
“First,” “next,” “best,” and “except” questions
| Wording | How to respond |
|---|---|
| What should the project manager do first? | Choose assessment, clarification, review, or direct communication before action |
| What should the project manager do next? | Choose the next step in the correct process |
| What is the best action? | Choose the option that addresses root cause, value, process, and people |
| What should have been done to prevent this? | Choose planning, stakeholder engagement, risk management, communication, or clarity |
| What should the project manager avoid? | Look for the action that violates process, ethics, collaboration, or tailoring |
| Which is not true / except? | Slow down; identify the one option that does not fit the concept |
High-yield decision rules
Change request decision rules
- If predictive and a baseline may change, use change control.
- Analyze impact before approval or rejection.
- Consider scope, schedule, cost, quality, risk, resources, procurement, and stakeholder effects.
- Approved changes require updates to affected plans, baselines, documents, and communication.
- In agile, new ideas generally go to the backlog for refinement and prioritization.
Stakeholder decision rules
- If a stakeholder is newly discovered, update stakeholder information and assess impact.
- If a stakeholder is resistant, understand concerns before forcing compliance.
- If expectations are unclear, clarify and document them.
- If communication is failing, review and adapt the communications approach.
- If the sponsor gives direction that conflicts with governance, respectfully follow proper process.
Team decision rules
- Coach before replacing.
- Facilitate before dictating.
- Address conflict early and privately when appropriate.
- Build shared understanding through working agreements and clear goals.
- Remove impediments rather than blaming the team.
Risk and issue decision rules
- Future uncertainty: risk register.
- Current problem: issue log.
- Risk occurred: implement response or workaround.
- Unknown problem: analyze root cause.
- Repeated issue: update lessons learned and improve process.
Quality decision rules
- Prevent defects rather than inspect them late.
- Use root cause analysis for recurring defects.
- Acceptance criteria define what the customer will accept.
- Definition of Done helps ensure consistent completion.
- Quality problems can indicate process problems, not just team performance problems.
Compact review table by knowledge area
| Area | Must know | Typical exam move |
|---|---|---|
| Integration | Charter, plans, baselines, change control, lessons learned | Coordinate impacts and follow governance |
| Scope | Requirements, WBS, scope baseline, acceptance | Prevent scope creep and clarify deliverables |
| Schedule | Critical path, float, compression, rolling wave | Analyze before changing dates |
| Cost | Budget, reserves, EVM indicators | Interpret CPI/SPI/CV/SV and investigate causes |
| Quality | Prevention, control, assurance, root cause | Improve process and meet requirements |
| Resources | Team development, conflict, negotiation | Coach, facilitate, empower |
| Communications | Stakeholder-specific information flow | Use the right method and confirm understanding |
| Risk | Identification, analysis, response, monitoring | Manage uncertainty proactively |
| Procurement | Contract type, vendor performance, claims | Follow contract and procurement process |
| Stakeholders | Identify, analyze, engage, monitor | Manage expectations continuously |
| Agile delivery | Backlog, iteration, review, retrospective | Prioritize value and inspect/adapt |
| Business environment | Benefits, compliance, change adoption | Keep project aligned to value |
Final quick self-check
Before moving into practice questions, confirm you can answer these without notes:
- When does a predictive project need formal change control?
- How does an agile team handle a new requirement?
- What is the difference between a risk and an issue?
- What does CPI below 1 mean?
- What does SPI below 1 mean?
- When is collaboration better than escalation?
- What should a project manager do before replacing a team member?
- How do you respond to a resistant stakeholder?
- What is the difference between product scope and project scope?
- Why is prevention usually better than inspection?
- What does the product owner usually prioritize?
- How do benefits and business value affect project decisions?
Using practice questions after this review
After this Quick Review, move into PM Mastery practice:
- Start with topic drills for weak areas such as change control, agile delivery, stakeholder engagement, risk, and earned value.
- Review every missed question with detailed explanations, especially when you selected an answer that escalated too early or skipped analysis.
- Use original practice questions to build scenario recognition, not just definition recall.
- Take mixed sets to practice switching between predictive, agile, and hybrid reasoning.
- Reserve full mock exams for timing, endurance, and final readiness checks.
A practical next step: choose one weak topic from the tables above, complete a focused question bank drill, and review the explanations until you can explain why the correct answer is better than the tempting one.
Continue in PM Mastery
Use this Quick Review as a final concept map, then move into PM Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original PM Mastery practice items; they are not official PMI questions, copied live-exam content, or exam dumps.