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.
"Richard L Hamilton" <dick -at- rlhamilton -dot- net> writes:
> Right, and every Agile methodology I've looked at brings
> documentation into the fold (or at least pays lip service
> to doing so). I'm most familiar with Scrum, which if done
> right should have documentation in the backlog for every
> sprint, and should have documentation present at the daily
> scrum meeting.
We do Scrum here, and our new ScrumMaster has introduced the concept of
"definition of done," a list of conditions that are assumed to be
required to be met even if not explicitly stated by the product owner.
Documentation (if necessary) is one of these. We have these posted on
the wall in our team room to keep them in mind as we task out user
stories.
As a result, stories that need documentation always end up with a
documentation task attached to them. There are also stories that are
entirely documentation from time to time that aren't tied to any
specific development story (especially in the SDK product, which I work
on -- the product owner is very interested in ongoing documentation
improvements).
I am considered a full-fledged member of the Scrum team (a "pig"). I
participate in our planning activities and give status at our daily
standups. Our other TW is also a member of the Scrum teams for the
products she works on.
I have worked at an organization that did XP in the past, and it was
much the same way.
--
Jerry Kindall, SDK Technical Writer
Tecplot, Inc. | Enjoy the View
Bellevue, Washington, USA
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals. http://www.doctohelp.com
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
