Re: Documenting A Moving Target

Subject: Re: Documenting A Moving Target
From: Eric -dot- Ray -at- WCOM -dot- COM
Date: Wed, 21 Feb 1996 10:45:40 PST

On Tue, 20 Feb 1996 16:16:51 EDT Karen Gwynn/Datatel wrote:

>Problem: I am trying to document a product that is still being
>developed, not just tweaked. By this I mean, something that I documented
>on January 31, now works differently.
>HELP! What do other people do? Do other software companies build in time
>Any advice (or job offers) is appreciated!!

Yup! In addition to the other suggestions offered (build in two
weeks lag for you, don't try to keep up on an ongoing basis, and
implement change control procedures), get yourself wired into the
loop. You'll find that there are people in your organization who,
for whatever reason, tend to just KNOW what's changing when and
how critical that will be. They will also be able to tell you
when the series of changes in a specific set of screens ceases,
so you'll be able to start into them again. How to find these people?
Good question. It depends on your organization. Just start talking
to people about the project you're on and wait for them to start
offering information.

You'll never get past the moving target problem, but you need to put
the responsibility for keeping you adequately informed on your
developers (or their management, if necessary).


Eric J. Ray | Eric -dot- Ray -at- wcom -dot- com
WorldCom, Inc. | W: 918-590-4140
1 Williams Center 29-5 | F: 918-590-2372
Tulsa, Oklahoma 74172 | P: 918-690-1314

Previous by Author: FW: Job posting for techwr-l (Mass.)
Next by Author: Re: Moving Target , Part 2
Previous by Thread: Re: Documenting A Moving Target
Next by Thread: Re: Documenting A Moving Target

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

Sponsored Ads

Sponsored Ads