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: Anybody working in "Agile" ecosystems? From:"Peter Swisher" <PeteS -at- bmgi -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Mon, 20 Jan 2003 09:55:29 -0700
John,
In addition to the questions below on the mechanics of an "agile"
software development project from a tech writers perspective, I wonder
if you could provide some insight into how successful the project was?
With everything taken into consideration, did it save the company time
and money in the end?
>From what I've read about "agile" environments, it seems the success
rate is not that good when people try to do too much in an "agile"
environment. For example, they use the generated code as a basis for
the product code.
Again, without real world experience, the better process seems to be to
go in with the understanding that you are not creating real product or
even demo-ware, but rather a visualization of what the end product
should be. The team should then set aside the "agile" generated code
and restart the dev process with proper architecting and whatnot. Is
this what your team did?
>From my real world experience as a PM and a tech writer, good planning
saves money in the end. Bug fixing is much more expensive than creating
pre1.0 code.
This is a great topic for discussion. It also may be an environment
more and more of us will face in the future. After 5 years at a company
with traditional 1 to 2 year release cycles, I am now at a company that
wants to have 3-4 month release cycles.
- Pete
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
A new book on Single Sourcing has been released by William Andrew
Publishing: _Single Sourcing: Building Modular Documentation_
is now available at: http://www.williamandrew.com/titles/1491.html.
Help Authoring Seminar 2003, coming soon to a city near you! Attend this
educational and affordable one-day seminar covering existing and emerging
trends in Help authoring technology. See http://www.ehelp.com/techwr-l2.
---
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
