Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace:
why_shouldn_t_we_set_up_dedicated_defect_teams

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
why_shouldn_t_we_set_up_dedicated_defect_teams [2020/06/02 14:22] – external edit 127.0.0.1why_shouldn_t_we_set_up_dedicated_defect_teams [2020/06/04 11:20] (current) – Removed LINKBACK hans
Line 1: Line 1:
 ====== Why Shouldn't We Set Up Dedicated Defect Teams? ====== ====== Why Shouldn't We Set Up Dedicated Defect Teams? ======
  
-Or "What are the benefits of having value production teams work on defects?"+> Or "What are the benefits of having value production teams work on defects?"
  
 Came across [[http://agileotter.blogspot.com/2014/01/bug-teams-well-meaning-foolishness.html|"Bug teams - Well Meaning Foolishness by Tim Ottinger"]] recently. Discussion is well-thought description of the downside of setting up a bug team but I thought it had a wider message than that - the idea that we need to treat production of bugs as something that you can analyze, run experiments to reduce, and increasingly create a team "immunity system" aimed at preventing bugs. Came across [[http://agileotter.blogspot.com/2014/01/bug-teams-well-meaning-foolishness.html|"Bug teams - Well Meaning Foolishness by Tim Ottinger"]] recently. Discussion is well-thought description of the downside of setting up a bug team but I thought it had a wider message than that - the idea that we need to treat production of bugs as something that you can analyze, run experiments to reduce, and increasingly create a team "immunity system" aimed at preventing bugs.
Line 21: Line 21:
  
 There may still be reasons we create a bug team to help deal with a capacity issue. But it is also important to understand that setting up a bug team won't necessarily improve the quality of the code produced. Irrespective of whether there is a team in place to do this, we still need to deal with the root cause issue, and really focus on understanding why we have defects. We need to set up our development environment so that we get feedback very quickly about the bugs, and then encourage real analysis back to the coding that was done to understand how we can stop bugs from entering the system the same way. This is the only approach that has the potential to reduce the capacity that we allocate to working bugs freeing everyone up for doing more interesting, and more valuable work. There may still be reasons we create a bug team to help deal with a capacity issue. But it is also important to understand that setting up a bug team won't necessarily improve the quality of the code produced. Irrespective of whether there is a team in place to do this, we still need to deal with the root cause issue, and really focus on understanding why we have defects. We need to set up our development environment so that we get feedback very quickly about the bugs, and then encourage real analysis back to the coding that was done to understand how we can stop bugs from entering the system the same way. This is the only approach that has the potential to reduce the capacity that we allocate to working bugs freeing everyone up for doing more interesting, and more valuable work.
- 
  
 {{tag>FAQ Quality Bugs Defects Team}} {{tag>FAQ Quality Bugs Defects Team}}
  
-~~LINKBACK~~ +
-~~DISCUSSION~~+
/home/hpsamios/hanssamios.com/dokuwiki/data/pages/why_shouldn_t_we_set_up_dedicated_defect_teams.txt · Last modified: 2020/06/04 11:20 by hans