Re: Agile, SCRUM and Technical Writing

Subject: Re: Agile, SCRUM and Technical Writing
From: "Gene Kim-Eng" <techwr -at- genek -dot- com>
To: "Gillespie, Terilyn" <Terilyn -dot- Gillespie -at- ddiworld -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 16 Feb 2007 10:09:32 -0800

All document projects have a certain element of "just in time," especially where software that does not require CDs and retail
packaging to go to market is concerned. Even in the best of
development efforts, there is always some last-minute eruption
of Murphy's law.

As for the studies, I can see how having "detailed requirements
documents early in a project," and "change management procedures" can seem like "a leading cause of failure." When
requirements are documented it is much easier for a customer or the development team's management to recognize that the product has failed to meet them.
Likewise, if the product development process is a poorly managed,
"make it up as we go" variety of chaos.whose end result hardly ever conforms to its design models, then those models do indeed become irrelevant to the success of the product.

One of the reasons why the people involved in poorly managed development environments are often resistant to attempts to document their requirements, processes, workflows, etc., is that not documenting these things makes it easier to gloss over the fact that they don't have any that make any sense in the first place.

Gene Kim-Eng

----- Original Message ----- From: "Gillespie, Terilyn" <Terilyn -dot- Gillespie -at- ddiworld -dot- com>

I have read a few articles that promote the "just in time" documentation
philosophy, going as far to say that comprehensive requirements and
functional specification are over kill, and that creating and
maintaining these documents can overburden a software development
project. Scott Ambler, from tells us: "One study
found that the creation of detailed requirements documents early in a
project and the change management procedures associated with doing so is
the leading cause of failure on IT projects. Another study found that
the creation of detailed design models had no effect on the success of a
software development."


Create HTML or Microsoft Word content and convert to Help file formats or printed documentation. Features include single source authoring, team authoring,
Web-based technology, and PDF output.

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


Agile, SCRUM and Technical Writing: From: Gillespie, Terilyn

Previous by Author: Re: When you hear the Axe in the dark...
Next by Author: Re: Writing test Fridays
Previous by Thread: Re: Agile, SCRUM and Technical Writing
Next by Thread: Re: Agile, SCRUM and Technical Writing

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

Sponsored Ads