RE: I'm now blogging about Agile & TW

["Ed" <hamonwry12 -at- hotmail -dot- com>]

I actually agree with Robert on this one. From the bit I read on Wikipedia,
it sounds like a buzzword-filled methodology forced on a group of people
that doesn't solve most people's problems. 

Kind of like DITA.

How does anything get done in four weeks when there's "extensive planning"?
And how extensive can planning be when it doesn't look long-term? Isn't that
a bit dangerous?

Also, a "manifesto" that's centered and laid out like a poem kind of
frightens me.

-=Ed.

> -----Original Message-----
> From: techwr-l-bounces+hamonwry12=hotmail -dot- com -at- lists -dot- techwr-l -dot- com
> [mailto:techwr-l-bounces+hamonwry12=hotmail -dot- com -at- lists -dot- techwr-l -dot- com] On
Behalf
> Of Marguerite Krupp
> Sent: Wednesday, December 02, 2009 1:21 PM
> To: TECHWR-L Writing; Robert Lauriston
> Subject: Re: I'm now blogging about Agile & TW
> 
> For the intellectually curious, or those just willing to keep an open mind
> about how we do our jobs (or, for that matter, who want to keep themselves
> marketable), consider reading the following resources:
> 
> www.agilemanifesto.org (The "project documentation" referred to means
specs.)
> 
> http://en.wikipedia.org/wiki/Agile_software_development
> 
> Obviously, there are issues as well as advantages in applying a software
> development methodology to documentation. Agile methodologies (there are
> several) have been around for 10 years that I know of. They don't work
well
> for all projects or for all people, but they're out there, and wise tech
> writers will at least familiarize themselves with the concepts. I'm not an
> advocate; I'm a learner. There are tech writing jobs out there using Agile
> methodologies. If you choose not to use the tools, that's OK, but know
what
> you're accepting or rejecting.
> 
> If you think of the Agile doc modules as building blocks, not as a
> "disorganized mess," you'll see how you can use them to create
documentation.
> Key Agile tenets, BTW,
> include extensive planning, generation of user stories (who will use this
> stuff how), and a high degree of granularity of material. But go look for
> yourself and then decide whether it works for you. Julie has given us a
good
> start.
> 
> Marguerite


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

Are you looking for one documentation tool that does it all? Author, 
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at:
http://www.doctohelp.com/ 

Help & Manual 5: The all-in-one help authoring tool. True single- sourcing -- 
generate 8 different formats and as many different versions as you need 
from just one project. Fast and intuitive.  http://www.helpandmanual.com/

---
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-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

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

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat