The no bugs journey part 3what kind of bug is this?

Posted by: Eric Gunnersons C# Compendium, on 02 Apr 2015 | View original | Bookmarked: 0 time(s)

If you are in a buggy group, you have a lot of bugs.

After writing the preceding, Ill endeavor to make the rest of this post slightly less obvious.

Anyway, so, you have a lot of bugs, and you need to get better. How can you get started?

Well, theres a common technique in agile called root-cause analysis. Its a good technique, but your team isnt ready for it and you cant afford to do it.

Instead, I recommend a technique I came up (probably not uniquely) that I call bug categorization. I started this when I team that I was on had a notably buggy iteration, and I noticed that a fair number of the bugs were just sloppy not reading the spec, not running the app after they had made a change, that sort of thing.

What I wanted was a way to help the team to clean up their act without being prescriptive.

So, I went through all the bugs something like 120 and did a really quick classification on each of them, putting them into one of the following categories:

  • Foreseeable: This is a bug that we should have caught.
  • External: Somebody else broke us.
  • Existing: This bug existed in past versions of our software.
  • Spec: There was a problem with the spec.
  • Other: Something else.

At our retrospective, I presented a graph of the bugs, and then put up a post-it that said, too many bugs.

And then I let the team work on the problem. And they did great, cutting the foreseeable bugs significantly in just a few iterations despite me expanding the definition of foreseeable to include more bugs.

And while my initial impetus was to reduce the sloppy bugs, the team spent a lot of time fixing bugs related to definition and communication. For example, they invented a dev/test/pm meeting that the start of a story to make sure everybody was on the same page.

So, thats bug categorization.

Category: Agile | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 614 | Hits: 7

Similar Posts

  • How to define state machine in Windows Workflow Foundation (WF) more
  • Speeding Up FireFox When Using the ASP.NET Development Server from Localhost more
  • Euchre Revisited: Fixing bugs and services releases (Matt Gertz) more
  • 5 years of Telerik, new office more
  • In software consulting, low cost consulting can be real. . . more
  • Toolkit 101: How the Toolkit project works more
  • TFS or not? Being a perfectionist is a realistic world more
  • TFS or not? Being a perfectionist in a realistic world more
  • Avoid Using a Database as an API Integration Point more
  • UpdateControls 1.1: Bug Fixes and UpdateAction more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD