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:"Weissman, Jessica R" <WeissmanJR -at- state -dot- gov> To:Sue McKinney <smckinn2001 -at- gmail -dot- com>, "techwr-l -at- lists -dot- techwr-l -dot- com" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 24 Mar 2017 14:53:48 +0000
Why would they think that Agile development methods would change user needs?
As you say, back end docs can be leaner, but there's nothing about Agile that makes software more intuitive to users. Well, fewer systems are developed from beginning to end without user involvement, so wildly unintuitive designs don't get locked in as early.
Developers are not qualified to say what is intuitive, and tech writers who have become familiar with a product or system are not as qualified as they were at the start of their involvement with the project.
Jessica Weissman
Senior Technical Writer
ValidaTek, Inc.
U.S. Department of State | Bureau of Consular Affairs
(M) (301) 775-1269 | weissmanjr -at- state -dot- gov
Providing innovative solutions through collaboration, accountability and excellence
Personal
UNCLASSIFIED
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com
