Seth Godin, small correction
I'd post this on Seth's web site, but he only allows trackbacks.
In his post, Starting over with customer service, credits Fog Creek Software's, FobBugz with "accidentally revolutionized a huge piece of management", in regards to the software's ability to only allow a single person to own a single issue (or bug).
Seth's got an awesome blog, and seems to be a really smart guy.
But, here's a small correction.
What piece of ticket/request/issue/bug tracking software allows more than 1 person to be assigned to anything?
The championing of "1 person assignment" with FogBugz probably comes from Joel seeing software projects managed with MS Project, where you can assign an infinite amount of people to any task. Unless FogBugz was the first ticket tracking app on the planet, I can't see how they "revolutionized" anything.
In his post, Starting over with customer service, credits Fog Creek Software's, FobBugz with "accidentally revolutionized a huge piece of management", in regards to the software's ability to only allow a single person to own a single issue (or bug).
Seth's got an awesome blog, and seems to be a really smart guy.
But, here's a small correction.
What piece of ticket/request/issue/bug tracking software allows more than 1 person to be assigned to anything?
The championing of "1 person assignment" with FogBugz probably comes from Joel seeing software projects managed with MS Project, where you can assign an infinite amount of people to any task. Unless FogBugz was the first ticket tracking app on the planet, I can't see how they "revolutionized" anything.


1 Comments:
I think what he's referring to is that, in FogBugz, tasks must always be assigned to exactly one person, in contrast to most bug trackers, where bugs frequently default to being assigned to no one. If you go to WebKit's Bugzilla, for example (http://bugs.webkit.org/), you can see unassigned bugs by looking for those assigned to "NEW." FogBugz prevents anyone from passing the buck this way, instead ensuring that someone, somewhere, is always responsible.
Post a Comment
<< Home