Frequently Asked Questions

Is tailoring the same as “cutting corners”?

No. It is the deliberate, justified adaptation of approach to fit context. Removing an element is valid only when it adds no economical value — and adding rigor (extra inspections for safety-critical work) is just as much tailoring as removing overhead.

Do I always have to tailor?

Yes, to some degree — because every project exists in a particular context. It can be an implicit act of accepting an established methodology rather than an explicit redesign.

Who owns the tailoring decisions?

Project stakeholders perform it; governance sets the bounds. Internal-only changes may be approved by the PM; external-impact changes may need PMO/VDO approval.

Can one project use more than one approach?

Yes — that is hybrid. A data centre might build predictively while developing computing capability iteratively; each sub-team may experience only one approach.

What limits how much I can tailor?

Organisational policy, safety-critical requirements, and contract terms can mandate a specific life cycle, approach or methodology.

When do I re-tailor mid-project?

Use diagnostics: retrospectives and lessons-learned are ideal; otherwise watch issues, threats, QA statistics and stakeholder feedback.

Model, method, artifact — what is the difference?

A model is a thinking strategy that explains something; a method is the means of achieving an outcome; an artifact is a template, document, output or deliverable. Tailoring selects and adapts all three to fit the project and its environment.