Re: Bug Tracks

Subject: Re: Bug Tracks
From: Robert Plamondon <robert -at- PLAMONDON -dot- COM>
Date: Sat, 5 Apr 1997 07:21:31 PST

I worked at a company that created and discarded about a dozen bug-tracking
databases. A succession of managers arrived at the fixed notion that,
with the right software, the problemof bug tracking would be a snap.

In fact, tracking such things is very labor-intensive, and the central
requirement is to assign someone the task of tracking the bugs, and to
allot vast amounts of time for it.

The software is almost irrelevant. Our best efforts happened with the
aid of a hideous database program written in FORTRAN, which was probably
less productive than chiseling the information into marble slabs. But
the project was taken very seriously, and dealing with bugs was one
of the central activities of the design team -- not something that
people hid from or brushed off. And a very committed person spend
enormous amounts of time doing the intelligence gathering that bug
tracking requires.

-- Robert
--
Robert Plamondon, High-Tech Technical Writing, Inc.
36475 Norton Creek Road * Blodgett * Oregon * 97326
robert -at- plamondon -dot- com * (541) 453-5841 * Fax: (541) 453-4139
http://www.pioneer.net/~robertp

TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html


Previous by Author: Re: Printing and incomplete manual
Next by Author: Re: TECHWR-L Digest - 6 Apr 1997 to 7 Apr 1997
Previous by Thread: IT Trainer/Writer Sought- Geneva - Switzerland - Corporate IT System
Next by Thread: Culture change & growing pains!


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads