Extreme Programming / Agile Development and documentation - Continued

["HSC Italian" <twins398 -at- hotmail -dot- com>]

Hello,

I want to thank everyone who responded to my initial post. All the feedback 
was very helpful. From the feedback I received I've summed up that User 
Stories and/or Use Cases should house what a requirement spec used to house. 
Is that correct? I guess I'm still lost as to where Documentation comes in. 
How am I to gather data when there is no written spec identifyng the changes 
to the product? The User Stories for this project are far from being 
comprehensive. They are a bunch of scribble the developers came up with that 
make sense to them only.

When the project I am working on initially started the developers and 
Product Manager told me all I'd need to document this firmware project to 
operate printers would be available on the Wiki pages. I learned that was 
false. In the iteration meetings as I gathered my data and asked questions I 
was always directed to either a document on of the developers or product 
managers wrote on this product or I was told to talk to one of my SMEs. I 
did just that. Now I am being told I (the tech writer who is on five 
projects at the moment, need to be the SME). YIKES! Not possible!

I am very frustrated and need to get facts to show management that this 
method of working was created for developers, not TechPubs/Documentation.  I 
need to propose a solution to the problem I see with this process and hope 
that someone out there and guide me to some resources I can go to to gather 
facts and offer a solution. I am working with one of our quality engineers 
who is confirming that this method does not work for techpubs, but if I 
could get articles, Web sites, books, something that supports my concerns 
and offers a solution, that would be fantastic.

Thanks much,

Heidi


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

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.