PMP Situational Questions: 50 Solved Agile + Hybrid Scenarios

The biggest single shift in the modern PMP exam is the move from process-knowledge questions to situational ones. Old PMP questions asked, "What is the input to the Develop Project Charter process?" Modern PMP questions describe a messy real-world scenario and ask, "What should the project manager do FIRST?" The answer almost never appears in PMBOK as a direct quote. It comes from internalising what PMI calls the PM Mindset.

I have walked candidates through hundreds of situational practice questions, and I have noticed something consistent: candidates who score 60% on situational questions are not lacking knowledge. They are lacking pattern recognition. They cannot tell, in ten seconds, whether the question is about servant leadership, conflict resolution, change control, or risk response. Once you have seen forty or fifty well-rationalised scenarios, the patterns become obvious.

This article is fifty worked scenarios with full rationales. Twenty are agile, fifteen are hybrid, fifteen are predictive. Each one includes the situation, four answer options, the correct answer, why the other three are wrong, and the underlying principle. I have built this from the situational patterns I see most often on the real exam. If you work through this article carefully, you will recognise these patterns when they appear on test day.

Before any scenarios, the mindset PMI is testing:

• You are a servant leader, not a command-and-control manager.
• You empower the team. You do not solve their problems for them.
• You facilitate, coach, and remove impediments.
• You talk to people before you escalate.
• You prevent problems through planning, not after them through firefighting.
• You tailor your approach to the project, not the other way around.
• You deliver business value, not just deliverables.
• You communicate proactively, not reactively.
• You value face-to-face or video over email.
• You manage risks before they become issues.

Internalise this, and 80% of the situational questions answer themselves.

Most situational PMP questions fit one of five patterns:

1. The Conflict: Two team members or stakeholders disagree. What should the PM do?
2. The Escalation Bait: A problem is presented, and one of the options is "escalate to the sponsor." Almost always wrong unless the issue is genuinely outside PM authority.
3. The Process Skip: A team has skipped a process (no risk register, no change control). The right answer almost always involves restoring the missing process.
4. The Approach Choice: A project is described with characteristics that fit predictive, adaptive, or hybrid. PMI is testing whether you recognise the cues.
5. The "Talk to the Team": An ambiguity or impediment is presented. The correct answer almost always involves the PM going to the team first.

Knowing these patterns lets you scan the question stem and predict the right answer family before reading the options.

Scenario 1: During a sprint, a developer realises that a user story will not fit in the current sprint. What should the Scrum Master do?

A. Add another developer to the story
B. Extend the sprint by two days
C. Bring the issue to the team during the daily stand-up for discussion
D. Re-estimate and move the story to the next sprint

Correct: C. Bring it to the team. The Scrum Master facilitates; the team decides.
Why others are wrong: A is the Scrum Master making a resourcing decision unilaterally. B violates the time-box. D may be the eventual outcome, but the team owns the decision.
Principle: The Scrum Master facilitates team self-organisation.

Scenario 2: A product owner keeps adding stories mid-sprint. The team is frustrated. What should the Scrum Master do?

A. Push back and refuse the new stories
B. Coach the product owner on the impact of mid-sprint changes
C. Escalate to the sponsor
D. Add the stories and lengthen the sprint

Correct: B. Coach the product owner.
Why others are wrong: A is confrontational and skips the coaching step. C escalates before coaching. D violates the sprint commitment.
Principle: Servant leadership through coaching, not enforcement.

Scenario 3: The team's velocity has dropped 30% over three sprints. What should the Scrum Master do?

A. Recommend hiring additional developers
B. Use the retrospective to explore the root cause with the team
C. Increase the sprint length to give more time
D. Reassign work to faster team members

Correct: B. Use the retrospective.
Why others are wrong: A is premature. C masks the problem. D damages team morale.
Principle: Inspect and adapt, with the team in the lead.

Scenario 4: A stakeholder demands the team show working software weekly instead of the current biweekly cadence. What should the team do?

A. Refuse to change the cadence
B. Discuss with the product owner and Scrum Master to evaluate the request
C. Comply immediately
D. Escalate to the sponsor

Correct: B. Discuss as a team.
Why others are wrong: A is dismissive. C may break sustainable pace. D escalates without discussion.
Principle: Decisions about working agreements are made collaboratively.

Scenario 5: A developer says they cannot work with a particular tester. What should the Scrum Master do?

A. Separate them onto different stories permanently
B. Coach both individuals on conflict resolution
C. Replace one of them
D. Ignore it; the team will work it out

Correct: B. Coach both.
Why others are wrong: A avoids the underlying issue. C is escalation. D abandons the team.
Principle: Address interpersonal conflict directly through coaching.

Scenario 6: The product owner is rarely available for the team. Stories are being misinterpreted. What should the Scrum Master do?

A. Have the team make their own interpretation
B. Replace the product owner
C. Engage with the product owner to clarify the availability expectation
D. Escalate to the sponsor

Correct: C. Engage with the product owner first.
Why others are wrong: A perpetuates the problem. B is a unilateral decision. D escalates without conversation.
Principle: Remove impediments by addressing root cause directly.

Scenario 7: The team has finished all sprint stories two days early. What should they do?

A. Pull from the backlog with product owner approval
B. Start working on stories outside the sprint
C. Take time off
D. Spend the time on technical debt without consulting

Correct: A. Pull from the backlog with PO approval.
Why others are wrong: B violates sprint scope. C is unprofessional. D bypasses the PO.
Principle: Sprint scope changes need product owner input.

Scenario 8: A senior executive wants daily progress reports. What should the Scrum Master do?

A. Provide daily reports as requested
B. Refuse, citing scrum principles
C. Explore the underlying need and propose a transparent alternative (e.g., access to the board)
D. Have the team prepare the reports

Correct: C. Explore the need.
Why others are wrong: A burdens the team. B is dismissive. D shifts overhead onto the team.
Principle: Transparency through information radiators serves stakeholders without burdening the team.

Scenario 9: The team's daily stand-ups have become status reports to the Scrum Master. What should the Scrum Master do?

A. Continue receiving the reports
B. Stop attending stand-ups
C. Coach the team on the purpose of stand-ups as team-to-team communication
D. Replace stand-ups with a written update

Correct: C. Coach the team.
Why others are wrong: A allows dysfunction to continue. B abandons the team. D removes a valuable ceremony.
Principle: Stand-ups are for the team, not for the Scrum Master.

Scenario 10: A user story is too large to fit in one sprint. What should the team do?

A. Split the story into smaller stories that each deliver value
B. Stretch the sprint
C. Accept the story will span multiple sprints
D. Move the story to the icebox

Correct: A. Split into smaller stories.
Why others are wrong: B violates the time-box. C undermines the sprint goal. D defers without rationale.
Principle: Stories should be sized to fit a sprint and deliver demonstrable value.

Scenario 11: A new team member joins mid-sprint and slows the team down. What should the Scrum Master do?

A. Remove the new member from the sprint
B. Pair the new member with an experienced one
C. Add another developer
D. Replan the sprint

Correct: B. Pair them.
Why others are wrong: A is exclusionary. C is unnecessary. D is overreaction.
Principle: Knowledge transfer happens through pairing, not isolation.

Scenario 12: The product backlog has 800 items, many old and unclear. What should the product owner do?

A. Delete the old items
B. Refine the backlog with the team to focus on near-term items
C. Continue prioritising as-is
D. Hand the backlog to the Scrum Master

Correct: B. Refine with the team.
Why others are wrong: A loses information. C does not address the problem. D shifts ownership.
Principle: Backlog refinement is a continuous, collaborative activity.

Scenario 13: A stakeholder wants to attend the team's retrospective. What should the Scrum Master do?

A. Allow the stakeholder
B. Discuss with the team and decide together
C. Decline immediately, citing retrospective being a team-only ceremony
D. Escalate to the sponsor

Correct: B. Discuss with the team.
Why others are wrong: A overrides team preference. C is dismissive. D escalates without need.
Principle: The team owns the retrospective; the Scrum Master facilitates the decision.

Scenario 14: The team consistently fails to meet sprint commitments. What should the Scrum Master do?

A. Increase the sprint length
B. Use retrospective data to understand the pattern with the team
C. Reduce the commitment going forward
D. Replace team members

Correct: B. Use retrospectives.
Why others are wrong: A masks the issue. C is a symptom-fix. D is destructive.
Principle: Inspect, adapt, address root causes.

Scenario 15: A new agile team is forming. What should the Scrum Master do first?

A. Conduct a kick-off and establish working agreements
B. Start the first sprint immediately
C. Train them on Scrum theory
D. Define their backlog

Correct: A. Kick-off and working agreements.
Why others are wrong: B skips foundation. C is partial. D is the product owner's role.
Principle: Forming-stage teams need explicit agreements before sprinting.

Scenario 16: The team's definition of done is unclear, leading to quality issues. What should the Scrum Master do?

A. Define it for the team
B. Facilitate a session for the team to agree on it
C. Use the previous team's definition
D. Defer to the product owner

Correct: B. Facilitate the team.
Why others are wrong: A removes ownership. C is template thinking. D is wrong owner.
Principle: The team owns the definition of done.

Scenario 17: Stakeholders demand a fixed-date delivery commitment. What should the product owner do?

A. Provide a fixed date
B. Refuse to commit
C. Engage stakeholders in a discussion of scope/date trade-offs
D. Escalate to the sponsor

Correct: C. Engage in trade-off discussion.
Why others are wrong: A may overcommit. B is unhelpful. D is premature.
Principle: Adaptive delivery manages variables through trade-off conversations.

Scenario 18: A developer is consistently underperforming. What should the Scrum Master do?

A. Performance-manage the developer
B. Coach the developer and surface the issue in retrospective if pattern continues
C. Escalate to the developer's manager
D. Move the developer to other work

Correct: B. Coach first, then escalate if persistent.
Why others are wrong: A is not the Scrum Master's authority. C is premature escalation. D is conflict avoidance.
Principle: Coach individuals; teams hold each other accountable.

Scenario 19: The team wants to skip the sprint review because no stakeholders are available. What should the Scrum Master do?

A. Cancel the review
B. Facilitate a review with the product owner and document outcomes for stakeholders
C. Postpone the review
D. Replace it with a written summary

Correct: B. Facilitate with PO, document for stakeholders.
Why others are wrong: A loses the inspection ceremony. C disrupts cadence. D misses the interactive value.
Principle: Cadence ceremonies preserve rhythm and learning.

Scenario 20: The team's burn-down chart has been flat for two days mid-sprint. What should the Scrum Master do?

A. Replan the sprint
B. Use the daily stand-up to surface impediments with the team
C. Escalate to the sponsor
D. Reduce the sprint goal

Correct: B. Surface impediments with the team.
Why others are wrong: A skips diagnosis. C escalates without understanding. D is symptom treatment.
Principle: The Scrum Master removes impediments through team conversation.

Scenario 21: A construction project has firm regulatory requirements but flexible interior design choices. What approach should the PM use?

A. Fully predictive
B. Fully adaptive
C. Hybrid with predictive for regulatory work and adaptive for design
D. Defer the choice to the sponsor

Correct: C. Hybrid.
Why others are wrong: A loses flexibility on design. B violates regulatory predictability. D abdicates PM responsibility.
Principle: Tailor the approach to the nature of the work.

Scenario 22: Halfway through a predictive project, the requirements start changing weekly. What should the PM do?

A. Lock the requirements
B. Switch fully to adaptive
C. Introduce iterative cycles for the changing components while maintaining predictive control for stable ones
D. Pause the project

Correct: C. Introduce iterative cycles selectively.
Why others are wrong: A ignores reality. B may abandon working controls. D loses value.
Principle: Adaptive tailoring can be introduced mid-project for affected components.

Scenario 23: A hybrid project has both a Gantt chart and a sprint backlog. Stakeholders are confused. What should the PM do?

A. Eliminate one
B. Facilitate stakeholder education on how each artefact serves the work it covers
C. Defer to the sponsor
D. Reduce reporting

Correct: B. Facilitate stakeholder education.
Why others are wrong: A removes value. C escalates without need. D hides information.
Principle: Transparency requires explaining tailoring choices to stakeholders.

Scenario 24: The team has a fixed budget but flexible scope. What approach makes sense?

A. Predictive with strict scope control
B. Adaptive with iterations prioritising highest-value scope first
C. Hybrid
D. Pause until scope is fixed

Correct: B. Adaptive prioritising highest value.
Why others are wrong: A forces stable scope that does not exist. C may add unnecessary overhead. D loses opportunity.
Principle: Match approach to constraint pattern.

Scenario 25: A hybrid project has a delivery schedule with hard milestones and iterative development between them. How should the PM communicate?

A. Use only predictive reports
B. Use only agile dashboards
C. Combine milestone-level reports for stakeholders with iteration-level dashboards for the team
D. Pick one and stick to it

Correct: C. Combine, tailored to audience.
Why others are wrong: A hides team-level data. B confuses stakeholders. D loses fit.
Principle: Tailor communication to audience needs.

Scenario 26: A team is using Scrum for development and Waterfall for infrastructure. Coordination is suffering. What should the PM do?

A. Force everyone into one framework
B. Facilitate cross-team alignment ceremonies (e.g., scrum of scrums or integrated standups)
C. Escalate
D. Add layers of management

Correct: B. Facilitate alignment.
Why others are wrong: A loses fitness. C is premature. D adds overhead.
Principle: Hybrid coordination needs lightweight integration ceremonies.

Scenario 27: A predictive plan has been baselined, but the team wants to use sprint retrospectives. What should the PM do?

A. Refuse retrospectives
B. Allow retrospectives as a learning tool while maintaining the predictive baseline
C. Abandon the predictive plan
D. Hold retrospectives only when issues arise

Correct: B. Allow retrospectives.
Why others are wrong: A rejects useful learning. C overreacts. D loses cadence.
Principle: Learning ceremonies enhance any approach.

Scenario 28: In a hybrid project, the sponsor wants traditional earned value reporting. The team wants velocity. What should the PM do?

A. Use both, mapped where possible (e.g., EV at milestone level, velocity at iteration level)
B. Refuse EV
C. Refuse velocity
D. Pick the sponsor's preference and override the team

Correct: A. Use both, mapped appropriately.
Why others are wrong: B and C refuse useful tools. D damages team buy-in.
Principle: Tailoring preserves the strengths of both approaches.

Scenario 29: A hybrid project has a fixed go-live date but evolving feature scope. How should the PM manage stakeholder expectations?

A. Commit only to the date, not the scope
B. Refuse to commit
C. Communicate the date as fixed and use minimum viable product (MVP) thinking with stakeholders
D. Push for a flexible date

Correct: C. Communicate date as fixed, MVP scope.
Why others are wrong: A is vague. B is unhelpful. D fights reality.
Principle: Manage scope around fixed constraints transparently.

Scenario 30: The team is delivering working software every two weeks, but the change control board meets monthly. Changes are bottlenecked. What should the PM do?

A. Bypass the CCB
B. Propose to the CCB a tiered process - lightweight approval for small changes, full review for major changes
C. Slow the team to monthly delivery
D. Escalate

Correct: B. Tiered CCB process.
Why others are wrong: A breaks governance. C kills agility. D escalates before proposing.
Principle: Tailor governance to delivery cadence.

Scenario 31: A hybrid project starts predictive but the customer requests more frequent demos. What should the PM do?

A. Refuse
B. Introduce regular demo cadence even within the predictive structure
C. Switch fully to adaptive
D. Hold demos only at milestones

Correct: B. Introduce demo cadence.
Why others are wrong: A is unhelpful. C is overreaction. D is the current state.
Principle: Demos can be added to any approach without changing the underlying structure.

Scenario 32: A hybrid team has a release train every three months with continuous internal iterations. The team feels constrained. What should the PM do?

A. Eliminate the release train
B. Use the retrospective to surface specific frictions and adjust within the cadence constraint
C. Switch teams
D. Skip a release

Correct: B. Surface frictions and adjust.
Why others are wrong: A overreacts. C is destructive. D damages predictability.
Principle: Identify specific frictions before changing structure.

Scenario 33: A stakeholder wants a detailed end-to-end schedule for a hybrid project. What should the PM provide?

A. A full predictive schedule
B. A roadmap with milestones, supplemented by current sprint plans, with transparency on uncertainty in the longer horizon
C. Refuse
D. Provide only the current sprint plan

Correct: B. Roadmap plus sprint plans, with uncertainty acknowledged.
Why others are wrong: A is dishonest about uncertainty. C is unhelpful. D withholds context.
Principle: Communicate at appropriate horizon and resolution.

Scenario 34: The hybrid team finishes its iteration early. Predictive milestones are still weeks away. What should the team do?

A. Take time off
B. Pull more backlog with the product owner's input
C. Work on documentation only
D. Start the next milestone work without coordination

Correct: B. Pull backlog with PO.
Why others are wrong: A is unprofessional. C is partial. D bypasses coordination.
Principle: Always coordinate scope with the PO.

Scenario 35: A hybrid project has both a risk register and a story-level risk attribute. They are out of sync. What should the PM do?

A. Eliminate one
B. Establish a clear relationship between the two (e.g., story risks roll up to register)
C. Maintain both separately
D. Use only the register

Correct: B. Establish a clear relationship.
Why others are wrong: A loses fidelity. C creates drift. D loses team-level visibility.
Principle: Tailor risk artefacts to the work but keep them connected.

Scenario 36: A stakeholder requests a scope change three weeks into a predictive project. What should the PM do FIRST?

A. Implement the change
B. Refuse the change
C. Document the change request and route through the change control process
D. Escalate to the sponsor

Correct: C. Document and route through change control.
Why others are wrong: A bypasses governance. B is dismissive. D is premature.
Principle: All changes go through change control.

Scenario 37: A team member identifies a risk during execution. What should the PM do?

A. Add the risk to the risk register and follow risk response planning
B. Tell the team member to handle it
C. Escalate to the sponsor
D. Wait until the next risk review

Correct: A. Add to register and respond.
Why others are wrong: B abandons the risk. C escalates without analysis. D delays response.
Principle: Risk management is continuous, not periodic.

Scenario 38: The critical path is at risk due to a supplier delay. What should the PM do FIRST?

A. Crash the schedule
B. Fast-track activities
C. Engage the supplier to understand the delay and explore options
D. Notify the sponsor

Correct: C. Engage the supplier.
Why others are wrong: A and B are tactics before diagnosis. D escalates without understanding.
Principle: Understand the problem before applying a response.

Scenario 39: The actual cost is 20% over the planned value at month three of a twelve-month project. What should the PM do?

A. Increase the budget
B. Calculate CPI and forecast EAC, then present options to the sponsor
C. Stop the project
D. Replace the team

Correct: B. Calculate and present options.
Why others are wrong: A is premature. C is overreaction. D is unfair.
Principle: Analyse with data, then communicate options.

Scenario 40: A predictive project's scope is creeping through informal stakeholder requests. What should the PM do?

A. Accept the changes
B. Reinforce the change control process with stakeholders
C. Escalate every request to the sponsor
D. Ignore informal requests

Correct: B. Reinforce change control.
Why others are wrong: A enables scope creep. C floods the sponsor. D damages relationships.
Principle: Process enforcement prevents scope creep.

Scenario 41: A team member is consistently late to status meetings. What should the PM do?

A. Have a private conversation with the team member to understand the cause
B. Skip them in the meeting
C. Replace them
D. Escalate to their functional manager

Correct: A. Private conversation first.
Why others are wrong: B is conflict avoidance. C is overreaction. D escalates without conversation.
Principle: Address performance issues directly first.

Scenario 42: The quality plan specifies inspection at three points. The team wants to skip the middle one because of schedule pressure. What should the PM do?

A. Allow the skip
B. Explain the cost of quality - prevention is cheaper than rework - and maintain the inspection
C. Move the inspection
D. Escalate

Correct: B. Maintain inspection.
Why others are wrong: A risks quality. C delays without basis. D escalates without conversation.
Principle: Quality is built in, not inspected out, but planned inspections are essential.

Scenario 43: A vendor under a fixed-price contract has delivered late and is requesting more money. What should the PM do?

A. Pay
B. Refuse and review the contract terms with procurement
C. Cancel the contract
D. Escalate to legal

Correct: B. Review contract terms.
Why others are wrong: A undermines the contract. C is premature. D escalates without internal review.
Principle: Contract terms govern; understand before responding.

Scenario 44: A risk in the risk register has materialised into an issue. What should the PM do?

A. Move it to the issue log and execute the contingency plan
B. Re-analyse the risk
C. Add a new risk
D. Inform the team

Correct: A. Move to issue log, execute contingency.
Why others are wrong: B is redundant. C is incorrect categorisation. D is partial.
Principle: Risks become issues; contingencies become actions.

Scenario 45: A predictive project has been baselined. Three weeks in, the technology choice is found to be infeasible. What should the PM do?

A. Push through with the existing technology
B. Initiate a formal change request to revise scope and approach
C. Cancel the project
D. Switch technology without approval

Correct: B. Formal change request.
Why others are wrong: A wastes resources. C overreacts. D bypasses governance.
Principle: Material changes require formal change control.

Scenario 46: A team member raises an ethical concern about the project. What should the PM do?

A. Investigate the concern and follow the organisation's reporting policy
B. Ignore it
C. Escalate immediately to legal
D. Have the team vote

Correct: A. Investigate and follow policy.
Why others are wrong: B is dereliction. C may be premature. D is inappropriate.
Principle: Ethics issues follow defined organisational processes.

Scenario 47: A milestone payment from the customer is overdue. The team is asking about the impact. What should the PM do?

A. Pause work
B. Escalate to finance and inform the team factually about the situation
C. Hide the issue
D. Pay vendors from the contingency

Correct: B. Escalate appropriately, inform team.
Why others are wrong: A is premature. C destroys trust. D misuses contingency.
Principle: Transparent communication and proper escalation channels.

Scenario 48: The project sponsor leaves the company. What should the PM do?

A. Continue as before
B. Pause the project
C. Engage with leadership to identify a new sponsor and reconfirm the business case
D. Cancel

Correct: C. Engage leadership, reconfirm sponsorship.
Why others are wrong: A risks misalignment. B is overreaction. D is destructive.
Principle: Sponsorship is essential; reaffirm at transitions.

Scenario 49: A predictive project has reached closing. The customer has accepted the deliverable. What should the PM do?

A. Move to the next project
B. Conduct lessons learned, archive documents, release the team, and obtain formal acceptance documentation
C. Disband the team
D. Submit final invoice and disengage

Correct: B. Full closing activities.
Why others are wrong: A skips closing. C is partial. D is partial.
Principle: Project closure is a defined process with multiple components.

Scenario 50: A stakeholder asks "when will the project be done?" mid-project. What should the PM do?

A. Provide the baselined end date
B. Provide the current forecast EAC date based on CPI/SPI, with the baseline as context
C. Refuse to commit
D. Defer to the sponsor

Correct: B. Provide forecast with baseline context.
Why others are wrong: A may be inaccurate. C is unhelpful. D abdicates PM role.
Principle: Communicate with current forecast data, transparent about variance from baseline.

When two answers look right, apply these heuristics in order:

1. Did the PM go to the team first? Pick that one.
2. Did the PM coach instead of direct? Pick that one.
3. Did the PM remove an impediment instead of report on it? Pick that one.
4. Did the PM use a process (change control, risk register, lessons learned) instead of working around it? Pick that one.
5. Did the PM avoid escalation when escalation was not strictly necessary? Pick that one.

These five heuristics resolve about 80% of the close-call situational questions.

Servant leadership answers usually contain verbs like:

• Facilitate
• Coach
• Empower
• Remove impediment
• Listen
• Engage
• Discuss with the team
• Explore

If you see one of these in an answer choice, it is often (not always) the right answer. Compare against the more directive options.

Hybrid questions often hinge on whether you can identify which parts of a project should be predictive and which adaptive.

• Predictive cues: Regulatory requirements, fixed-price contract, well-understood scope, stable technology, mature processes.
• Adaptive cues: Evolving requirements, customer collaboration, new technology, innovation focus, learning-driven work.
• Hybrid cues: A mix of the above across different workstreams.

When in doubt, propose a hybrid approach with explicit tailoring. The exam favours this answer when characteristics are mixed.

My exam-day pattern for situational questions:

1. Read the last sentence first. That is the actual question.
2. Read the stem to identify the setup (conflict, escalation bait, process skip, approach choice, or talk-to-team).
3. Predict the answer family before reading options.
4. Scan options for servant leadership verbs.
5. Eliminate two options that obviously violate PM mindset.
6. Choose between the remaining two using the "when in doubt" heuristics.

This pattern processes a typical situational question in 60-90 seconds.