Skip to main content

The 10 contracts for your next Agile software project

Which contract form is the right one for your project? It depends. In this chapter we examine each of the widely used contract forms and evaluate them in the context of the criteria we set out in Chapter 5, What is the purpose of a contract?

Photo courtesy of hydropeek@flickr CC-BY-2.0

  1. The Sprint Contract - Not really a contract, but a useful metaphor to describe the agreement within the Scrum Team during the sprint.
  2. Fixed-Price, Fixed-Scope - All the product decisions are taken up front. The winner is the master of the change request game.
  3. Time and Materials (T&M) – Risk is owned by the customer. So are the costs.
  4. T&M with Fixed Scope and Cost Ceiling – The worst of both worlds from the supplier’s point of view.
  5. T&M with Variable Scope & Cost Ceiling – A pragmatic approach to outsourced product development.
  6. Phased Development – How venture capitalists work with start-ups.
  7. Bonus and Penalty Clauses – Looks good on paper, works better with things you can build out of concrete. 
  8. Fixed Profit – Share the risk and incentivizes both parties to come to a conclusion.
  9. Money for Nothing, Changes for Free” – Encourages both customer and supplier to focus on value.
  10. Joint Ventures – A marriage made in heaven…? Or hell?!

The text is excerpted from Ten Contracts For Your Next Agile Project, by Peter Stevens. 
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…

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 …

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…