AGILE IN ACTION

Tuesday, 24 April 2007

Improve quality to increase productivity

Posted by Simon Baker

Sadly, these days most managers are more interested in the cost of quality than in quality itself. Essentially, they’re wondering ‘how low can we take our quality before we start losing customers?’ They might permit us to improve quality up to a point, beyond which they see further improvements in quality as a poor investment. When a manager warns us that we’re in danger of putting too much time and effort into quality, he’s wrong! We can’t take quality too far.

And when scope, time and cost are fixed, as is so often the case these days, we’ve all been guilty of habitually cutting quality to meet the deadline. It’s madness! This is one of the major contributing factors to project failure.

Seeking excellence through continuous improvements in quality initiates a chain reaction of positive and beneficial results.


Improve quality to increase productivity
Originally uploaded by sjb140470 .


When you continuously improve quality the defect count is significantly reduced and there are fewer delays. You find yourself with more time to spend on adding new features that are valuable to your customers. Productivity is increased and costs are reduced. People are happy in their jobs. Existing customers see more of the features they’ve requested materialise in the product with fewer defects, which secures their continuing loyalty. And new customers are attracted to your product because it’s feature-rich, has a higher quality and is more reliable than competitor products and comes at a lower price. All this is very good for business.

Creative Commons Licence

Recent Posts

  1. Managing costs provides a false sense of security
  2. State of Agile survey for 2011 tells a familiar story
  3. (I can't get no) satisfaction, let alone customer delight
  4. Positive emotions and purpose
  5. People don't buy what you do, they buy why you do it
  6. Too busy chopping wood to sharpen the axe
  7. So you want a fresh apple
  8. Systems are seductive
  9. Crack cocaine problem-solving and complexity
  10. Beware the Coefficient of Fiction

Archives

  1. 2012 (4)
  2. 2011 (24)
  3. 2010 (31)
  4. 2009 (41)
  5. 2008 (69)
  6. 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)
    9. April (14)
      1. Does the Agile Manifesto need refactoring? Should it be extended?
      2. Self-management and self-leadership
      3. Improve quality to increase productivity
      4. Self-organisation again
      5. Breaking habits
      6. Self-organisation
      7. Put customers first and everything else follows
      8. I just came from there ...
      9. Defect tracking tools and waste
      10. Individuals and interactions over processes and tools
      11. Are you missing the point?
      12. Scrum Master, Master of Ceremonies and Quartermaster
      13. When you put it like that ...
      14. Become a certified Agile Software Specialist!
    10. March (19)
    11. February (7)
    12. January (10)
  7. 2006 (128)
  8. 2005 (63)
  9. 2004 (2)

Tags

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