Re: Xtreme Programming / Agile Development and Documentation

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

--- Beth Agnew <beth -dot- agnew -at- senecac -dot- on -dot- ca> wrote:

Use Cases and User Stories can be made as detailed
and comprehensive as one wants.

Tony Markos responds:

Regarding Use Cases:  You disagree with the members of
the Requirements Engineering listserv - a virtual
"who's who" in the requirements specification
industry.  Just about everyone on that listserv is
well aware of the tragic flaw of Use Cases: Weakness
in requirements elicitation (i.e., comprehensiveness).

Regarding User Stories (i.e., documenting requirements
by using written sentences).  Here Beth, you not only
disagree with the above people, but also with all
those who have developed and/or espouse requirements
modeling techniques including the UML, Structured
Systems Analysis, and a variety of others - all of
which are based on the need to move away from using
single-dimensional text to describe multi-dimensional
systems.

Tony Markos

--- Beth Agnew <beth -dot- agnew -at- senecac -dot- on -dot- ca> wrote:

> Use Cases and User Stories can be made as detailed
> and comprehensive as 
> one wants. It just depends on how much the company
> believes those 
> aspects of the process are useful. If techwriters
> are involved at the 
> earliest stage of creating user stories, they have
> the opportunity to 
> ensure the specifications contain enough
> information. It's easy enough 
> to make a good case for techwriter involvement in
> user stories, if the 
> company understands our role as user advocates.
> Programmers will only do 
> cursory user stories because they see their real
> work as coding. Having 
> the writer do the "writing" makes everyone happier.
> 



	
		
__________________________________ 
Yahoo! Mail - PC Magazine Editors' Choice 2005 
http://mail.yahoo.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l

Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author 
content and configure Help in MS Word or any HTML editor. No 
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005

---
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 http://lists.techwr-l.com/mailman/options/techwr-l/archive%40infoinfocus.com

Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.