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.
Agile really only released programmers from the onerous duty of producing thorough and accurate design documents. My experience has shown that they rarely update any design document and expect osmosis to fill in the rest.
That may seem unfair, but I have yet to see implementation of Agile as described in books.
Scott T.
> On Feb 5, 2015, at 11:03, Robert Lauriston <robert -at- lauriston -dot- com> wrote:
>
> Writing docs based on specifications is a good way to get out of sync
> with the product, but use cases as I know them are nothing like specs.
> They're short descriptions of what customers would do with specific
> features of the product.
>
>> On Wed, Feb 4, 2015 at 6:26 PM, Keith Hood <klhra -at- yahoo -dot- com> wrote:
>>
>> The idea of basing documentation on use cases makes me nervous. It tells me the development team wants the docs written with only the use cases for source material. But there are ALWAYS gaps, bugs, shortfalls, and just plain mistakes between developing the use cases and cutting the gold master. There will be changes to the design that the technical writer will never know about until he sees the product itself, because the developers will all be too busy hunting bugs, or (happens all too often) they don't consider the tech writer really part of the team and they forgot he's there. Basing product documentation on any kind of design paper instead of basing it on looking at the actual product itself is nothing but a guarantee of documentation that is incomplete and out of phase with reality.There has never been an end-result product that actually works the way the design documents say it should, and I'll bet my entire next month's pay there never will be.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as quills -at- airmail -dot- net -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
>
> Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Doc-To-Help: The Quickest Way to Author and Publish Online Help, Policy & Procedure Guides, eBooks, and more using Microsoft Word | http://bit.ly/doctohelp2015
