AGILE IN ACTION

Wednesday, May 16, 2007

How did it get to be so wrong?

Posted by Simon Baker

A short while ago I said that fixed-price contracts don’t work . Over on the Scrum Development group there’s a discussion about competitiveness, estimates and organization culture .

Dave Martin said: People underbid because it gets them the initial contract as many clients will just go for the lowest bid. Once the project is underway, the costs start to escalate and the client has 2 options - pay up or write the project off and start again. The client is often better off writing off their initial investment and starting over but its amazing how often they don’t do that and continue to burn money.

Keith Sterling responded: This is why so many large consultancies stick to the waterfall method. By bidding low and stipulating a waterfall approach, yet knowing that 99.99% of all projects will undergo 25-35% change during its lifetime, they know they will be able to make up the shortfall in their bid with high value change requests. It’s a well known fact, yet unwritten rule that most large consultancies in the UK base their business model on the volume of change requests they can generate during a project, and why most of these organisations have some of the biggest legal departments I have ever seen.

Where is the sense in awarding business based solely on the price? Price is meaningless without a measure of the quality being purchased. If clients award business to the lowest bidder they’re likely to receive low quality and high cost. You get what you pay for. And the client-vendor relationship will become acrimonious as neither party is satisified and it falls to the lawyers to fight it out. Deming predicated that driving down the price without regard to quality and service will drive good vendors and good service out of business . He was right but it’s actually worse. As Keith describes, we now see companies making money from providing poor quality by charging extortionate sums for change requests. It’s part of their business models. What a truly sad state of affairs.

Wouldn’t it be better to enter into and nurture cooperative partnerships for the long-term that are built on mutual loyalty, trust and confidence, and which share the risks and the rewards? If you treat your partners as extensions to your business and align incentives so that everybody works for the good of the partnership, then quality will return, cost will fall, speed of delivery will increase, customers will be happy and everyone will realise prosperity.

Creative Commons Licence

Recent Posts

  1. Debugging Grails Database Performance
  2. Grails for Hipsters
  3. Governance - Friend or Foe?
  4. The Energized Work lab is moving aboard ship
  5. Gus Power on the future of software development at The CW500 Club
  6. Agile On The Beach: Session: How Are We Doing?
  7. Presenting BuyaPowa at Hacker News London
  8. Knowledge nuggets from Kent Beck
  9. There's gold in them thar hills
  10. No Bull: An author's note

Archives

  1. 2013 (2)
  2. 2012 (27)
  3. 2011 (24)
  4. 2010 (31)
  5. 2009 (41)
  6. 2008 (69)
  7. 2007 (152)
    1. December (11)
    2. November (7)
    3. October (17)
    4. September (8)
    5. August (7)
    6. July (13)
    7. June (15)
    8. May (24)
      1. Product Owner and business marksmanship
      2. Say something
      3. 7 faces of leadership
      4. Scrum Master pulls the trigger
      5. Left leg or whole body?
      6. Additional values
      7. Layman's Manifesto
      8. Brian Marick wants to stir things up
      9. Iterating user interfaces
      10. Lessons are learned ...
      11. Quality is ...
      12. How did it get to be so wrong?
      13. Does standardisation suppress innovation?
      14. Is there a better way?
      15. Wake up and smell the complacency
      16. It takes 1 woman 9 months to make a baby
      17. You, organisational hierarchies, avast there!
      18. Story test-driven development
      19. Agile estimation techniques
      20. Fixed-price contracts don't work
      21. Competing on the basis of speed
      22. Testing in agile projects
      23. Jeff Sutherland on tuning Scrum
      24. Talking about agility
    9. April (14)
    10. March (19)
    11. February (7)
    12. January (10)
  8. 2006 (128)
  9. 2005 (63)
  10. 2004 (2)

Tags

agile (43) big visible chart (15) conference (43) culture (18) extreme programming (22) leadership (18) lean (47) people (27) planning (17) retrospective (18) scrum (41) story (19) team (30) testing (19) xpday (19)