AGILE IN ACTION

Sunday, April 15, 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. 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)
    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)
  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)