Product
Novelty, complexity, safety, architecture, quality attributes, physical/software coupling.
Fit the approach to the work
Tailoring Models, Methods & Artifacts
Tailoring is the deliberate adaptation of the development approach, governance, processes, methods, and artifacts to a project’s context. The goal is “just enough” discipline to deliver value and manage risk—not maximum or minimum process.
ContextLifecycleMethodsArtifactsInspect & adapt
01 · The case for tailoring
Every project has a different shape
Project
Size, duration, budget, dependencies, uncertainty, delivery cadence, procurement.
Organization
Culture, governance, policies, process assets, distributed structure, maturity.
Environment
Regulation, market volatility, technology change, sustainability, geopolitical constraints.
People
Skills, team size, location, autonomy, stakeholder access, trust and experience.
Guardrail: organizational standards, law, contracts, security, safety, and audit needs constrain tailoring. Removing a control requires an evidence-based replacement or explicit authorization.
02 · Tailoring sequence
Choose, adapt, then improve
Select the initial development approach
Predictive, adaptive, or hybrid; determine delivery cadence.
Predictive, adaptive, or hybrid; determine delivery cadence.
Tailor for the organization
Align with governance, policy, methods, and required controls.
Align with governance, policy, methods, and required controls.
Tailor for the project
Adjust processes, roles, methods, ceremonies, tools, and artifacts.
Adjust processes, roles, methods, ceremonies, tools, and artifacts.
Implement ongoing improvement
Inspect outcomes and adapt when evidence or context changes.
Inspect outcomes and adapt when evidence or context changes.
Record consequential tailoring decisions, rationale, constraints, owner, and review point. This creates transparency and prevents “we have always done it this way” from becoming the process.
03 · Three building blocks
Model → method → artifact
Model · a way to think
A simplified representation that explains behavior or relationships: situational leadership, communication models, motivation models, conflict models, complexity frameworks, change models.
Method · a way to act
A means for accomplishing work: estimating, workshops, interviews, retrospectives, earned value analysis, root-cause analysis, prioritization, testing, planning poker.
Artifact · evidence or information
A template, document, deliverable, or visual: charter, backlog, roadmap, risk register, schedule, business case, requirements, burn chart, dashboard, lessons learned.
Memory hook: a model frames the situation, a method performs the work, and an artifact captures or communicates the result.
Example: uncertain product
Model: Cynefin/complexity. Methods: prototypes and experiments. Artifacts: hypotheses, experiment results, ordered backlog.
Example: regulated release
Model: stage-gate. Methods: traceability and formal reviews. Artifacts: approvals, test evidence, requirements matrix.
Example: distributed agile team
Model: adaptive lifecycle. Methods: asynchronous refinement and virtual reviews. Artifacts: shared backlog, decision log, definition of done.
04 · Design tests
Evaluate the tailored system
Value
Does this activity or artifact improve a decision, reduce risk, enable delivery, or satisfy a real obligation?
Sufficiency
Is the evidence detailed enough for its audience and consequence—without avoidable duplication?
Coherence
Do roles, cadence, governance, lifecycle, methods, and tools reinforce one another?
Feedback speed
How quickly does the approach expose incorrect assumptions, defects, and changing needs?
Adoption
Can the team actually use it? A theoretically perfect process that people bypass is not effective.
Compliance
Are mandatory policy, contractual, regulatory, safety, security, and audit needs demonstrably met?
Review at retrospectives, phase gates, releases, major risk events, team changes, and shifts in external conditions. Use outcomes—cycle time, defects, rework, value, risk exposure—not document count.
05 · Common traps
Tailoring is not permission to drift
Copy-paste process
A prior project is evidence, not a universal recipe. Reassess its assumptions.
Method buffet
Combining fashionable practices without understanding interfaces creates friction.
Zero documentation
“Agile” does not erase knowledge-transfer, compliance, architecture, or operating needs.
Permanent first choice
The initial approach is a hypothesis. Update it when results or context disagree.
06 · Retrieval practice
Check your reasoning
What is the difference between tailoring and a hybrid approach?
Tailoring adapts the whole project approach to context. Hybrid specifically combines predictive and adaptive elements; it is one possible tailoring outcome.
Classify a risk register: model, method, or artifact?
Artifact. It captures and communicates risk information.
When should tailoring decisions be revisited?
Continuously, especially at retrospectives, phase or release boundaries, major changes, and when performance evidence shows the approach is not working.
A team wants to remove a mandatory security review because it slows delivery. What should happen?
Confirm the constraint and seek an authorized, evidence-based alternative that preserves the control objective; do not silently remove it.