Re: Agile programming and tech comm

[Tony Markos <ajmarkos -at- yahoo -dot- com>]

Ronald:

I have lead requirements engineering efforts on an
agile development project.  It means forget the fluff
and peripheral and get wright to the essential. 
(Typically, only a small percentage of requirements
are essential.) 

If you are working on documenting requirements, create
an essential data flow diagram, and then use that to
plan any supplemental text-based documentation.

If you are creating end-user documentation, I suggest
a simular approach (but you don't have to be as
rigorous).

Tony "Focused On The Essential Like A Laser" Markos

--- Ronald Sering <ron_sering -at- yahoo -dot- com> wrote:

> 
> I am working in a shop that uses the Agile
> methodology, and recently ran across this item from
> the Agile Manifesto:
> 
> [The agile methodology favors] "Working software
> over
> comprehensive documentation."
> 
> Now, this sounds a little alarming, being the lone
> writer in charge of documentation. Can anyone
> elaborate on this, and maybe share your experiences
> working in an agile environment?
> 
> Thanks,
> 
> Ron Sering
> 



		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - now with 250MB free storage. Learn more.
http://info.mail.yahoo.com/mail_250

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

WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:
http://www.webworks.com/techwr-l

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.