Skip to main content

Fixed-Price, Fixed-Scope Contracts

This question has challenged the Agile community since the beginning: How do you do a fixed-price, fixed-scope project? Especially the big customers think they know exactly what they want, so their suppliers should be able to tell them exactly how long it will take and how much it will cost. In practice, neither of these beliefs are true.

Revenue is constant, regardless of the effort applied or the actual delivery date.

Desired Benefit: Clarify all the questions so the purchasing decision can be made on price. Move the risk for time and budget overruns to the supplier.

Structure: Agree on the deliverables, deliver it. Send a bill. Customers like fixed price projects because it gives them security (or at least they think so).

Decision-Making: Generally, the customer's governance level decides on changes and on whether things are done. This approach works better for runways than for smartphones because feedback cycles are usually relatively slow.

Scope changes: The name says it all, doesn't it? The change request game (correction: change request process) is intended to limit scope changes. This process is costly, and the changes are usually not preventable.

Risks: Obvious risk is on the side of the supplier. If the estimates are wrong, the project will lose money. A less obvious risk is the change request game, through which the supplier negotiates additional revenue through scope changes. If the supplier has badly underestimated the effort or risk, or quoted an unrealistically low price, the losses can even threaten the existence of the supplier, which also presents a problem to the customer.

Since the customer almost by definition wants more scope, ending the project can be difficult. The supplier wants the customer to be happy, so the supplier usually yields. The words ‘et cetera’ are very dangerous in the specification of a fixed price requirement.

If the supplier is not good at the change request game, the customer can milk the supplier until the supplier says, 'No more!'. This can risk the relationship with the customer.

The biggest risk is the impact of contracting for a runway when you are actually building a smartphone. Decision-making is slow and often far removed from the project team. The chances of arriving late with the wrong product are high, and this can have catastrophic consequences.

Relationship: Competitive to indifferent. Customers generally want to have more, and suppliers generally want to do less. The supplier wants the customer to be happy, so usually the supplier yields.

Tip: Specify the functional requirements with a user story or complete sentences that use active verbs, for example: “As a job hunter, I want to search for a job by location, so I can find a job close to where I live.” This makes it clear whether the backlog item has been achieved. You can do it, or you can’t. But it leaves negotiable how to achieve it. This gives you both an important wiggle room to simplify the implementation and makes it easier to declare a new request to be out of scope.

Mike Cohn’s classic, Agile Planning and Estimating offers strategies for estimating and pricing these kinds of projects.

You can get the whole book now, or you can read it a chapter at a time as I publish it here under the label ten contracts. To download the e-book or pre-order the physical book visit


Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …