Agile didn’t just change how software gets built. It changed who carries the risk.
And most clients were never told.
Here’s what Agile quietly hands to the client:
1. Ownership of priorities.
In Scrum, the Product Owner decides what matters and in what order. If the priorities are wrong, the outcome is wrong. But the client is often told this role is “light” — a few meetings, a backlog to review. In practice, it’s the most consequential decision in the project.
2. Ownership of scope.
Agile treats scope as variable. If the date slips, the answer is often “we delivered what was prioritised.” The developer followed the process. The client absorbed the uncertainty.
3. Ownership of acceptance.
“Done” is defined by the client’s criteria. If the client can’t articulate what “done” means — or can’t verify it — the risk lands on them. The developer can always say: we built what you accepted.
4. Ownership of change.
Agile welcomes changing requirements. That’s a genuine strength. But when requirements change, the cost of rework is rarely the developer’s to bear. It’s the client’s budget and the client’s timeline.
5. Ownership of failure.
When a project fails, the framework gives the developer a defensible answer: we followed the process, we delivered increments, we responded to change. The client is left holding the outcome.
None of this is malice. Agile’s values are sound.
But here’s the contradiction:
The client is not a system-building expert. Agile asks them to act like one.
Prioritising a backlog requires knowing how components depend on each other. Accepting an increment requires knowing what “done” should mean. Verifying quality requires the ability to judge it.
Most clients can’t do any of that — and they shouldn’t have to. They know their business, not system architecture.
So the responsibilities aren’t really transferred. They’re just placed where they can’t be exercised — and the risk stays with the client anyway.
The client is told they’re “collaborating.” What they’re actually doing is carrying risk they didn’t know they’d accepted.
Before you sign a delivery contract, ask one question:
Who carries the risk when this goes wrong — and did I agree to that?