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: The Agile / Xtreme TW From:John Posada <jposada99 -at- gmail -dot- com> To:Michael West <WestM -at- conwag -dot- com> Date:Tue, 10 Feb 2009 13:53:25 -0500
>>My slight experience with agile-like development has suffered from some
>>of the usual diseases that keep the writer out of the loop.
Having worked in, and having managed some writing projects within an
Agile team environment, all I can say to address this issue is:
Be more of a pain to the team by being outside than you would be if
you were on the inside.
- Be at every scrum that you can be, even if you aren't invited.
- Act like you are in the loop even if they don't think you are. That
includes doing everything you would do if you were in the loop. Don't
wait to be invited. Crash.
- At each planning session, submit your list of Stories and Tasks and
if they aren't incorporated, ask why. Ask why again, and again, and
again.
- Make sure that one of the development tasks is that they must
perform the review of the material that is submitted as part of that
iteration. By getitng this, they cannot close it and advance to the
next with the task still open.
- Understand when you are the pig and when you are the chicken and
respect the process.
- Do this all with all due respect until you get to the point where
your efforts are ignored, then notify the Product Manager and the
Marketing manager of your efforts and issues, and the possible impact
if you aren't included, because from a project perspective, the
success or failure of the project is their responsibility
--
John Posada
Senior Technical Writer
NYMetro STC President
Looking for the next gig.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-