WIKI SLATEPrecision to Vision
← LibraryTailoring — Frameworks & ModelsProject Management · Managing Complexity in Projects← PrevNext →
Poster 05 · Tailoring
PMBOK® Guide — 7th Edition · §3.3–3.4

Frameworks & Models

The reusable structures behind tailoring: what you can tailor, the five actions on processes, who you engage, the project attributes you weigh, and the development-approach spectrum.

Framework A · What to tailor — 5 aspects

1

Life Cycle & Approach

Life cycle, phases, and predictive / iterative / incremental / adaptive / hybrid mix.

2

Processes

Add, modify, remove, blend or align process elements.

3

Engagement

Who is involved, how empowered, how integrated as one team.

4

Tools

Software & equipment suited to the work — tempered by cost.

5

Methods & Artifacts

Means of working plus documents, templates & outputs.

Framework B · Five process-tailoring actions

Add
Bring rigor or cover unique conditions.
e.g. Independent inspections for safety-critical work.
Modify
Adjust to better suit the project/team.
e.g. Reformat documents for accessibility.
Remove
Drop what is not economical for its value.
e.g. No minutes for a small colocated team.
Blend
Combine elements for added value.
e.g. Appreciative inquiry in lessons-learned.
Align
Harmonise for consistent use.
e.g. Reconcile risk standards across disciplines.

Framework C · Engagement (P·E·I)

  • People — match skills/experience to the work; staff hard projects with experienced members.
  • Empowerment — how much local decision-making to defer to the team.
  • Integration — forge one team from staff, contractors & partners.

Framework D · Tailor for the project (P·T·C)

  • Product/Deliverable — criticality, type, market, technology, time frame, requirements stability, security, incremental delivery.
  • Project Team — size, geography, distribution, experience, access to customer.
  • Culture — buy-in, trust, empowerment, value alignment.

Model E · The development-approach spectrum

Predictive · stable

Scope known up front. Plan in detail; reserves absorb risk. Best for well-understood, low-change work.

Hybrid · mixed

A blend across workstreams — e.g. predictive build plus iterative discovery on one endeavour.

Adaptive · evolving

Requirements evolve. Plan iteratively; adjust plans & use reserves as understanding grows.