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: Moving Target, Part 2 From:"Colleen Dancer (02) 333-1862" <DANCER -dot- COLLEEN -at- A2 -dot- ABC -dot- NET -dot- AU> Date:Thu, 22 Feb 1996 11:45:00 +1100
Two suggestions:
1. In some of our newer gui projects a developer cannot consider their
code "task" complete until a Business Analyst (ie techwhirler) has
signed it off. This is the person doing the doco and interface design.
Consequently they can't report it as finished until we have signed it so
we usually know what is going on.
2. ALso our developers are really good and consider us as part of the
team, I find my job is possible even with our timelines if I am
considered part of the team, but if not it comes more under the miracle
type of project. That is it will be a miracle if it comes in on time and
on budget.
Re: Databases
We have our own databases usually, with a nifty rollback feature, so that
you can change it and then go back to your original if wished. This is
usually the database for training. I tend to only try and create one
only.
Colleen Dancer
dancer -dot- colleen -at- a2 -dot- abc -dot- net -dot- au
