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.
Ah, I view requirements as a proactive thing and not a reactive thing.
By the time you get requirements from development, it's too late.
We get requirements right from the customer-facing folks who manage
the product positioning. Those go to engineering, and all groups
(Documentation included) review them and provide an initial scope of
effort to meet them. The product managers then nearly have a heart
attack at the level of effort, and negotiation begins. When the dust
settles, we have a refined set of requirements from which to plan all
work.
On 12/15/05, Ashaki K. Hamlett <ashaki -at- altair -dot- com> wrote:
> I thought Tara was implying to talk to SMEs and find out what they're
> developing, how they are developing it, and document that as the
> requirements. I assume she was stating to not formally annouce you are
> gathering requirements, but informally get the information you need
> through general/casual conversation. Based on that conversation, you can
> begin to (at the least) draft a requirements document. I didn't think
> she was advocating replacing formal requirements with word of mouth.
--
Bill Swallow
HATT List Owner
WWP-Users List Owner
42.8162,-73.7736 http://techcommdood.blogspot.com
============================
I support Char James-Tanny for STC Secretary.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
