How to use this PMP flashcard deck

PMP questions often ask what you should do next in a situation, rather than whether you can repeat a definition. A useful flashcard therefore needs to train a decision: identify the immediate concern, choose a proportionate action, and involve the right people before jumping to a solution.

Work through the deck one card at a time. Read the question, commit to an answer, then reveal and compare it with the answer. Grade yourself honestly: choose “Again” if you could not produce the action, “Hard” if you needed a long pause, “Good” if you recalled it correctly, or “Easy” if it came promptly and clearly. The grade is about your recall, not how familiar the topic feels.

The answers below are compact enough for flashcard review, but each should prompt you to explain why that action is best in the scenario. In particular, notice when a card calls for direct team discussion, when it calls for governance, and when the right move is to assess before acting.

The deck: best next action

This 16-card deck focuses on decisions that recur across technology projects: a threatened release, a proposed scope change, a delivery problem, or a team disagreement. It is not a claim about the exact wording or number of questions on the PMP exam. Check PMI’s official website for the current exam content outline and policies.

A deck on this topic ends up looking like this:

Cards — PMP — Situational judgement16 due

A sponsor asks you to add a feature to a predictive project. The team says it will affect the approved scope. What should you do first?

Clarify the request and assess its impact with the relevant team members; then follow the project’s change control process.

All 16 cards
A sponsor asks you to add a feature to a predictive project. The team says it will affect the approved scope. What should you do first?Clarify the request and assess its impact with the relevant team members; then follow the project’s change control process.
An agile team reports that a planned item is too large to complete in the next iteration. What is the best next action?Work with the product owner and team to clarify and split the item, then reprioritise it if needed.
A developer identifies a security weakness shortly before a software release. What should you do first?Assess the risk and impact with the appropriate technical and security stakeholders, then agree on a response before release.
Two team members disagree about a technical approach and delivery is slowing. What should you do?Facilitate a discussion so they can surface evidence, constraints and options, then support a decision aligned with project goals.
A vendor warns that a key component will arrive late. What should you do first?Confirm the likely impact and available options with the vendor and team, then update the risk or issue information and communicate as needed.
A stakeholder says they were surprised by a decision that affects their department. What is the best next action?Speak with the stakeholder to understand the impact and review whether engagement and communication arrangements need to change.
A team member reports a risk that could threaten a critical milestone. What should you do?Assess probability and impact with the team, identify a response owner and action, and monitor the risk.
A change request is approved, but the project schedule still shows the old scope. What should you do next?Update the relevant plans and baselines, communicate the approved change, and track the revised work.
A team member proposes a shortcut that may bypass a required quality check. What should you do?Understand the pressure behind the proposal, explain the quality concern, and agree a compliant way to address the constraint.
A customer reports that a delivered feature does not meet an agreed acceptance condition. What should you do first?Review the agreed condition and evidence with the customer and team, then determine the appropriate corrective action.
A senior stakeholder asks you to hide a delivery issue from the customer. What should you do?Respond honestly and professionally, clarify the issue and its impact, and follow the agreed communication and escalation path.
A project is using a hybrid approach, but a team member insists every decision must follow the predictive approval route. What should you do?Check the agreed governance and tailoring for this work, then apply the appropriate decision route rather than a blanket rule.
An impediment is preventing an agile team from completing work. What is your best next action as project manager?Work with the team to understand and remove or escalate the impediment while keeping the team involved in the solution.
A stakeholder requests a change directly from a developer, outside the agreed process. What should you do?Acknowledge the request, bring it into the agreed evaluation and decision process, and make sure its impact is assessed.
A new regulation may affect a project deliverable. What should you do first?Verify the requirement with an appropriate source and compliance stakeholders, then assess its impact and required response.
A project is behind schedule, and the team proposes adding people immediately. What should you do first?Analyse the cause and likely impact with the team before choosing a response; adding people may not resolve the underlying constraint.

That is a MySummaries deck, filled with PMP material. Yours is written from your own notes. Start free

Review the decision pattern

After each answer, ask yourself three questions: What needs attention first? Who needs to be involved? What project process or working agreement applies? That sequence helps prevent a common error: taking a visible action before understanding the impact or authority to make the decision.

The cards deliberately distinguish a risk from an issue. A risk is an uncertain event that could affect objectives; assess it and plan a response before it occurs. A problem that has already happened needs active management as an issue. In either case, keep the response proportionate and make ownership clear.

Change control is not a reflexive “no” to new requests. First understand what is being requested and its likely effects on scope, schedule, cost, quality, risk and stakeholders. Then use the governance agreed for the project. An agile team may refine and reprioritise work within its decision rights; a change to an approved predictive baseline may need formal evaluation and approval. The project’s context matters.

A compact checklist behind the deck keeps the most reusable decisions together. Use it to identify what you have forgotten, then return to the cards to practise retrieval rather than simply rereading the points.

The deck’s must-not-miss core looks like this:

Must not miss corePMP — Situational judgement
Best next action: clarify the situation, assess impact and act on the most urgent risk before offering a generic solution.
Change: assess effects and use the decision rights and change control agreed for the project; communicate approved changes and update relevant plans.
People: involve affected stakeholders, communicate clearly, and facilitate team problem-solving rather than imposing a one-size-fits-all answer.
Risk and ethics: respond proactively, escalate through appropriate channels when needed, and communicate honestly.

Turn missed marks into another review

When an answer feels plausible but misses the actual next step, note exactly what made it incomplete. Perhaps you proposed a response before assessing impact, bypassed the product owner or sponsor, or treated every project as predictive. Make the correction specific enough to retrieve later: “Assess impact before recommending a schedule recovery action” is more useful than “revise project management”.

If you miss the same point twice, put it back into the review queue as a short question. MySummaries can create that follow-up from repeated missed marks, so the correction is practised as a decision rather than left as a note to reread.

A repeated-miss card might look like this:

Remediation tray

You lost this mark twice: before agreeing to a proposed scope change, what impact should you assess and which project decision process should you follow?

Add cardDismiss

Make the deck fit your project experience

For each card, change one detail and test whether your decision changes. A vendor delay may affect a contractual milestone; a security weakness may require urgent risk assessment and specialist input; a requested feature may be a backlog item or a change to an approved baseline. The best next action depends on those facts, the project’s governance and who holds the relevant decision authority.

This is also a useful way to find weak recall. If you can answer only when the scenario resembles your own workplace, practise stating the principle and then applying it to a different delivery approach. Avoid memorising a slogan such as “escalate everything” or “always follow change control”. Instead, identify the risk, authority, people and process in the scenario.

Keep the deck short enough to review consistently. After a session, revisit cards you graded “Again” or “Hard” and explain the action aloud in one or two sentences. If you cannot name who you would involve or what you would check, your answer may still be too generic.

How MySummaries helps

MySummaries turns your project-management study material into a revision board and flashcards, then schedules reviews so you can practise decisions such as these over time. Build a board from your own notes at portal.mysummaries.app.