RE: Business Requirements

Subject: RE: Business Requirements
From: "James Barrow" <vrfour -at- verizon -dot- net>
To: <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 06 Apr 2007 09:31:08 -0700

I'm with the Architecture department. And, like you suggested, I included a
fairly clean matrix that listed the business requirements at the top of the
table, and the derived functional requirements at the bottom.

The problem (see "convoluted" previously) is that the PMO gathered
requirements and specs for one out of twelve facilities (user groups) and
tried to pass these requirements off as all-encompassing. When I came on
board I looked at all of the facilities and noted that the developers were
going to start work with only 1/12th of the requirements. This is when the
firestorm started. And, like a room full of kindergartners, the PMO stood
up and said, "The Architecture team is dumb. We're not playing with you any

On a personal level I have a difficult time with this. My brain wants to
see the backwards traceability of the functional requirements to the
business requirements, not FR to a project manager's whim.

- Jim

-----Original Message-----
From: Gene Kim-Eng [mailto: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
> 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
> 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.

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:

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

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 for more resources and info.


Re: Business Requirements: From: Gene Kim-Eng

Previous by Author: RE: Business Requirements
Next by Author: RE: Business Requirements
Previous by Thread: Re: Business Requirements
Next by Thread: Re: Business Requirements

What this post helpful? Share it with friends and colleagues:

Sponsored Ads