Re: Making Agile work with remote resources

Subject: Re: Making Agile work with remote resources
From: Julie Stickler <jstickler -at- gmail -dot- com>
To: techwr-l -at- lists -dot- techwr-l -dot- com
Date: Fri, 8 Jun 2012 10:34:59 -0400

In my experience doing Agile at four different jobs, the ones where it
was least successful were the jobs where the team was not co-located.
Agile is all about teamwork, and it is hard enough to build a good
Agile team when you're all in the same building. Having people in
different time zones adds a whole 'nother level of difficulty to the
task.

And Agile is already difficult for writers, since the model is NOT
designed with technical writers in mind. Since all of the Agile
evangelists, training, coaches, and blogs seem to either forget about
technical writers, or only mention them as an afterthought, it's all
to easy for a development team to neglect to fully integrate the
writers into the Agile team.

I'm currently struggling with a *ahem* less than optimal Agile
implementation, where our IT department has locked the writers out of
the engineering domain on the network, the ScrumMasters often forget
to invite us to meetings, and developers release code without
mentioning to the doc and training department that oh, by the way,
this is going live.

Which is not to say that Agile cannot be done well. At my last job it
was done extremely well, and I was a full member of the team, even
though I was a part-time contractor. I think it has a lot to do with
management and team buy-in to the idea of adopting Agile. If everyone
knows what the goals are, and works towards them as a team, then
things tend to go well. If it's unclear why the team is going Agile
(for example, if a manager decides it's the hot new thing so we should
be doing it) then it's harder to get everyone on board.

--
Julie Stickler
http://heratech.wordpress.com/
Blogging about Agile and technical writing

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.

http://bit.ly/doc-to-help

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


References:
Making Agile work with remote resources: From: Alison Wyld

Previous by Author: Re: Designing online help - book suggestions?
Next by Author: Re: Flare 8.1.1
Previous by Thread: Making Agile work with remote resources
Next by Thread: RE: Making Agile work with remote resources


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads