Comments on: Bugs, defects and feedback

By: Matt Hinze

Matt Hinze — Thu, 01 Oct 2009 10:54:46 +0000

It is interesting how you classified them. I’ve always thought of them opposite that: where defects are “stop the line” issues and bugs are “anything that bugs the user”.

By: Siim

Siim — Thu, 01 Oct 2009 08:19:35 +0000

It’s interesting that there isn’t been any discussion on bug vs issue. Issue seems to be correct term for what most people call a bug.

So your process of handling bugs and defects seems correct way to me. So there can be some issue tracker software which stores all customer issues which are coming from customer support for example. But in general, need for a special software depends on the scale of the project.

By: Vijay Santhanam

Vijay Santhanam — Thu, 01 Oct 2009 06:21:03 +0000

This whole paper thing is intriguing! I like reading about your process.

if a customer has an issue that ends up being a new story, does that then get put down on paper? Or was your last post only referring to bug-bugs that are paper post-it persisted onto your desk?

I wish my first level customer support had that readable handwriting.

By: Mihai Lazar

Mihai Lazar — Wed, 30 Sep 2009 18:36:12 +0000

Indeed I see your point. It would be nice to hear more about how your system is organized.

15 minutes away from production fix.. WOW!! You really do have a nice team. It takes us 3 to 5 days to go into production although it’s a website build from scratch and all the developers know almost all that goes on with the system. We usually get change requests or bugs.. submit the fixes to the trunk, then they are tested by the testers ( obviously ), than some fixes are selected and go into staging.. and if everything on staging is fine we go into production.

I admit the way you work sounds like a dream at this point to me , which is why I’d like to hear more about the way the system is organized so that I can learn from it.