Skip to main content

Ten contracts for your next Agile project

As a customer or supplier of software services at the beginning of an Agile software development project, you know that there is too much at stake to work with just a verbal agreement. Although the Agile Manifesto values customer collaboration above contracts, written contracts are often necessary when working with external suppliers. What do you need to know? How can the contract help you achieve a good result? What are the traps to avoid?
Kevin Smith CC-BY scootergenious.com.png
Contract Cloud courtesy of Kevin Smith scootergenious.com

Ten years ago, I wrote an article for AgileSoftwareDevelopment.com called Ten Contracts for Your Next Agile Project. Artem Marchenko, the founder and editor, was really enthusiastic about this article and pushed me to make it thorough, well-researched and well-documented. This article became a popular reference. I was invited to speak about the ten contract forms at the Munich Scrum Gathering in October 2009. And I was thrilled to see the search autocomplete suggest the title after typing just “10 contracts.”

Alas, ASD is no more, but various people have requested that I republish the article. Last fall I started working on an update. I got it “90% finished” but never quite got around to publishing it.

A few days ago, while attending Jacopo Romei’s meetup on “Extreme Contracting”, I was surprised to see some of my original language and risk/reward diagrams reproduced in his presentation – with attribution to someone else! It’s clear: The topics in this book are still relevant!

I went on the Internet and discovered that the original article and presentation are hard to find and many of the reproductions are without attribution. So enough procrastination, it is time to republish!

I have learned a lot about Agility in the last ten years. The community has advanced a lot in this time. So, an update is more than necessary.

One caution: IANAL. I am not a lawyer. The advice in the following pages is based on my experience as a consultant, trainer and entrepreneur. If you need advice, get the advice you need. It may seem expensive, but good advice can be much cheaper than no advice!

I have expanded the original two articles into a 58 page-book which should serve as a lightweight guide for your next Agile software project! 

You can get the whole book now, or you can read it a chapter at a time as I publish it here under under the label ten contracts. As I publish the chapters (scheduled for a period of three weeks), I will activate the links below.

Ten contracts for your next Agile project, by Peter Stevens
Table of contents

7.8. Fixed-Profit

You can download the e-book or pre-order the physical book at https://saat-network.ch/ten

Comments

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 …