Re: User Documentation in Agile Development Teams

Subject: Re: User Documentation in Agile Development Teams
From: Robert Lauriston <robert -at- lauriston -dot- com>
To: TECHWR-L Writing <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Mon, 27 Mar 2017 10:56:25 -0700

In an agile environment, it's the product owner's responsibility to
make sure acceptance criteria reflect real-world customer
requirements.

Somebody who got a degree in computer science and has never worked as
anything other than a programmer isn't likely to have much insight
into what goes on in a bank, insurance company, factory floor, etc.,
at least not until they've been writing code for a particular market
for a few years and learn from customer feedback, support issues, bug
reports, and so on.

On Mon, Mar 27, 2017 at 9:05 AM, Monique Semp
<monique -dot- semp -at- earthlink -dot- net> wrote:
>> 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


References:
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
Re: User Documentation in Agile Development Teams: From: Monique Semp

Previous by Author: Re: User Documentation in Agile Development Teams
Next by Author: Re: Creating Secure PDFs
Previous by Thread: RE: User Documentation in Agile Development Teams
Next by Thread: Re: User Documentation in Agile Development Teams


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads