Most PMP candidates prepare for questions that ask what to do inside a chosen approach: how to run a retrospective, how to process a change request, how to read a burndown chart. Fewer prepare for the question one level up — who decides the approach in the first place, on what evidence, and what to do when that decision turns out to be wrong. That decision is tailoring, and it has become harder to avoid on the exam.
The reason is a shift in emphasis. When PMI updated the PMP exam in July 2026, the three domains were reweighted: People moved from 42 to 33 percent, Process from 50 to 41 percent, and Business Environment from 8 to 26 percent. Velociteach's summary of the updated exam also reports that the balance of delivery approaches moved from an even split to roughly 40 percent predictive and 60 percent agile or hybrid. PMI's own announcement describes a stronger focus on agile and hybrid ways of working without publishing a percentage. Either way, the direction is the same: fewer questions assume a single method, and more of them put you in a mixed environment and ask you to fit the approach to the work.
Tailoring is a decision, not a preference
Tailoring means deliberately selecting and adjusting the processes, governance, and delivery cadence of a project so they suit that project. It is not the same as choosing the method you personally like, and it is not a one-time choice made at kickoff and then left alone.
On the exam, the distinction matters because the tempting wrong answers are usually the ones that apply a method as a rule. An answer that says "hold a sprint review" is wrong in a project with no iterations, however correct it would be elsewhere. An answer that says "submit a change request" is wrong when the scenario describes a backlog that the product owner reprioritizes every two weeks. The exam rewards reading the environment before reaching for a practice.
A useful habit when reviewing practice questions: before looking at the options, write down in one line what the delivery environment appears to be and what single constraint is driving it. If you cannot name the constraint, you have not finished reading the question.
The factors that drive the choice
Tailoring questions generally hinge on a small number of factors. The scenario will mention one or two of them, and those mentions are the clue.
| Factor | What the scenario sounds like | Pushes toward |
|---|---|---|
| Requirements stability | Scope defined and signed off; or requirements still being discovered | Predictive; or agile |
| Rate of change | Priorities shift monthly; or the design is frozen | Agile; or predictive |
| Regulatory and audit load | Inspections, certification, traceable approvals | Predictive governance |
| Delivery cadence the customer can absorb | Customer wants working output early; or one release at go-live | Agile; or predictive |
| Team experience and location | Co-located, experienced, empowered; or distributed and new to the method | Agile; or more structure |
| Product type | Physical build, long lead items; or software and content | Predictive; or agile |
| Organizational maturity | Existing agile practice; or heavy stage-gate culture | Match what exists, then adjust |
Notice that most rows can point either way. That is deliberate. The factor itself does not decide the answer — the direction the scenario pushes it does.
Hybrid is a design, not a compromise
The most common misreading of hybrid is that it means doing a bit of both and hoping for the best. In exam scenarios, hybrid almost always means something more specific: different parts of the work use different approaches because they have different constraints.
A typical pattern is a project with a hardware or infrastructure component that has long lead times and certification requirements, and a software or configuration component where the customer's needs are still settling. The first part gets a baseline, a sequence, and formal change control. The second part gets iterations and a prioritized backlog. The integration points between them get explicit attention, because that is where hybrid projects actually fail.
When a question describes this kind of split, the better answer usually does three things: it applies the right approach to the right component, it names the interface between them, and it does not force the whole project onto one cadence. Answers that standardize everything "for consistency" are generally the distractor.
Re-tailoring mid-project
A second category of tailoring question gives you a project already underway and a signal that the current approach is not working. Scope keeps reopening in a predictive project. An agile team is spending more time on compliance paperwork than on delivery. A two-week cadence is producing increments the customer cannot review that quickly.
The pattern for these is consistent: gather evidence, propose the adjustment through the governance that exists, and change one thing deliberately rather than restarting the project. Answers that abandon the approach wholesale, or that quietly change how the team works without telling anyone, are usually wrong for the same reason — both skip the agreement step.
It also helps to remember where tailoring decisions get recorded. A development approach and its rationale belong in the planning artifacts the project already maintains, not in an informal understanding among the team. If a question asks what to do first after deciding to adjust, updating the relevant plan and confirming it with stakeholders is often the better answer than immediately executing the change.
Where to study this
Two points about sources are worth knowing. First, the exam is built from the Exam Content Outline, not from any single book; the PMBOK Guide is one of a longer list of references PMI cites. Second, PMI has described AI and sustainability as elements that appear inside project scenarios rather than as standalone topics. Both points apply to tailoring: you are unlikely to see a question that asks you to define tailoring, and quite likely to see one where a sustainability requirement or an AI-assisted tool is simply part of the environment you have to tailor to.
For practice, the format of the updated exam is worth keeping in mind as you build stamina. Velociteach's summary describes 180 questions, of which 170 are scored, over 240 minutes, with two ten-minute breaks. Case-style and graphic-based questions were added in the update, and tailoring suits that format well — a case that establishes a mixed environment can support several questions about how to run it.
A short checklist
When a question looks like a tailoring question, work through it in this order.
- Name the delivery environment the scenario describes, in one word if possible.
- Identify the constraint driving it — regulation, uncertainty, lead time, customer capacity, team maturity.
- Decide whether the work is uniform or splits into components with different constraints.
- Choose the response that fits that structure, not the one that fits your preferred method.
- Check whether the response respects the agreement step: has the change been proposed to the people who need to accept it?
Candidates who practice this sequence tend to stop losing points on questions where two options are both reasonable practices and only one fits the project described. That is the specific skill tailoring questions test.