Re: Business Requirements

["Gene Kim-Eng" <techwr -at- genek -dot- com>]

So do you work for one or the other of these departments,
or are you just on the outside looking in?  If you report to
the group that says it requires it, just write it and make it 
the introductory chapters of the product's functional spec,
or whatever the first requirements doc that department
has ownership of.

Gene Kim-Eng


----- Original Message ----- 
From: "James Barrow" <vrfour -at- verizon -dot- net>

> Again, in a circumstance in which a tech writer was trying to push best
> practices this would be a good rule, but this isn't my case.
> 
> Specifically, I'm talking about a Project Management Office saying "We don't
> need no stinking requirements" and an Architecture Department saying "We
> can't build it without requirements."  Even more specifically, the
> Architecture Department cannot measure nor report any successes (milestones)
> without the requirements.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create HTML or Microsoft Word content and convert to Help file formats or 
printed documentation. Features include support for Windows Vista & 2007 
Microsoft Office, team authoring, plus more.
http://www.DocToHelp.com/TechwrlList

Now shipping: Help &amp; Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help &amp; Manual: http://www.helpandmanual.com

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to 
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/ for more resources and info.