TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:OT: Bugs and changes record keeping From:"Halter, Meg" <HalterMC -at- navair -dot- navy -dot- mil> To:"'Techwr-L Listerv'" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Fri, 3 Dec 1999 10:11:07 -0800
Hello, oh wise ones --
This is a bit off topic, but perhaps you can help.
We're developing a program at an ever-accelerating pace. As I'm documenting
(and developing) I've been keeping a list of things to change when we catch
our breath. We really need something more formal than my little piece of
paper with handwritten notes tucked in the back of my logbook, especially
since we will no doubt be dealing with bugs found by users shortly after
this is released.
Do you folks have suggestions for a way to keep track of problems,
suggestions and plain nice-to-have changes? Any lessons learned? I'm looking
for a system that is as minimalist as possible, that doesn't turn into a
full time job by itself.
