Comments on: Is Defect Tracking Dead in an Agile World? http://accurev.com/blog/2008/01/02/is-defect-tracking-dead-in-an-agile-world/ SCM and Agile Software Development Blog Wed, 09 May 2012 07:08:34 +0000 hourly 1 http://wordpress.org/?v=3.3 By: mark http://accurev.com/blog/2008/01/02/is-defect-tracking-dead-in-an-agile-world/comment-page-1/#comment-18763 mark Wed, 09 May 2012 07:08:34 +0000 http://blog.accurev.com/2008/01/02/is-defect-tracking-dead-in-an-agile-world/#comment-18763 Yes it was dead for me ! The most hard thing for me was to manage our bugs in our sprints but i just recently start using a new tool Yodiz and what i loved about it is that it allows you to add bugs in your sprints and releases and you can also associate a bug to user story this is one killer feature for me i think so it is the first agile project management tool which is allowing you to handle your issues in agile project and in your agile scrum Yes it was dead for me ! The most hard thing for me was to manage our bugs in our sprints but i just recently start using a new tool Yodiz and what i loved about it is that it allows you to add bugs in your sprints and releases and you can also associate a bug to user story this is one killer feature for me i think so it is the first agile project management tool which is allowing you to handle your issues in agile project and in your agile scrum

]]> By: Rob http://accurev.com/blog/2008/01/02/is-defect-tracking-dead-in-an-agile-world/comment-page-1/#comment-18759 Rob Fri, 27 Apr 2012 09:30:05 +0000 http://blog.accurev.com/2008/01/02/is-defect-tracking-dead-in-an-agile-world/#comment-18759 I agree that a bug tracking system is very handy, mainly for tracking details about bugs. One problem though is that the system can over time become out-dated, full of hundreds of bugs that no longer exist. Working on new features we may remove old code (and hence bugs) or fix bugs without knowing and the system isn't updated. Time then has to be spent confirming each bug and removing them from the tracking system. You can in effect created work for yourself that won't make you any money. Arguably, if you have good enough reporting and feedback from your customers you shouldn't need a bug tracking system. If something is really wrong, you'll know and it'll jump up the work queue as higher priority. I don't believe in fixing a bug when you find one. It should enter the work queue like any other piece of work. Software is written by humans so there will always be bugs. Just make sure you're getting on with the piece of work that will benefit your customer (and in turn your business) most. I agree that a bug tracking system is very handy, mainly for tracking details about bugs.

One problem though is that the system can over time become out-dated, full of hundreds of bugs that no longer exist. Working on new features we may remove old code (and hence bugs) or fix bugs without knowing and the system isn’t updated. Time then has to be spent confirming each bug and removing them from the tracking system. You can in effect created work for yourself that won’t make you any money.

Arguably, if you have good enough reporting and feedback from your customers you shouldn’t need a bug tracking system. If something is really wrong, you’ll know and it’ll jump up the work queue as higher priority.

I don’t believe in fixing a bug when you find one. It should enter the work queue like any other piece of work. Software is written by humans so there will always be bugs. Just make sure you’re getting on with the piece of work that will benefit your customer (and in turn your business) most.

]]> By: Adele Adam http://accurev.com/blog/2008/01/02/is-defect-tracking-dead-in-an-agile-world/comment-page-1/#comment-18748 Adele Adam Wed, 28 Mar 2012 07:18:34 +0000 http://blog.accurev.com/2008/01/02/is-defect-tracking-dead-in-an-agile-world/#comment-18748 In our office Agile is often discussed. I've heard the office colleagues saying that pure agile does not deal much with bugs/issues/defects. So we have to manage bugs separately from agile. For this purpose we are <a href="http://www.yodiz.com" rel="nofollow">using a tool Yodiz</a> in our office for managing Agile and bugs in a handy way. In our office Agile is often discussed. I’ve heard the office colleagues saying that pure agile does not deal much with bugs/issues/defects. So we have to manage bugs separately from agile. For this purpose we are using a tool Yodiz in our office for managing Agile and bugs in a handy way.

]]> By: Scott Rosin http://accurev.com/blog/2008/01/02/is-defect-tracking-dead-in-an-agile-world/comment-page-1/#comment-379 Scott Rosin Fri, 08 Feb 2008 21:27:12 +0000 http://blog.accurev.com/2008/01/02/is-defect-tracking-dead-in-an-agile-world/#comment-379 So, lets see... A bug gets reported, a programmer starts working on it. Then another bug is reported. The programmer writes it down on a piece of paper so he won't forget it. Then another one is reported. The programmer, says to himself "Ya know, instead of writing all these bugs down on a piece of paper, I'll put them in a database somewhere. And I'll write a web interface to it so I can get the bugs at home too." Thus a Defect Tracking System is born into an Agile World. So, lets see… A bug gets reported, a programmer starts working on it. Then another bug is reported. The programmer writes it down on a piece of paper so he won’t forget it. Then another one is reported. The programmer, says to himself “Ya know, instead of writing all these bugs down on a piece of paper, I’ll put them in a database somewhere. And I’ll write a web interface to it so I can get the bugs at home too.” Thus a Defect Tracking System is born into an Agile World.

]]> By: Cory von Wallenstein http://accurev.com/blog/2008/01/02/is-defect-tracking-dead-in-an-agile-world/comment-page-1/#comment-378 Cory von Wallenstein Mon, 07 Jan 2008 02:27:07 +0000 http://blog.accurev.com/2008/01/02/is-defect-tracking-dead-in-an-agile-world/#comment-378 I've heard of folks say the same... from my experience, it's often only when multiple reports in the issue tracking system come in that we have enough information to actually reproduce the problem and fix it. If we were to just dive right into the code on the first report of a problem, it would take multiple times the effort to fix the problem than if we were armed with a handful of scenarios that can be used to reproduce and isolate the problem. I’ve heard of folks say the same… from my experience, it’s often only when multiple reports in the issue tracking system come in that we have enough information to actually reproduce the problem and fix it. If we were to just dive right into the code on the first report of a problem, it would take multiple times the effort to fix the problem than if we were armed with a handful of scenarios that can be used to reproduce and isolate the problem.

]]>