RSS

Don’t let your buglets escape!

08 Dec

I caught up with an Agile team this week and learned a new word: buglet

We were discussing how the move to Agile methods has improved the quality of their products – the test lead pointed out that they have found and fixed a total of 8 defects so far in the project, previously there would have been hundreds by this stage of the project.   During the discussion they mentioned not letting buglets escape, which intrigued me.

It turns out that buglet is the term they’ve adopted for in-iteration test failures, when a test fails the tester notes the circumstances and records a buglet against the story so the developers can address it as soon as possible.  The whole team is focused on making sure buglets are squashed before the end of the iteration, making sure that stories are Done-Done-Done and keeping quality high.

Simple language and simple processes that are resulting in quality products that meet customer needs, faster better, cheaper.

What terms and approaches are your teams using to keep quality high?

Posted by Shane Hastie

Advertisements
 
3 Comments

Posted by on December 8, 2009 in Agile, Testing

 

Tags: ,

3 responses to “Don’t let your buglets escape!

  1. Parimala Shankaraiah

    December 14, 2009 at 4:50 pm

    Hi,
    Can you please elaborate on how the bug is different from a buglet?

    Regards,
    Parimala Shankaraiah

     
  2. Shane Hastie

    December 14, 2009 at 9:05 pm

    Hi Parimala

    A buglet is te result of a failed test INSIDE an iteration, the tester records the test failure details against the story and passes the story directly back to the developer working on it, the intent is to fix all buglets during the iteration they are found in, preventing defects from leaking into later iterations (it will always be quicker to fix the problem if it is found shorty after it is inserted).

    A bug is the result of a defect that is identified against a part of the system that is not being worked on in the current iteration (the dreaded regression). When a bug is found it is recorded in a defect log and (severity 1 possibly severity 2) worked on immediately or (sev 2 / 3 or below) goes onto the backlog of work to be prioritised and sequenced along with the outstanding stories.

    This focus on preventing defects from leaking out of an iterations is one of the reasons Agile projects often result in higher quality products.

    I hope this makes sense.

    Shane

     
  3. Parimala Shankaraiah

    December 16, 2009 at 2:21 am

    Thanks for your response Shane. I got the idea behind buglet.

    One thing I really like about Agile is that it is people focused rather than process focused. Most of the things followed in Agile is a result of motivation rather than brute force 🙂

    Again, people have to be extremely sincere and honest for Agile to work wonders.

    Just my thoughts,
    Regards,
    Parimala Shankaraiah

     

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: