User pain

Monday, June 23, 2008 1 Comments

After reading Jonathan's interesting post about bug classification, I got interested in the article behind it, finding a very promising approach. It has been an issue for us during the last months and this approach looked good to the team.

After making a few samples with some variations on the formula, we decided to give it a try, so I implemented a few changes during the weekend to support it on our internal defect tracking tool (it's a bit primitive, but easy to customize), here you can see the result:

I think the method will need to be fine-tuned for our needs, but we already see an improvement over just having a very subjective "priority" field for the bug.

Thanks Jonathan for the excelent reference!

By the way, the original article can be found here. It's worth reading!

1 comment:

  1. It sounds easy, but it really reminds me to "structured estimation" as introduced by Steve McConnell at "Software Estimation: Demystifying the Black Art".

    It is so simple, but it helps you thinking in a more structured way. When you just say "high" or "low" or something like that, you're not normally making your best, and this really simple technique helps!

    Good work!