Tailoring is a decision: given uncertainty, risk, regulation, team skill, and stakeholder need, which practices do we use, and which do we leave on the shelf? It is not a guilty compromise. It is the job.
Read the context before you pick a brand
Useful variables: how much you do not know, how expensive late change is, how regulated the evidence trail is, how stable the team is, how many vendors sit on the critical path, and how much the sponsor can tolerate a range instead of a date. Those variables point to practices. They do not point to a fandom.
High uncertainty and cheap change: small increments, frequent review, a backlog, a definition of done. High cost of change and stable requirements: more design up front, a baseline, formal change. High regulation: build the evidence into whichever clock you use. Low team skill in a method: do not pick the method that requires fluency you do not have without a coaching plan.
A sponsor who 'wants Agile' and a contract that is fixed-scope fixed-price is a tailoring problem, not a motivational one. Either change the contract, or tailor toward predictive control and use adaptive practices only where they do not breach the commitment. Pretending both are fully true is how you get a dispute and a retro.
Practices, not package deals
You can take a daily coordination huddle without taking a two-week sprint. You can take a change board without taking a 400-line Gantt. You can take a product backlog without retiring a milestone that Legal requires. Tailoring is assembling a system that fits. It is not 'a bit of everything so nobody is upset.'
Write the tailoring down: what we are doing, what we are not, why, and when we will revisit. A team that cannot explain its own method will drift back to the loudest person's habit. A sponsor who cannot hear the 'why' will impose theirs in week three.
Re-tailor when the context changes. A discovery that has found a stable design can shift toward more predictive planning for the build-out. A predictive plan that has hit a wall of unknown interfaces can shift a slice to spikes and increments. Tailoring is not a one-time ceremony at kickoff. It is Process-domain maintenance.
What you must not tailor away
Ethics, safety, and required compliance evidence are not optional practices. You can change how you produce the evidence. You cannot change whether it exists because 'we are being lightweight.' Lightweight that skips the regulator is just late heavyweight with legal fees.
You also should not tailor away a way to see status, a way to change the plan, a way to own risks, and a way to close. Those Process tasks can be thin. They cannot be absent. A sticky note on a wall is a tool. The absence of any tool is a hope.
When a scenario asks you to choose a method, the best next action is often to assess the variables with the team and sponsor, then propose a tailored approach — not to impose the method you passed a quiz on. We will work that judgement in short scenarios next. No score. No pass promise. Just the habit of matching method to context.
Summary & next steps
Tailor from context variables, assemble practices on purpose, write the choice down, and re-tailor when the world changes. Do not tailor away ethics, safety, or the minimum control loops.
Next: a final mock review — a handful of short scenarios with a recommended next action and a rationale. It is practice, not a replica exam.