Agile Contracts ?

78
Agile Contracts? AgilePrague 2012 Johannes Brodwall, Principal Architect Steria Norway @jhannes

description

Agile Contracts ?. AgilePrague 2012 Johannes Brodwall , Principal Architect Steria Norway @ jhannes. Part I. Motivation. Agile Manifesto - PowerPoint PPT Presentation

Transcript of Agile Contracts ?

Page 1: Agile  Contracts ?

Agile Contracts?

AgilePrague 2012Johannes Brodwall, Principal Architect

Steria Norway

@jhannes

Page 2: Agile  Contracts ?

Part I

Page 3: Agile  Contracts ?

Motivation

Page 4: Agile  Contracts ?

Agile ManifestoIndividuals and interactions over processes and toolsWorking software over comprehensive documentation

Customer collaboration over contract negotiationResponding to change over following a plan

Page 5: Agile  Contracts ?

Agile ManifestoIndividuals and interactions over processes and toolsWorking software over comprehensive documentation

Customer collaboration over contract negotiationResponding to change over following a plan

Page 6: Agile  Contracts ?

Does «contract» make a difference?

Page 7: Agile  Contracts ?

Supplier

Customer

Hold on, I expected a much fancier UI

for this.?

Page 8: Agile  Contracts ?

Most common contracts:Fixed price

Time and material

Page 9: Agile  Contracts ?

Supplier

Customer

Hold on, I expected a much fancier UI

for this.

Crap

Page 10: Agile  Contracts ?

Supplier

Customer

Hold on, I expected a much fancier UI

for this. No problem, we’ll work some more

Page 11: Agile  Contracts ?

«Time and material» creates the most happiness

Page 12: Agile  Contracts ?

«Time and material» creates the most happiness

(Source: My best and worst projects)

Page 13: Agile  Contracts ?

«Time and material» creates the most happiness

(Also for customer!)

Page 14: Agile  Contracts ?

So why care about the rest?

Page 15: Agile  Contracts ?

Do you pay taxes?

Page 16: Agile  Contracts ?

How should your government handle:

• We’re running out of money for pensions• We need to change the rules!

• The current system is huge

Page 17: Agile  Contracts ?

How should govt spend your money?

• A big, state-run project?• Hire a random company to do it all?

• Just pay consultants until it’s done?• “Just be agile”?

Page 18: Agile  Contracts ?

Can Agile help?

Page 19: Agile  Contracts ?

Customer collaboration over contract negotiation:

• Contracts hurt• Big tax-funded projects are inevitable

• Agile can help – but insufficient

Page 20: Agile  Contracts ?

Part II

Page 21: Agile  Contracts ?

PS2000 + Agile

Page 22: Agile  Contracts ?

Typical Norwegian public sector project:

«We need to replace huge system X…

Page 23: Agile  Contracts ?

Typical Norwegian public sector project:

«We need to replace huge system X…… we’d like to use Scrum»

Page 24: Agile  Contracts ?

PS2000:«Target price»

Page 25: Agile  Contracts ?

(Target price:Set a budget,

report cost.Supplier & client splits difference)

Page 26: Agile  Contracts ?

PS2000 + agile:«Colocated»

«Sprints»«Sprint reviews»«Product owner»

«Product backlog»

Page 27: Agile  Contracts ?

… but also«Negotation phase»

«Requirement phase»«Acceptance test phase»

Page 28: Agile  Contracts ?

Whence PS2000?

Page 29: Agile  Contracts ?

Contract standard from Norwegian Computing

Association

Page 30: Agile  Contracts ?

2001: PS2000 with target price

Page 31: Agile  Contracts ?

2009: PS2000 + Agile

Page 32: Agile  Contracts ?

Norwegian trends:• Active community

• Meetups about contracts• Scrum certifications

• Large and diverse consultancy industry

Page 33: Agile  Contracts ?

Some project highlights

Page 34: Agile  Contracts ?

In progressLARM: Domain: Electricity reserve powerApplication: Operator UI

Internal IntegrationProject size: 2 scrum teams plus supportOrganization: Supplier + Customer teams

Colocated at customer siteTeam size: 7 per teamDuration: 3 years (1,5 years left)Sprint length: 3 weeks (customer present)Releases: 3 times per yearContract: Target pricing for whole scope

Page 35: Agile  Contracts ?

?

Bid

Apr, 2010

Negotiation

Aug, 2010

Mar, 2010

Elaboration

Nov, 2010

Release 1Sprint Sprint Sprint Sprint Sprint

May, 2011

Acceptance Production

Sept, 2011

Elaboration Sprint Sprint Sprint

Sprint Sprint

Sprint

SIGNED

Page 36: Agile  Contracts ?

Smart move:Reliable product backlog using

scenarios

Page 37: Agile  Contracts ?

Big win:First release in use 1 year after contract, containing most used

screen

Page 38: Agile  Contracts ?

Big loss:Feature creep of individual user

stories

Page 39: Agile  Contracts ?

CompletedPERFORM: Domain: State pension fundApplication: Case worker UI

External IntegrationProcess flow

Project size: 12-14 scrum teams plus supportOrganization: Three suppliers with 3-6 teams

Colocated at customer siteTeam size: 10 per teamDuration: 3 yearsReleases: 3 times per yearSprint length: 3 weeks, with shared demoContract: First release: Time & materials

Subsequent:Target pricing per release

Page 40: Agile  Contracts ?

Smart move:Contract on price per release

First release on T&M«Competing» suppliers

Page 41: Agile  Contracts ?

Big win:Delievered what was needed

Government is happyUsers are happy

Page 42: Agile  Contracts ?

Big loss:Full time requirement spec

Hostile architecture team

Page 43: Agile  Contracts ?

Customer collaboration over contract negotiation

Page 44: Agile  Contracts ?

Reality:• We must compete

• We must commit

Page 45: Agile  Contracts ?

Part III

Page 46: Agile  Contracts ?

Wishful contracts

Page 47: Agile  Contracts ?

The source of our troubles

Page 48: Agile  Contracts ?

Fabulation

Speculation

Bungling

Yelling

Worrying

2 year - development Use

Page 49: Agile  Contracts ?

Fabulation

Speculation

Bungling

Yelling

Worrying

2 years - development Use

ContractPrice

ScopeDeliverableOk?

Page 50: Agile  Contracts ?

The problem

Page 51: Agile  Contracts ?

Fabulation

Speculation

Bungling

Yelling

Worrying

2 years - development Use

ContractPrice

Scope

Page 52: Agile  Contracts ?

A way out?

Page 53: Agile  Contracts ?

Pure fabria

ction

IMAGINE: Project size: Some scrum teams with independent

users and product ownersOrganization: Colocated at customer siteTeam size: 6-8 per teamDuration: 3 yearsSprint length: 2 weeks, with shared demoReleases: Every month

Bidding: Performance competitionContract: Target estimate per user story

Page 54: Agile  Contracts ?

Pricing: Unit pricing

Page 55: Agile  Contracts ?

Menu:• Simple GUI: 20 kNOK• Complex GUI: 50 kNOK• GUI that customer decides

how looks: 100 kNOK

(Or 2, 5, 20 story points)

Page 56: Agile  Contracts ?

Supplier

Customer

I need a screen shot for X. We want something simple. Ok. 2

kEURO

Page 57: Agile  Contracts ?

Supplier

Customer

Do you have anything to show for it?

We’ve spent half the budget

Nothing that is tested yet

Okay, I’m pulling the

plug

Page 58: Agile  Contracts ?

Supplier

Customer

Stop!

We’ve spent the budget

Page 59: Agile  Contracts ?

Supplier

Customer

But I wanted rounded corners, and gradients!

No problem, but that means it’s

no longer «simple»

Oh, never mind.

Page 60: Agile  Contracts ?

(I hate having this sort of discussions)

Page 61: Agile  Contracts ?

Supplier

Customer

But I wanted …!

Oh, I guess we have to do it, thenNo way! Change

order!

Hmm…we didn’t consider that when we gave the price

Page 62: Agile  Contracts ?

Bidding: Competitive delivery

Page 63: Agile  Contracts ?

Supplier

Supplier

Supplier

Supplier

Supplier

Customer

Project referenceResumesHourly rates

Supplier

Pre-qualification

Page 64: Agile  Contracts ?

Supplier

Supplier

Supplier

Page 65: Agile  Contracts ?

Supplier

Supplier

Supplier

6-10 weeks

Page 66: Agile  Contracts ?

Supplier

Supplier

AnalysisCoding

Delivery

Analysis

Coding

Delivery

Analysis

Coding Coding

AnalysisDelivery

Delivery

Supplier

Page 67: Agile  Contracts ?

Supplier

Supplier

AnalysisCoding

Delivery

Analysis

Coding

Delivery

Analysis

Coding Coding

AnalysisDelivery

Delivery

Supplier

Page 68: Agile  Contracts ?

Another model

Page 69: Agile  Contracts ?

Pure fabria

ction

Supplier Commitment:Δ ☺Δ $

IMAGINE:

Page 70: Agile  Contracts ?

Questions and discussions

Page 71: Agile  Contracts ?

Conclusion

Page 72: Agile  Contracts ?

Customer collaboration over contract negotiation

Page 73: Agile  Contracts ?

We need an answer for large investments

Page 74: Agile  Contracts ?

Norway’s answer ain’t half bad

Page 75: Agile  Contracts ?

Norway’s answer ain’t half bad

Page 76: Agile  Contracts ?

But

Page 77: Agile  Contracts ?

We can do better

Page 78: Agile  Contracts ?

Thank [email protected]

http://johannesbrodwall.com

http://twitter.com/jhannes