Re: User Documentation in Agile Development Teams

[Robert Lauriston <robert -at- lauriston -dot- com>]

Avoiding the "curse of knowledge" is one of the things writers mean
when we say, know your audience.

In software development, a problem I've seen far more often is that
developers don't really understand customers' use cases.

That's one of the advantages of agile development. If the coders make
false assumptions and build the wrong thing, someone in product
management, support, or documentation will look at it at the end of
the sprint and say, hey, guys, you're off track here. So course
corrections can be made within a few weeks.

Over time, if the sprints are long enough to allow adequate
retrospectives and planning, the team should get better at writing
acceptance criteria that ensure sure they won't get off track.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

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

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot- 

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


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

Looking for articles on Technical Communications?  Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions?  Search our public email archives @ http://techwr-l.com/archives