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.
Correction... Documentation requirements are determined by the *product* -- software is one component of the product. The overall relationship with the customer is part of the calculation. But this is academic. The question here is, how does the project specify doc requirements? Agile has has its own protocol, and tech writers have to negotiate within it.
> What documentation is required is dictated by the software. Whether
> the developers are using agile methods is irrelevant.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
