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.
Re: Technical Communicators on Software Development Teams
Subject:Re: Technical Communicators on Software Development Teams From:Tony Ioven/Voice Processing Corp <Tony_Ioven/Voice_Processing_Corp -at- VPRO -dot- COM> Date:Tue, 5 Mar 1996 09:09:30 -0600
Chuck Blessing writes . . .
>I am trying to convince my management that a technical writer needs to be on
the
>requirements development team.
For end-user products, I couldn't agree more. But be warned -- if you're going
to be involved in the design process, you may well find yourself writing the
design spec (as I currently am). Things change fast early in the process, and
this "living document" needs constant updating.
For APIs and other low-level products, I'm less enthusiastic about writers'
being involved in the design process.
