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.
Indeed, I think that your immediate concern is to ensure that TW won't
be relegated out of the loop. You MUST attend and participate in the
scrums. You must not let anyone shut you up just because you are "only a
tw" or because they feel your questions are "nonproductive."
The change to Agile represents a possibility for certain people to gain
control that they previously lacked. It is both a threat and an
opportunity.
The change may be anything from a fully supported approach that is
properly implemented with total approval of upper management, to a
"flavor-of-the-month" flag that will be lowered as soon as someone sees
that it's a threat to his power or someone else comes along with another
flavor.
I'd try to be aware of the political undercurrents involved.
Blount, Patricia A wrote:
>...
> I've got a few concerns... chief among them: Does tech writing fall off
> the radar in such environments? Rumor hear has it that tech writing will
> lag a sprint behind development. I think that's a bad idea because we
> typically do more than 'write'. We review GUI screens for grammar and
> sense, we suggest design improvements when instructions feel clunky, we
> can test as we write, so if we lag a sprint behind, those problems won't
> be fixed immediately (and isn't that the goal of agile?)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Use Doc-To-Help's XML-based editor, Microsoft Word, or HTML and
produce desktop, Web, or print deliverables. Just write (or import)
and Doc-To-Help does the rest. Free trial: http://www.doctohelp.com
Explore CAREER options and paths related to Technical Writing,
learn to create SOFTWARE REQUIREMENTS documents, and
get tips on FUNCTIONAL SPECIFICATION best practices. Free at: http://www.ModernAnalyst.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
