1 / 60

Agile Contracts ?

Agile Contracts ?. Agile Riga Day 2012 Johannes Brodwall , Principal Architect Steria Norway @ jhannes. Motivation. Agile Manifesto

odelia
Download Presentation

Agile Contracts ?

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile Contracts? Agile Riga Day 2012 Johannes Brodwall, Principal Architect Steria Norway @jhannes

  2. Motivation

  3. Agile Manifesto Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan

  4. Customer collaborationover contract negotiation

  5. Does «contract» make a difference?

  6. Hold on, I expected a muchfancier UI for this. ? Supplier Customer

  7. Most commoncontracts: Fixedprice Time and material

  8. Hold on, I expected a muchfancier UI for this. Crap Supplier Customer

  9. Hold on, I expected a muchfancier UI for this. No problem, we’llworksome more Supplier Customer

  10. «Time and material» createsthe most happiness

  11. «Time and material» createsthe most happiness (Source: My best and worstprojects)

  12. So whycareaboutthe rest?

  13. Do youpaytaxes?

  14. How shouldyourgovernment handle: We’rerunningoutofmoney for pensions Weneed to changetherules! The current system is huge

  15. How shouldgovt spend yourmoney? A big, state-run project Hire a random company to do it all Just payconsultantsuntilit’s done

  16. Can Agile help?

  17. Customer collaborationover contract negotiation

  18. PS2000 + Agile

  19. Typical Norwegian publicsectorproject: «Weneed to replacehuge system X…

  20. Typical Norwegian publicsectorproject: «Weneed to replacehuge system X… … we’d like to useScrum»

  21. PS2000: «Target price»

  22. (Target price:Set a budget,report cost.Supplier & clientsplitsdifference)

  23. PS2000 + agile: «Colocated» «Sprints» «Sprint reviews» «Product owner» «Product backlog»

  24. … butalso «Negotationphase» «Requirementphase» «Acceptance test phase»

  25. Whence PS2000?

  26. Contract standard from Norwegian Computing Association

  27. 2001: PS2000 with target price

  28. 2009: PS2000 + Agile

  29. Norwegian trends: 2 Agile usergroupswith 100+ people at meetings from 2005 Conferences: Smidig 2007 + 2008 Networking: Devs <-> PMs <-> customers Meetupsaboutcontracts Scrumcertifications Large and diverse consultancyindustry

  30. Someprojecthighlights

  31. LARM: In progress Domain:Electricity reserve power Application:Operator UI Internal Integration Project size: 2 scrum teams plus support Organization:Supplier + Customer teams Colocatedat customersite Team size: 7 per team Duration: 3 years (1,5 yearsleft) Sprint length: 3 weeks (customer present) Releases:3 times per year Contract: Target pricing for wholescope

  32. Smart move: Reliable productbacklogusing scenarios

  33. Big win: First release in use 1 yearaftercontract, containing most used screen

  34. Big loss: Featurecreepofindividualuserstories

  35. PERFORM: Completed Domain: State pensionfund Application:Case worker UI External Integration Processflow Project size: 12-14 scrum teams plus support Organization: Three supplierswith 3-6 teams Colocated at customersite Team size: 10 per team Duration: 3 years Releases: 3 times per year Sprint length: 3 weeks, withshared demo Contract: First release: Time & materials Subsequent: Target pricing per release

  36. Smart move: Contractonprice per release First releaseon T&M «Competing» suppliers

  37. Big win: Delieveredwhatwasneeded Government is happy Users are happy

  38. Big loss: Full time requirementspec Hostilearchitecture team

  39. Customer collaborationover contract negotiation

  40. Reality: We must compete We must commit

  41. IMAGINE: Pure fabriaction Project size: Somescrum teams withindependent users and productowners Organization:Colocated at customersite Team size: 6-8 per team Duration: 3 years Sprint length: 2 weeks, withshared demo Releases:Everymonth Bidding:Performancecompetition Contract:Target estimate per user story

  42. Bidding: Competitivedelivery

  43. Project reference Resumes Hourly rates Pre-qualification Supplier Supplier Supplier Supplier Supplier Customer Supplier

  44. Supplier Supplier Supplier

  45. 6-10 weeks Supplier Supplier Supplier

  46. Analysis Delivery Coding Supplier Supplier Supplier Analysis Analysis Delivery Coding Delivery Coding Analysis Coding Delivery

  47. Analysis Delivery Coding Supplier Supplier Supplier Analysis Analysis Delivery Coding Delivery Coding Analysis Coding Delivery

  48. Pricing: Customersetsbudget

  49. I need a screen shot for X. Wewantsomething simple. Ok. 2 kEURO Supplier Customer

  50. We’ve spent half thebudget Do you have anything to show for it? It’s not testedyet. Supplier Customer Okay, I’mpullingtheplug

More Related