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: Documentation Process in an Agile environment From:"Dan Goldstein" <DGoldstein -at- riveraintech -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 17 Apr 2012 13:11:16 -0400
We use Agile within the broader context of design control under US and European medical device regulation. It is possible!
IMHO, the trick is not to get hung up too much on templates, but rather to understand what information ought to be covered by each artifact, and to be there when the document is being created to make sure it has what you need. You have to be at Sprint Planning and Review Meetings, and to get copies of other artifacts - Unit Testing records, Conditions of Satisfaction, etc. If you can attend the stand-ups, I recommend it, just for the sake of better understanding the artifacts later on.
-----Original Message-----
From: reshma pendse
Sent: Tuesday, April 17, 2012 12:30 PM
To: TECHWR-L
Subject: Documentation Process in an Agile environment
We've recently adopted Scrum as our company-wide development framework, and are trying to define a documentation process that will fit into this environment. I'm sure several people on this list already work in Agile, so I'm looking for information on how you manage the doc process in Scrum. We have excellent Doc Plan and Content Plan/ content spec templates that we used before, but I feel they are too elaborate and rigid for Agile.
What process do you follow for doc and what are the tools/templates you use for planning, scheduling, estimating? Any insights on this are much appreciated.
This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.