How to Answer PMP Situational Questions

Most PMP questions are short project stories that ask what the project manager should do. Several options usually sound reasonable. The exam is checking whether you make the judgment call PMI expects from an experienced project manager.

That judgment follows patterns. Once you know what PMI rewards and penalizes, most questions narrow to two options quickly, and a clear method helps you choose between them.

Why Situational Questions Feel Hard

More than one option is "not wrong." The exam wants the best response for this moment, not any acceptable one.
Real-world habits get in the way. Escalating fast or fixing things yourself may be normal at work. The exam expects a PM who investigates, collaborates, and follows agreed processes.
Context changes the answer. A stakeholder asking for a new feature has a different best answer under a change control board than on an agile team with a product owner.

A Repeatable Method for Every Scenario

Use the same steps every time, even on questions that feel easy.

1. Read the last sentence first

The last sentence is usually the actual question. Read it before the scenario so you know what you are looking for. "What should the project manager do first?" is a different task from "What is the most likely cause?"

2. Identify the context

Which approach? Predictive, agile, or hybrid. Clues include sprints, backlog, product owner, and daily standups (agile) versus baselines, change control board, and work breakdown structure (predictive). A mix points to hybrid.
Who is involved? A team member, a functional manager, the sponsor, a vendor, a regulator, a customer. Your options depend on their role and on your authority over them.
What stage? Early in the project, during execution, or near closure. Stakeholder analysis is a strong answer early on. Late in the project, the same option may come too late to help.

3. Spot the real problem

Many stems include a symptom and a distraction. A team member missing deadlines is a symptom. The real problem might be unclear priorities, a skills gap, or a personal issue. Ask: what is actually going wrong, and what would fix it at the source?

4. Eliminate the weak options

Remove options that fall into the usual traps:

Escalates too early. Going to the sponsor or management before the PM has tried to resolve the issue.
Ignores the process. Changing scope, baselines, or contracts without the agreed change process, or making a change "because the customer asked."
Acts without assessing. Implementing a fix, replacing a person, or applying a risk response before understanding the situation.
Blames or avoids. Reprimanding someone publicly, pointing at another team, or waiting for the problem to go away.

5. Choose the best of what is left

Among the remaining options, prefer the response that is:

Proactive: addresses the issue now, not after it gets worse
Collaborative: involves the right people, usually starting with a direct conversation
Root-cause focused: fixes why the problem happened, not only what it caused
Within the PM's authority: something the PM can actually do without overriding someone else's role

This matches our PMP exam tips: eliminate options that ignore stakeholders, skip communication, or act unilaterally, then pick the proactive, collaborative, principle-driven answer.

Mindset Rules: Usually Right vs Usually Wrong

These are patterns, not laws. Escalating, for example, is correct when the issue truly exceeds the PM's authority. Use the table to speed up elimination, then confirm with the scenario details.

Situation	Usually right	Usually wrong
Team conflict	Meet the people involved, listen, find a collaborative solution	Decide for them, ignore it, or escalate to their manager right away
Underperforming team member	Talk privately, understand the cause, offer support or training	Remove or replace them, criticize them in a team meeting
Requested change	Assess impact, follow the change process or route to the product owner	Implement it immediately, or refuse it outright
Identified risk	Analyze it, update the risk register, plan a response with the owner	Ignore it until it happens, or apply a costly response without analysis
Risk has occurred	Implement the planned response or workaround, then update records	Start a brand-new analysis while the impact grows
Unhappy stakeholder	Meet them, understand their concerns, review the engagement approach	Avoid them, or promise what they want to make them go away
Missed deadline or variance	Find the root cause, review options with the team, communicate	Hide it, or pressure the team to work overtime as a first move
Issue beyond PM authority	Escalate with facts and options after doing what the PM can	Make the decision anyway, or escalate with no analysis
Ethical or compliance concern	Act on it, follow policy, report through the proper channel	Look the other way because the schedule is tight

Keywords That Change the Answer

A single word in the stem often decides which correct-sounding option is best.

First: several options may be good eventually. Pick the one that logically comes before the others, which is often gathering information, reviewing a document, or talking to the person involved.
Next: something has already happened in the story. Do not repeat it. If the PM has already met the stakeholder, the next step is not "meet the stakeholder."
Best: more than one option works. Choose the one that solves the root cause with the fewest side effects.
Most likely: you are asked for a cause or an outcome, not an action. Choose what best explains the situation.
Should have done: the question is about prevention, so the answer usually comes from planning.
Except / not: the logic flips. You are looking for the one option that does not fit.

Restate the question in your own words before reading the options: "They want the first action," or "They want the cause."

How Agile Scenarios Differ

In agile and hybrid scenarios the same values apply, but roles change. The PM (or scrum master or agile coach) leads by enabling, not directing.

Servant leader. The PM removes impediments, shields the team from interruptions, coaches, and facilitates. Options where the PM assigns tasks or dictates how to do the work are usually wrong.
The team self-organizes. The team decides how to do the work and who takes which item. In a technical disagreement, the team resolves it, with the PM facilitating if needed.
The product owner owns backlog priority. A stakeholder who wants a new feature works with the product owner, who decides where it goes. Neither the PM nor the team adds it to the sprint on their own.
Change is expected, but the sprint goal is protected. New work normally goes to the backlog for a future iteration, not into the middle of a sprint.
Use the right ceremony. Process issues go to the retrospective, product feedback to the review.

In hybrid scenarios, check which part of the project the question is about: a regulated component may still need formal change control while software runs in sprints. See the agile and hybrid guide.

Ethics and Compliance Cases

Some scenarios test professional responsibility rather than technique. PMI is clear on the expected behavior: honesty, responsibility, respect, and fairness.

Bribes, gifts, and favors. Decline anything that could influence a decision and follow policy.
Conflicts of interest. Disclose them to the appropriate party and step back from the decision if needed.
Pressure to report false status. Report accurate information, even when it is unwelcome. Hiding a variance to keep the sponsor happy is never the best answer.
Laws, regulations, and safety. If a shortcut would breach a regulation or put people at risk, the PM raises it and does not proceed, even if the sponsor wants the date.

An option that "keeps the project on schedule" by bending a rule is a trap. Ethics and compliance outrank schedule and cost.

Worked Example Scenarios

1. The conflict between two senior developers

On a predictive project, two senior developers disagree strongly about a design approach, and the argument is slowing the team. The question asks what the PM should do first.

The options are: escalate the disagreement to the functional manager, pick the design yourself to save time, meet with both developers to understand each position and work toward an agreed solution, or tell them to settle it on their own.

The real problem is an unresolved conflict hurting delivery. Escalating comes before the PM has tried anything. Imposing a decision damages commitment, and the PM may lack the technical depth to choose well. Telling them to sort it out is avoidance. The best answer is to meet both developers and collaborate on a solution. See conflict management questions for more practice.

2. The sponsor's new feature mid-sprint

On an agile team, the sponsor approaches the PM halfway through a sprint and asks for a new reporting feature to be added before the sprint ends. The question asks for the best response.

The options are: add it to the current sprint because the sponsor has authority, ask the team to work extra hours to fit it in, direct the sponsor to the product owner so the feature can be added to and prioritized in the product backlog, or reject the request because the scope is fixed.

The context is agile, so the product owner owns priority and the sprint goal is protected. Adding work mid-sprint or pushing overtime ignores both. Rejecting the request outright is not collaborative. The best answer routes it to the product owner and the backlog.

3. The quiet team member

In a hybrid project, a team member who used to deliver on time has missed two deadlines and seems disengaged in meetings. The question asks what the PM should do first.

The options are: report the issue to the person's functional manager, reassign their work to others, speak privately with the team member to understand what is happening, or raise the missed deadlines in the next team meeting.

The real problem is unknown, which is the point. Reporting or reassigning acts without assessing, and raising it in front of the team is public blame. The best answer is a private conversation to find the cause, then support. More practice: team building and psychological safety.

4. The resistant stakeholder

Early in a predictive project, a department head who will be affected by the new system keeps missing requirements workshops and has criticized the project to colleagues. The question asks for the best action.

The options are: ask the sponsor to order the department head to attend, proceed with requirements from other participants, meet the department head to understand their concerns and update the stakeholder engagement approach, or note the issue in the issue log and continue.

The real problem is low engagement from an influential stakeholder, which threatens requirements and adoption. Going to the sponsor escalates too early. Proceeding without them, or only logging the issue, ignores the risk. The best answer is a direct conversation and an adjusted engagement approach. More practice is in stakeholder engagement.

5. The skipped safety inspection

A construction project is behind schedule. The site supervisor suggests skipping a required safety inspection, noting it would recover several days. The sponsor is pushing hard for the original date. The question asks what the PM should do.

The options are: skip the inspection because the sponsor wants the date, skip it but document the decision, keep the inspection and look for other ways to recover schedule such as fast tracking or crashing where appropriate, or quietly reduce the inspection scope.

This is a compliance case. Any option that bypasses a required inspection breaks a rule and puts people at risk, so the "skip" and "reduce" options go. The best answer keeps the inspection, informs the sponsor honestly, and explores legitimate schedule compression. See compliance and governance.

Common Mistakes to Avoid

Answering from your own workplace. The exam asks what a PMI-aligned PM would do.
Choosing "analyze" every time. If the analysis is already done or the risk has already occurred, the best answer is to act.
Ignoring roles. The PM does not override the product owner, the sponsor, or a functional manager's formal authority.
Spending too long on one question. Apply the keyword check, choose, flag it, and move on. There is no penalty for wrong answers, so never leave a question blank.

Quick Review

Read the last sentence first so you know what is being asked.
Identify the approach (predictive, agile, hybrid), the people involved, and the project stage.
Separate the real problem from the symptoms and distractions.
Eliminate options that escalate too early, bypass the process, act without assessing, or blame.
Prefer answers that are proactive, collaborative, root-cause focused, and within the PM's authority.
Watch for keywords: first, next, best, most likely, should have done, except.
In agile scenarios, the PM is a servant leader, the team self-organizes, and the product owner owns backlog priority.
Ethics and compliance outrank schedule and cost.