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.
Our software development team is building the software in increments.
Once certain features are ready, they will be ready for shipping. This
means the documentation has to be ready as well.
The challenges we face are:
* Due to the way the development team is building the product, we
may have to document the software by feature. However, most
documentation is provided based on use, not feature.
* We may be almost finished documenting a feature, but the feature
doesn't make it in the release because the development team is not
finished. We then have to pull it out of the documentation.
We are trying to figure out the best way to handle this. Any ideas
lingering out there? Anyone else in the same situation?
I'd appreciate any comments.
Thanks,
Shari Scheske Goodman
scheskes -at- cognos -dot- com
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-
