Recently we gathered some of our thoughts and practices about fixed price into a longer article which starts the series for agile techniques that work (don’t know yet how often we will be able to publish one of these).
We like to say that fixed price contracts are evil, but they are reality which many agile teams have to face. So what if we try to tame it instead of fighting against it?
The main point in the “Agile Team Meets a Fixed Price Contract” is that what actually bothers us in the iron triangle is not a fixed price nor the time but the scope which is defined upfront. So what actually the agile team needs to try, is to change the explicitly defined requirements into scope defined as the amount of work which has to be done.
In other words, exchange a “what” into “how much” value we need to deliver because “what” is about to change and we want that change to happen. How the company can execute this kind of contract using agile practices to achieve better results with lower risk?
Take a look at the full article in the white papers section:
http://www.tinypm.com/whitepapers
As always we are waiting for your comments. What works for us may not work for you, so we are always happy to hear about new ideas that worked in your context.
Tags: agile, agile metrics, contracts, planning, scrum
Follow us on Twitter
Read our Blog
Find us on Facebook