Do You Still Need to Memorize ITTOs and the 49 Processes in 2026?

Short version, so you can stop worrying: no, you do not need to memorize the ITTOs and the 49 processes by rote for the 2026 PMP® exam. Not the whole grid of inputs, tools, techniques, and outputs. Not all 49 process names in order. People keep asking because older courses drilled that matrix hard and the flashcard decks are still floating around. But the exam moved on. Spend three weeks memorizing that table and you're studying for a test that no longer exists.

Where all this came from

The 49 processes, the five process groups, the ten knowledge areas, and the giant table of inputs, tools, techniques, and outputs come from an older edition of the PMBOK® Guide, the 6th. It was a tidy structure, and it was very memorizable, so a whole test-prep culture grew up around drilling it. Then the guide itself changed. The current PMBOK Guide is the 8th edition, and newer editions moved away from that rigid process-and-ITTO framing toward principles and outcomes. The old grid didn't vanish from the earth. It just stopped being the thing the exam is built on.

Why memorizing it is the wrong bet now

The exam has been scenario-based for years. Since the last major overhaul in 2021, questions stopped asking "which of these is an input to Develop Schedule" and started dropping you into a situation: a vendor's late, a stakeholder's angry, a sprint's half-done and someone wants to change it. The 2026 update, live since July, leans even further that way, toward outcomes, value, and business impact. PMI writes questions to the Exam Content Outline, the ECO, not to any one book. The PMBOK Guide is a reference, useful background, and that's all.

Think about what an ITTO question would even look like on this exam. "Which is a tool of the Control Quality process?" You'll see almost none of that. What you'll see instead is a paragraph about a quality problem and four plausible actions, and you have to pick the best one. Knowing that inspection is technically a Control Quality tool does nothing for you there. Understanding when and why you'd inspect does everything.

What to learn instead

Three things, and each one is more useful than the grid.

First, learn the logic and flow. The processes connect for a reason. An output of one becomes an input to the next because the work genuinely depends on it. You don't memorize that the project charter feeds a dozen downstream processes. You understand that the charter authorizes the project, so nothing serious happens until it exists. You don't memorize that change requests are an input to integrated change control. You understand that every change, from anywhere, funnels through one controlled gate. Get the flow, and the "connections" stop being a list to recall and start being common sense.

Second, know the purpose of the major processes. Not the ITTOs, the point. What is risk management for? To handle uncertainty before it handles you. What's the scope baseline for? To set an agreed line so you can tell when someone's pushing past it. When you know what a process is trying to accomplish, you can reason your way to the right action even on a question you've never seen before.

Third, learn to spot which approach fits. A big share of the exam is predictive, and most of the rest is agile or hybrid, and the same situation calls for a different move depending on the setup. A mid-project change is a formal change request on a predictive project and a backlog item on an agile one. Reading which world you're in is half the battle, and no amount of ITTO memorization tells you that.

A quick example

Say a question describes a stakeholder who wants a change on an agile project, mid-sprint. The memorization approach has you flipping through mental flashcards for a matching ITTO and finding nothing useful. The flow approach is faster and correct: new requests go to the product backlog, the product owner prioritizes, the current sprint stays protected. You didn't recall a table. You understood how the work flows, and the answer fell right out of that.

That's the whole trick. The exam is built to reward people who get how a project actually moves, not people who can recite a lookup table under pressure. Once you stop trying to hold 49 processes and their attributes in your head, you free up real hours for the practice that moves your score.

What you do still need to know

"Don't memorize the ITTOs" is not "don't study." You still want a working grasp of the core formulas, earned value especially, because the numbers still show up, just lighter than they used to. You still need the vocabulary, so terms like baseline, backlog, and definition of done mean something instantly. And you absolutely need the PMI mindset: understand the situation before you act, look for the root cause, favor collaboration over command, and escalate only when something is truly beyond your authority. That mindset is worth more points than any table of inputs and outputs ever was.

So put your hours where they pay. Do practice questions, read the explanations, and follow the reasoning instead of hunting for a process name to match. You can work through free scenario-based questions with full explanations at pmprep.app. After a few hundred of them, the logic the exam is testing starts to feel obvious, which is exactly the place memorizing a grid could never get you to.

PMP, CAPM, PMI-ACP, and PMI are registered marks of the Project Management Institute, Inc. pmprep.app is an independent study resource and is not affiliated with or endorsed by PMI.