RE: Business Requirements

[<jan -dot- arnopolin -at- thomson -dot- com>]

I think the Business Requirements for A2 are important for the direction
of the product - map out what will happen in release 2 and the future.
BRs can also help with accountability - we want to do these 10 things,
did we accomplish them?  
On the other hand, I'm sure we've all worked at shops where there are no
business requirements, not to mention functional specs and functional
requirements.  The only spec might be technical specs for the
developers.
If this is an on-going product, take a stab at making a case for the
business requirements.  If you get shot down a second time, it sounds
like you've already gotten shot down once, let it go.  Sometimes it's
easier to go with the flow and let the higher ups live with the
consequences.
Just my opinion.
jan

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

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 & 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 & 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.