September 7, 2026 · 7 min read
TL;DR: Tailoring appears in 18 answer options across the bank and is keyed 10 times. The slice splits in two. Tailoring the delivery approach is keyed 6 times against 4, and it wins whenever an unadapted framework is failing or a project mixes definable work with uncertain work. Tailoring communication is keyed 4 times against 4, and it wins when the content or channel does not fit the audience. Both lose when tailoring is offered as a principle it is not, or as a personal accommodation where the problem belongs to the whole team.
PMBOK 8 gives tailoring its own section of the Guide, and the bank's explanations cite that fact repeatedly. That makes it worth knowing as doctrine, not just as a word that sounds sensible in an option.
When a framework has been applied without being fitted, or when different parts of one project need different treatment.
A PMO with no way of working of its own bought an extreme programming framework from a vendor at significant cost, and projects are still late, over budget and disappointing customers. Switching to predictive is offered, and so is switching to Scrum. Both lose to tailoring the approach to fit the organisation and the project's needs. The explanation names the two switches as the same mistake in different clothes: each replaces one unadapted framework with another.
A construction firm's office fit-out has shell, electrical and plumbing work fixed by code, and interior layout to be refined with the client through rounds of mockups. Keyed is a predictive approach for the fixed-specification deliverables and an iterative approach for the client-facing ones, tailoring the mix to each. Running the whole thing one way or the other ignores half the work. Asking the client to finalise every preference up front defeats the purpose of iterating with them at all.
A PMO mid-way through adopting a popular framework has already branded the templates and aligned them with governance. Keyed next step: enable a process for tailoring based on size and complexity, and implement ongoing improvement. The explanation walks the PMBOK 8 sequence: select an initial approach, tailor for the organisation, tailor for the project, improve continuously. The stem places the PMO at the end of step two, so what is left is steps three and four.
A sponsor asks which standard PMO model to adopt so the PMO is set up correctly from the start. Keyed, citing PMBOK 8 Appendix X2.4, is that no model is universally ideal and the characteristics of several should be blended and tailored to the organisation's context. The directive PMO, the supportive-then-controlling ladder, and the highest published maturity rating are each a way of treating a type as a rung to stand on.
And the definitional pair: a hybrid approach is a tailored blend of predictive, iterative, incremental and agile approaches; and asked when on a nine-month agile project the project manager should stop tailoring, the keyed answer is that tailoring should never be stopped. The three distractors each name a person who could decide it ends, and it makes no difference which, because none of them can decide there is nothing left to learn.
When it is offered as something it is not: an agile principle, a stewardship behaviour, or a private arrangement with individuals where the problem belongs to the whole team.
Offered as a principle it is not. Asked for a correct agile clarifying principle about delivery, tailoring the project approach to suit the project and the team is offered. It loses to delivering working software frequently with a preference for the shorter timescale. The explanation is careful: tailoring is sound advice and PMBOK 8 doctrine, but it is not one of the agile principles, and PMI's principles and the Manifesto's are often quoted side by side and blur together. Asked which behaviours a customer means by stewardship, tailoring is offered alongside care, respect and diligence and loses, because stewardship is about how responsibility is discharged, and tailoring is a separate matter with its own section.
Offered as a personal accommodation for a team problem. A hybrid hospital-records team needs to work as one unit across its agile and predictive halves. Regular one-on-ones to tailor communication and task management to each person loses to open communication and shared team norms, because one-on-ones optimise each relationship with the project manager, which is the opposite of building cohesion. Team members are reluctant to use new software they call overcomplicated, and the question asks what should have been done at the outset. One-on-one sessions to understand resistance and tailor support is the strongest distractor and loses to training that demonstrates the functional benefits, because the one-on-ones are a response to resistance that exists, and the question asks what would have prevented it.
Common trap: treating the customer's preference as a tailoring factor. Asked which project factors influence tailoring decisions, whichever life cycle the customer prefers is offered, and so is whichever is newest and most interesting to upper management. Both lose to whether the flow of work is interrupted by delays and whether the work is easily definable or highly uncertain. The explanation is the rule: tailoring starts from the nature of the work, and preferences are inputs to listen to that say nothing about the work itself. The bank pairs that with a second item naming the full set of factors that influence how a product life cycle is tailored, which is the demand pattern for value, the rate of process improvement the team needs, and the number of teams. Naming one of the three is true and incomplete.
| Scenario | Keyed | The distractor tailoring loses to, or beats |
|---|---|---|
| Engineers, scientists and project staff need different information at different depths | A communications plan tailored to each discipline's needs | Beats a centralised dashboard, which presents one view to audiences with different needs |
| Operations director says updates lack adoption metrics | Tailor the updates to include those metrics | Beats an interactive dashboard, which changes the channel and leaves the content missing |
| Team disagrees on frequency, methods and content | Tailor frequency and method to each stakeholder | Beats a fixed-schedule status update to everyone, which looks like transparency and produces the opposite |
| A single sponsor is replaced by a steering committee | Recognise the structure has changed and tailor communications | Beats one meeting with the committee, then carrying on as before |
The four keyed communication items share a shape with the approach items: the fit is the problem, and the fix is to change what is sent or how, to match the audience in front of you. The explanation for the disciplines case says it in one line: a single presentation of the data for audiences with different needs is the original problem in a new place.
Across both halves, the bank keys tailoring when something has been applied unadapted and is failing for that reason, and rejects it when it is dressed up as a principle, a behaviour or a private arrangement. Every one of the 18 options is explained rather than just marked wrong, and the explanations lean on the same PMBOK 8 section every time.
What does tailoring mean in PMBOK 8? Selecting and adapting the delivery approach, processes and practices to fit the deliverable, the team and the environment, rather than adopting a framework wholesale. PMBOK 8 gives it its own section, running as a sequence: select an initial approach, tailor for the organisation, tailor for the project, then improve continuously.
When should a project manager stop tailoring? Never. The bank keys that answer directly. Review points, phase gates and retrospectives all give the team occasions to inspect the way it works and adapt it, and no person can decide that there is nothing left to learn.
Is tailoring one of the agile principles? No. Tailoring the approach to the project and the team is sound advice and PMBOK 8 doctrine, but it is not one of the principles behind the Agile Manifesto. The bank offers it as a distractor in exactly that question.
Which side of the PMI talent triangle does tailoring a delivery approach strengthen? Ways of working. Selecting and tailoring life cycles, methods and tools is the delivery craft itself, which earlier editions called technical project management.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.
Related reading: Choosing a Delivery Approach: Predictive, Iterative, Incremental, Agile, Hybrid and The PMO: 6 Keyed, 23 Distractors, and It Never Does Your Job For You. Planning tasks are mapped on the Process domain study page.
Sources: PMI, A Guide to the Project Management Body of Knowledge (PMBOK Guide), Eighth Edition and PMI, 2026 PMP Examination Content Outline.
What does tailoring mean in PMBOK 8?
Selecting and adapting the delivery approach, processes and practices to fit the deliverable, the team and the environment, rather than adopting a framework wholesale. PMBOK 8 gives it its own section, running as a sequence: select an initial approach, tailor for the organisation, tailor for the project, then improve continuously.
When should a project manager stop tailoring?
Never. The bank keys that answer directly. Review points, phase gates and retrospectives all give the team occasions to inspect the way it works and adapt it, and no person can decide that there is nothing left to learn.
Is tailoring one of the agile principles?
No. Tailoring the approach to the project and the team is sound advice and PMBOK 8 doctrine, but it is not one of the principles behind the Agile Manifesto. The bank offers it as a distractor in exactly that question.