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.
> 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
I agree, which is why I think it is important to have BRs before you
can write an FS.
Where I am now, we call this a Product Requirement Document (PRD).
The one I have in front of me is a 24 page table, with each row being
either a requested customer feature or internally driven enhancement.
They are given a priority, a description of the requirement, a
comment by product mamagement on its importance, and comments by
engineering on the amount of effort to include that feature. Each one
is approved, rejected, or deferred to the next release. This document
is reviewed ALOT and documentation is at each of the reviews...this
gives us the anticipated scope of the upcoming product.
However, once they are at the point where they are developing, our
documentation is a snapshot of the application at the time it is
being written. I don't care the business reason for having a
requirement that says "Monitor the LSP end points for status
changes." If the ability gets developed, I write about it.
Once you have something to write about, BR are not nearly as
important as the FS documents, which will, in this case, tell me HOW
the application monitors LSP end point status changes.
> 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.
I tell my managers that I'll make the case once. If they decline,
I'll try once more if I feel strongly. If they decline, I won't try
again. It's one thing to feel strongly and another to be a fanatic.
John Posada
Senior Technical Writer
"They say everyone needs goals. Mine is to live forever.
So far, so good."
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-
