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:Re. Keeping up to date on software changes From:Geoff Hart <geoff-h -at- MTL -dot- FERIC -dot- CA> Date:Fri, 7 Apr 1995 09:29:15 LCL
The time-tested, number 1 method for keeping track of evolving
software is to be part of the design team and participate at the
meetings. Even if you're a silent attendee at the meetings, this at
least ensures that you'll know what's going on and be able to plan to
cope with it. At very least, you won't be blindsided with two days to
go until deadline. (This assumes that your developers actually plan
instead of blindly forging ahead independantly with their own "most
wanted" code features. This should be true of most commercial
projects.)
A reasonable substitute is to make sure the developers send you
regular updates (weekly?) of the changes they are making. The problem
with this is that, being human, developers will be more interested in
meeting their deadlines and producing error-free code than writing
memos to you. Still, if there is some mechanism in place that requires
such memos, it may suffice.
--Geoff Hart geoff-h -at- mtl -dot- feric -dot- ca
#8^{)}
