Someone on r/pmp this week bought PMI Study Hall twice. Once in June for the old exam, then again after PMI told them they needed the new version for the new format. PMI even refunded the first purchase. They opened the new one, and it was the exact same product. Same practice questions, same mini exams. "I never had a case study practice question," they wrote. So is the test even different?
They're not the only one asking. Since the new exam went live on July 9, the sub has filled up with people who bought or re-bought Study Hall for the new format and can't find the one thing the new exam leans on hardest: case studies.
Here's what actually changed, why case studies are the real shift, and what it takes to actually practice for them.
What actually changed
Before the rumors pull you around, here's the honest split between what's confirmed and what first-takers are reporting.
- 180 questions, 170 scored and 10 unscored pretest. Unchanged.
- 240 minutes, up from 230. This is the real change.
- Two breaks, ten minutes each. Unchanged.
- You can't return to a section once its break starts.
- The "185 questions" number going around is wrong.
- Case studies are front-loaded, the first thing on the exam.
- The first break hits after roughly the first 10 questions.
- Then nothing until around question 97.
- The long back-to-back stretch makes the 4-hour sit exhausting.
The left column is confirmed. The right column is what first-takers have been posting on r/pmp since July 9, not something PMI publishes. Treat it as useful field signal, not gospel.
So the headline is smaller than the panic suggests. The exam is ten minutes longer and the same length it has always been. What genuinely moved is the shape of it. Case studies now come first, and once a section's break starts, you can't go back to it. Whatever you did on those case studies is locked in before you answer a single standalone question.
What a case study actually is on this exam
If you tested on the old format, you answered questions one at a time. Read a scenario, pick an answer, move on. The next question was a fresh scenario with no connection to the last one.
Case studies don't work that way. First-takers describe a long scenario, five paragraphs or so, sitting on the left side of the screen, with a series of questions on the right that all draw from that same scenario. You read one situation, then answer several linked questions about it. The scenario doesn't reset between questions. The stakeholder you met in paragraph two is the same stakeholder the fourth question asks about.
That's a different skill than answering standalone questions, and it's the skill the front-load tests first, while you're freshest and the clock still feels roomy. Read the scenario wrong, or miss a detail buried in paragraph three, and you don't get one question wrong. You get a cluster wrong, all traceable to the same misread. Then the break starts and the section closes behind you.
Here's what that actually looks like
This is an original scenario written for this post, in the 2026 style. Read the whole thing first, then take the three questions that follow it.
You're the project manager on a hybrid initiative to replace a hospital's patient-scheduling system. The work is split into two streams. A Scrum team is building the new scheduling app in two-week sprints, and a separate group is handling the data migration and staff training on a phased plan with fixed go-live dates tied to each hospital wing.
Three sprints in, the Scrum team is delivering working features and the product owner is happy with the demos. But the migration group tells you they're two weeks behind, because the source data is far messier than the estimate assumed, and the first wing's go-live is now at risk.
At the same time, the hospital's Chief Nursing Officer, a key sponsor, emails you directly. She's heard the app looks great in demos and wants to accelerate the first wing's go-live by a week to show early results to the board. She has no idea about the migration delay.
You have a sprint review tomorrow and a steering committee meeting on Friday.
What should you do first?
- AReply to the Chief Nursing Officer and commit to the earlier go-live date, since the app is on track
- BEscalate the migration delay to the steering committee on Friday
- CMeet with the migration group to understand the delay and its impact on the go-live before responding to the sponsor
- DAdd the data-migration work to the Scrum team's backlog so it moves faster
Reveal answerHide answer
You can't respond to the sponsor or the committee responsibly until you understand the real impact. Escalating before you've done your own diligence (B) skips a step. Moving migration into the Scrum backlog (D) ignores that it's a different kind of work on a different team, and throwing messy source data into sprints won't clean it up.
The trap: A friendly, enthusiastic sponsor makes "just say yes" feel safe. Commit to a date you haven't verified (A) and you own it.
After meeting with the migration group, you confirm the two-week delay is real and can't be safely compressed without risking patient-data integrity. How should you respond to the sponsor's request to accelerate?
- ATell her the go-live can't move earlier and leave it there
- BExplain the migration constraint, the patient-data risk of rushing it, and offer what can be shown to the board on the original timeline
- CAccelerate the app's go-live for the wing but delay the data migration until after the board meeting
- DAsk the Scrum team to work overtime to make up the migration group's delay
Reveal answerHide answer
The sponsor needs the constraint explained and an option she can actually take to the board. C splits go-live from its own data migration, which for a patient-scheduling system means going live without safe data. D confuses the two work streams again and burns out the wrong team for a delay they didn't cause.
The trap: A flat "no" (A) feels honest, but it hands the sponsor nothing to take to the board. The job is the constraint plus an option.
The steering committee meets Friday. What's the most important thing to bring?
- AA recommendation to switch the entire project to a fully agile approach so it moves faster
- BA request to replace the migration group's lead
- CA clear picture of the delay, its impact on the go-live dates, the options with their trade-offs, and your recommendation
- DReassurance that everything is on track, since the app demos are going well
Reveal answerHide answer
Steering committees exist to make informed decisions, so your job is to give them a clear, honest picture and a recommendation. Not to reorganize the whole delivery approach over a single delay (A), or turn it into a blame exercise (B).
The trap: The demos are going well, so "everything's on track" (D) feels true. It hides the one risk the committee exists to weigh.
Notice what those three questions had in common. They all lived inside one situation. Treat the two work streams as one, or default to pleasing the sponsor, and you'd have walked into the same trap three times in a row. That's the case-study format. It rewards reading carefully once and reasoning consistently, and it punishes the reflex answers you can sometimes get away with on standalone questions.
Why a question bank alone doesn't cover this
This is why the Study Hall reports matter. A bank of standalone practice questions, however big, trains you to answer questions one at a time. It doesn't train you to hold a five-paragraph scenario in your head and answer four linked questions off it without contradicting yourself. Those are different muscles.
Multiple buyers are reporting that the new Study Hall, the one PMI pointed them to for the new format, doesn't include case study practice questions. We can't verify what's inside every version of their product, and some people have said they only got updated content after chatting with support, so your mileage may vary. But if you're prepping for an exam that opens with case studies, "lots of practice questions, no case studies" is exactly the gap you don't want to discover on test day, in the one section you can't go back to.
What to actually do
Practice the format, not just the content.
Before exam day, you want to have sat down with full multi-question case studies in the 2026 style and worked them end to end. Read the long scenario, answer the linked questions, then check not just whether you got them right but whether you read the situation right. When you miss one, trace it back. Did you misread a detail, or did you reach for a reflex answer? That's the exact feedback loop the front-loaded section is testing.
That's why we built PM Mastery around case studies, not just a question bank. There are 40 full case studies in the app with 200 linked questions, written in the 2026 format, so you practice the actual shape of the exam instead of just its topics. And the AI Coach is there for the moment you get a cluster wrong and want to understand why in plain language, not just see the right letter.
The exam is testing the job now
Here's the thing the new format makes obvious. The exam isn't really checking whether you memorized a process. It's checking whether you can read a messy situation, hold the details, and make the call a good project manager would make, several times, off the same set of facts. That's not a test-taking trick. That's the job.
The best way to pass the new exam is to practice thinking like a PM across a whole scenario. The case studies are just where that shows up first now.
Practice a Full 2026 Case Study Free
PM Mastery is built around case studies, not just a question bank: 40 full case studies with 200 linked questions in the 2026 format, plus 4,500+ practice questions and an AI Coach that walks through your reasoning when you miss one.
Try a Free Case Study, No CardNo credit card required. 7-day money-back guarantee on paid plans.