WIKI SLATEPrecision to Vision
← LibraryTailoring — Quick ReferenceProject Management · Managing Complexity in Projects← PrevNext →
Poster 10 · Tailoring
PMBOK® Guide — 7th Edition · §3.5–3.6

Quick Reference Tables

Scan-and-recall tables: tailoring questions per performance domain, the diagnostics situation-to-fix list, and predictive vs adaptive at a glance.

Table 1 — Tailoring considerations by performance domain (§3.5)
DomainRepresentative questions
StakeholdersCollaborative environment? Internal/external? What communication technology fits and is cost-effective? How diverse in language, culture, numbers and relationship networks?
Project TeamColocated or distributed across time zones? Full- or part-time; contractors available? Established culture, development tools, special-needs / training?
Dev Approach & Life CyclePredictive, iterative, incremental or hybrid? Which life cycle & phases? What audit / governance policies apply?
PlanningHow do environmental factors influence the work? What drives durations? What estimating / budgeting policies — and how to estimate in adaptive work? Unstable requirements? Sustainability?
Project WorkHow lean should processes be? How are communications, physical resources & procurements managed? How is learning retained?
DeliveryHow are scope & acceptance criteria defined? What is “done”? What delivery cadence — single, multiple, periodic, continuous?
UncertaintyRisk appetite & tolerance? How are threats / opportunities handled? Does size, novelty or strategic importance demand robust — or simplified — risk management?
MeasurementHow is value measured (financial & non-financial)? How is benefits-realisation data captured during & after? What status reporting is required?
Table 2 — Diagnostics: situation → tailoring (§3.6)
SituationSuggested response
Poor-quality deliverablesAdd feedback / verification loops & QA steps.
Team unsure how to proceedAdd guidance, training & verification.
Long waits for approvalsStreamline — fewer approvers with value thresholds.
Too much WIP / high scrapVisualise work (value-stream mapping, kanban).
Stakeholders disengaged / negativeCheck info-sharing & feedback; deepen engagement.
Low visibility of progressCollect, analyse, share & agree the right measures.
Recurring surprise issuesExplore root causes for process / activity gaps.
Table 3 — Predictive vs adaptive
DimensionPredictiveAdaptive
ScopeStable, defined earlyEvolving; ambiguity
PlanningDetailed up frontIterative; adjusts
Risk responseReserves absorb riskAdjust plans / reserves
FeedbackNear milestonesFrequent
Best fitLow-change workHigh novelty / change