23
Waterfall To Agile: Contracts and other Rough Edges 5 th SCRUM meet up 11-Feb-2014 Dimitris Dimitrelos Senior Project Manager Dienekis Information Systems S.A. [email protected] All Photographs by Christos Georgalas christosg.org

Waterfall To Agile: Contracts and other Rough Edges

Embed Size (px)

DESCRIPTION

When it comes to Software Projects, Fixed Price contracts are the norm. What limitations and risks do they pose for the seller and the buyer? Do the work well with Waterfall? Can you do Fixed Price contracts with SCRUM? Should you do Fixed Price contracts with SCRUM? How? This is a presentation given in the 5th SCRUM Meetup, in Athens, at Feb-11 2014.

Citation preview

Page 1: Waterfall To Agile: Contracts and other Rough Edges

Waterfall To Agile: Contracts and other Rough Edges

5th SCRUM meet up11-Feb-2014

Dimitris DimitrelosSenior Project Manager

Dienekis Information Systems [email protected]

All Photographs by Christos Georgalas

christosg.org

Page 2: Waterfall To Agile: Contracts and other Rough Edges

The problem with contracts

Keep – you have to

Change – you can’t

Page 3: Waterfall To Agile: Contracts and other Rough Edges

Contract Types

• Fixed Cost• Cost Reimbursable• Time & material• Other…

Page 4: Waterfall To Agile: Contracts and other Rough Edges

Everybody loves Fixed Price Contracts

EasyRisk to YOUReally?they are here to STAY

Page 5: Waterfall To Agile: Contracts and other Rough Edges

FP + Waterfall + PM

More Analysis >> Better Estimation >> Detailed Contract >> Less Risk

Project Plan

Offer/Contract

Reqs/Analyse/Estimate

Page 6: Waterfall To Agile: Contracts and other Rough Edges

The estimation Paradox

• Low Risk vs. Getting the deal!• What’s it gonna be?

• Analysis Carries costs• Realistic pricing means

higher pricing

Page 7: Waterfall To Agile: Contracts and other Rough Edges

Can it go wrong?

UnderestimationScope changeChange management does not

workCustomer bullyingAnalysis fights

Page 8: Waterfall To Agile: Contracts and other Rough Edges

What if it goes wrong?

• Accountability >> Blame• Challenges Relationship• Options– Break the project– Take the hit– Formally renegotiate– Negotiate/threat/adjust/silently change

the contract

Page 9: Waterfall To Agile: Contracts and other Rough Edges

What should we do?

“I have a dream; the dream that IT professionals stop offering on fixed price bids. Because it is unethical, risky and untrustworthy to make that kind of hard-coded promises in a complex and fast-changing environment. It is… unprofessional. ”

 Gunther Verheyen

Page 10: Waterfall To Agile: Contracts and other Rough Edges

Fixed Price with SCRUM

• Do it with a friend…• …who wants to get

involved• Fixed Price, Schedule• Fixed Scope?

Page 11: Waterfall To Agile: Contracts and other Rough Edges

SCRUM for FP contracts

• Vagueness is your friend!• Propose SCRUM (just don’t call it that)• Find a product owner. Find a product owner. Repeat

until you have a product owner.• Product backlog: High level/must be complete• SCRUM• Deliver value / Let customer take lead• Watch your back(log)

Page 12: Waterfall To Agile: Contracts and other Rough Edges

Public sector?

• RFP (Διακήρυξη)• Analysis after the contract?• Use SCRUM instead• Key risk: Product owner

Page 13: Waterfall To Agile: Contracts and other Rough Edges

Why AGILE? (Vote)

A. Customer/Organization forced me toB. Have been burned by WaterfallC. Want to increase software qualityD. Want to reduce development timesE. Is a big trend in S/W project management

Page 14: Waterfall To Agile: Contracts and other Rough Edges

My experience

Page 15: Waterfall To Agile: Contracts and other Rough Edges

The nightmare

• New customer / High priority project

• Underestimation• Scope changed• Death March• Heading for the Rocks

Page 16: Waterfall To Agile: Contracts and other Rough Edges

The turnaround

• Stopped fighting change• Built Full Backlog• Planned for 1 month only• Released every 10 days• Self organization• Followed Contract time limit• Then, T&M

Page 17: Waterfall To Agile: Contracts and other Rough Edges

How did it go?

• Terrible, for 2 sprints

• Overcontrolled

• Overcommited

• Underdelivered

• Missed deadlines

• But then, it took off. Happy ending.

Page 18: Waterfall To Agile: Contracts and other Rough Edges

Other Rough Edges

Page 19: Waterfall To Agile: Contracts and other Rough Edges

Self organization

• PM will not let go• Team will not pick up• Tip: Take the leap of faith• LET GO!

Page 20: Waterfall To Agile: Contracts and other Rough Edges

Overcommiting

• Team is not used in estimating using buffers

• Tip: Teach them• Tip: Measure/Adjust

Page 21: Waterfall To Agile: Contracts and other Rough Edges

Customer involvement

• Keep customer involved• Needs to maintain a product log• Should Inspect and evaluate every

sprint outcome• Tip: Offer higher quality

Page 22: Waterfall To Agile: Contracts and other Rough Edges

Management Support

• Get Management support• Fear of “Loss of Control”• Fear of “Planning Block”• Tip: Another presentation

Page 23: Waterfall To Agile: Contracts and other Rough Edges

Thank you

All Photographs by Christos Georgalas

christosg.org