Re: User Documentation in Agile Development Teams
In software development, a problem I've seen far more often is that developers don't really understand customers' use cases.
Yes, that's correct!! <rant-kvetch>I've worked with many teams at many companies where the engineers in particular don't have any idea how the whole flow will work, what the customers need from the product overall, and how the customer will use it. When I talk to the engineers they're often not even troubled by the fact that they don't know. They frequently say things such as, "I'm just implementing the protocol, and donât need to know how this code fits into the process." Such thinking certainly explains the lack of usability in systems!</rant-kvetch>
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
- Re: User Documentation in Agile Development Teams, John G
- Re: User Documentation in Agile Development Teams, Robert Lauriston
User Documentation in Agile Development Teams: From: Sue McKinney
RE: User Documentation in Agile Development Teams: From: mbaker
Re: User Documentation in Agile Development Teams: From: Robert Lauriston
Previous by Author:
Re: criteria for choosing tools ?
Next by Author: SourceTree (on Mac) w/Mercurial - show remote un-pulled files ?
Previous by Thread: Re: User Documentation in Agile Development Teams
Next by Thread: Re: User Documentation in Agile Development Teams
Visit TechWhirl's Other Sites