TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
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
