Did you know the 2026 PMP exam adds case studies? It's one of the bigger format changes most candidates haven't fully wrapped their heads around yet.
Starting July 9, 2026, the exam stops being 180 standalone questions. Some of those questions get grouped into case study scenarios: you read one detailed project situation and then answer several questions about it. The certification is the same, but the way you're tested shifts toward applied, real-world judgment.
If your exam date is on or after July 9, this is part of what you're walking into. Below is what case studies actually are, how they differ from the questions you've been practicing, how to approach them, and a full worked example you can try right now.
Skip to the example case study ↓
What is a case study on the PMP exam?
A case study, sometimes called a case set or scenario set, presents one detailed project situation and then asks a set of questions about it. The scenario describes the things that drive real decisions: the team composition, the delivery approach, the stakeholders involved, the budget and schedule constraints, and what has already gone wrong or right. Then you answer several related questions, all referencing that same situation.
PMI has not published a single fixed number of questions per case, but the format is commonly described as a set of about three to five linked questions per scenario. This is part of the broader July 2026 update, which you can read about in our complete guide to the 2026 PMP exam changes.
How case studies differ from standard questions
With standalone questions, you reset your thinking every time. Each item is its own little world, and once you answer it, you move on. Case studies break that rhythm. You have to hold one situation in your head and reason across several questions about it, which means a detail buried in the scenario can be the key to a question three items later.
They also take longer. The exam moved to 240 minutes partly to give candidates time to read and digest these richer scenarios. If you have trained entirely on quick standalone questions, the first thing you will notice is how much more reading there is before you even reach the answer choices.
What case studies actually test
The point of the case study format is integrated, applied judgment. PMI wants to see whether you can take a messy, realistic situation and apply consistent decision-making to it, not just recall a definition. That fits the direction of the whole 2026 exam, which leans harder into agile and hybrid delivery and into the business environment, where the focus is on value rather than output.
Because the questions share a scenario, consistency matters. If one question rewards assessing impact before acting, the next one usually does too. The candidates who struggle are the ones who answer each question on instinct instead of recognizing the PMI thinking pattern running through the whole set. If that mindset gap is new to you, our post on questions that trip up experienced PMs walks through it.
How to approach a case study
Read the entire scenario before you look at any question. Note the delivery approach first, since a hybrid project is handled differently than a fully predictive one, and a lot of the answer choices hinge on that. Pay attention to who the stakeholders are and what their relationship to you is, because stakeholder dynamics drive a surprising number of these questions.
Then answer each question on its own merits while keeping the scenario's context in mind. Watch for the same traps that show up everywhere on the exam: the answer that feels decisive and fast is often the one that skips a step PMI wants you to take first. When two answers both look reasonable, the one that assesses, collaborates, or follows the plan usually beats the one that acts unilaterally. For the agile and hybrid side specifically, our guide to predictive, agile, and hybrid on the 2026 exam is worth a read.
Try a full example case study
Here is a realistic case study in the 2026 format: one scenario followed by five linked questions. Read the scenario once, then work through all five. Try to answer each before opening the explanation, and notice how the same situation drives every question.
Scenario. Riverside Bank is building a customer-facing mobile banking app. You are the project manager on a hybrid effort: the development team works in two-week sprints, but launch is tied to a fixed regulatory deadline set by a banking regulator that will not move. An engaged product owner prioritizes the backlog. Midway through the project, a senior compliance officer who was not involved at kickoff joins and begins raising concerns about how customer data is handled. Over the last two sprints, the team's velocity has dropped noticeably, and the project sponsor has asked for a status update framed around business value, not just features shipped.
Question 1
The team's velocity has dropped over the last two sprints. As the project manager, what should you do FIRST?
A. Add an experienced developer to the team to recover velocity
B. Reduce the number of stories the team commits to in the next sprint
C. Facilitate a retrospective to help the team find the root cause
D. Report the velocity drop to the sponsor in your status update
Reveal Answer
Answer: C, facilitate a retrospective.
Adding people (A) often slows a team down further in the short term, and reducing commitment (B) treats the symptom without knowing the cause. Reporting it (D) is something you will do, but not first. As a servant leader, your first move is to help the team inspect what is happening and surface the root cause themselves, whether that is technical debt, unclear requirements, or an outside dependency.
PMI principle: servant leadership and root cause over quick fix.
Question 2
The compliance officer joined late and is now raising concerns about data handling. What is the BEST way to handle this stakeholder?
A. Tell the product owner to add the compliance requirements to the backlog
B. Revisit your stakeholder engagement plan, then meet with the compliance officer to understand the concerns
C. Escalate to the sponsor that a stakeholder is disrupting the project
D. Continue with the current plan since the requirements were already agreed
Reveal Answer
Answer: B, update engagement and meet with them.
Jumping to add requirements (A) solves a problem you have not understood yet. Escalating (C) is the reflex to treat a stakeholder as a nuisance rather than a source of real risk. Ignoring them (D) dismisses a legitimate voice on a regulated project. A new and influential stakeholder means you reassess engagement, then engage to understand what is actually at stake.
PMI principle: stakeholder engagement is continuous, and you assess before you act.
Question 3
After meeting with the compliance officer, you confirm a new data-handling requirement is genuinely needed. The team is in the middle of a sprint. What should you do?
A. Stop the current sprint and re-plan it to include the new requirement
B. Add the requirement to the current sprint so it is not delayed
C. Have the product owner add it to the product backlog to be prioritized
D. Implement it yourself so the team is not burdened
Reveal Answer
Answer: C, route it through the product owner and backlog.
Stopping the sprint (A) and injecting work mid-sprint (B) both break the team's sprint commitment, which is exactly what the framework protects against. Doing it yourself (D) undermines the team and your role. New work belongs in the backlog, where the product owner prioritizes it. If it is truly urgent, the product owner can negotiate the current sprint's scope with the team, but the move that starts that conversation is routing it through the product owner.
PMI principle: protect the team's sprint, and let the product owner own backlog priority.
Question 4
The sponsor asked for a status update framed around business value. Which is the BEST way to report progress?
A. Report the number of story points the team completed per sprint
B. Report the percentage of planned features delivered so far
C. Report progress toward the business outcomes and benefits the app is meant to deliver
D. Report the number of open defects and outstanding risks
Reveal Answer
Answer: C, report against business outcomes and benefits.
Story points (A) and features delivered (B) are output and velocity measures, useful internally but not what the sponsor asked for. Defects and risks (D) matter, but they still are not business value. The 2026 exam puts real weight on the business environment, where the question is always whether the project is delivering the value it was funded to deliver, not just how much work got done.
PMI principle: connect the work to business value and benefits realization.
Question 5
With the fixed regulatory deadline approaching, the team reports it may not finish all planned features in time. What should you do FIRST?
A. Add contractors to increase capacity before the deadline
B. Assess the impact and work with the product owner to re-prioritize so the compliance-critical features ship first
C. Ask the regulator to extend the deadline
D. Ask the team to work overtime until the deadline
Reveal Answer
Answer: B, assess and re-prioritize to protect the must-have scope.
Adding contractors this late (A) usually makes a project later, not faster. Asking the regulator to move a fixed deadline (C) is not a realistic first move, and overtime (D) burns out the team and is not sustainable. When the date is fixed, the lever you flex is scope. You assess the impact and work with the product owner to make sure the compliance-critical, must-have features are the ones that ship by the deadline.
PMI principle: when time is fixed, protect the constraint by prioritizing scope, and assess before you act.
The skill a case study is really testing
Look back at the five questions. The scenario never changed, and neither did the thinking that produced each right answer. You assessed before acting, you protected the team and its sprint, you routed new work through the product owner, you reported value instead of output, and when the deadline was fixed you flexed scope to protect it. That consistency is the whole point. A case study is not five harder questions, it is one situation that rewards you for applying the same PMI judgment all the way through. Once you can spot the pattern, the format stops being intimidating.
Frequently asked questions
Does the 2026 PMP exam have case studies?
Yes. Effective July 9, 2026, the exam adds case study scenarios. Instead of every question standing alone, some are grouped into a set that all reference one detailed project situation.
How many questions are in a PMP case study?
PMI has not published a single fixed number. Case studies are commonly described as a set of about three to five related questions tied to one scenario.
Are case studies harder than standard PMP questions?
Not inherently. They require more reading and more integrated thinking, since you apply consistent judgment across several questions about the same situation rather than resetting for each isolated item.
How do I practice PMP case studies?
Practice with scenario sets that mirror the format, one detailed scenario followed by several linked questions, and focus on the PMI decision patterns rather than memorizing facts. Working through full examples like the one above is the fastest way to get comfortable with the rhythm.
Free 2026 PMP Cheat Sheet
Every formula, all 12 principles, risk strategies, and exam tips, on 2 pages.
Download Free Cheat Sheet →Practice Real 2026-Format Case Studies
PM Mastery has 40 case studies built in the new 2026 format, plus 4,500+ practice questions aligned to the 2026 ECO, each with a full explanation of why every answer is right or wrong. The AI Coach breaks down the PMI thinking behind any question you miss.
Start Free, 100 Questions IncludedNo credit card required. 7-day money-back guarantee on paid plans.