Differences

This shows you the differences between two versions of the page.

--- 2013:agile_contracts [2012/11/27 21:15] – rogero
+++ 2013:agile_contracts [2016/06/11 14:05] (current) – external edit 127.0.0.1
@@ Line 2: / Line 2: @@
 Back to [[conference:committee:proposals-2013]]\\
 \\
-**Title**: Agile Contracts\\
+**Title**: Agile Contracts: Building Trust\\
 **Proposer**: [[2013:ewan_milne]]\\
 **Type**: Tutorial\\
 **Duration**: 45 minutes\\
 **Description**:
-The industry standard Fixed Price contract has been around for a long
+The Fixed Price contract continues to be the most common means of
-time, and continues to be a popular means of defining contracts for
+defining contracts for software development projects, despite the
-development projects, despite being based on the same assumptions
+amount of evidence suggesting that such contracts commonly contribute
-about being able to predict the future, and produce software according
+to project failure. Schedule and cost overruns, expensive change
-to a pre-defined plan that the Agile movement has gone a long way to
+control procedures, and a lack of trust between customer and supplier
-breaking down in the last decade.\\
+are typical war stories.\\
 \\
-Suppliers often face a struggle to engage customers in a way which
+Essentially the fixed price contract is based on the same assumptions
-minimises contract negotiation and allows real collaboration to begin.
+about a fully predictable, easily planned future as the waterfall
-Time and materials contracts are often used, but are not the ideal
+model. The Agile movement has gone a long way to breaking down such
-solution for either party. So what is the best way forward for those
+assumptions in the last decade, so that agile software delivery is now
-on both sides of the negotiation table? In this session I will explore
+firmly in the mainstream. However, suppliers still often face a
-some ideas for how to define contracts or run a procurement process in
+struggle to engage customers in a way which minimises contract
-an agile manner, in a way which better supports customer and supplier
+negotiation and allows real collaboration to begin.\\
-collaboration towards shared goals.\\
 \\
-This session will be run as a tutorial, with the possible addition of
+In this session we will look at a number of possible contract models
-a discussion session: I do not claim to have the answers to the
+which support an agile way of working to a greater or lesser degree,
-questions I’m raising, and so may round off with an informal panel:
+and explore the issues surrounding the procurement process. Can a
-this will depend on getting hold of participants\\
+contract form the basis of a relationship built on trust and mutual
+benefit?\\
 \\
-Roger: Yes. I suspect it will be of interest to those with either external or 'internal' markets.
+\\
+Roger: Yes. I suspect it will be of interest to those with either external or 'internal' markets.\\
+Asti: I've seen this question come up several times on various forums. I'd attend \\