AGILE IN ACTION

Sunday, 15 April 2007

Defect tracking tools and waste

Posted by Simon Baker

Defects are waste. User stories with known defects aren’t done and can’t be released, they’re partially complete work or inventory, and they are waste too. If you’re using a defect tracking tool you’re queuing up waste and you’re inspecting for quality after the code’s been written.

Eliminate waste . Avoid queues because they prevent throughput of released software and block the flow of value to the customer. Build quality into the code from the start by fixing defects as you go. To help improve the quality of code, developers should use test-driven development and testers should perform exploratory testing as developers complete vertical slices of user stories . If a defect is found, stop the line and fix it immediately. Don’t queue it up.

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)