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.
I'm bored to death with thinking about processes but I thought I would share
my experience of the role of methodolgy in large sophisticated companies.
I worked as part of a large team of writers on a huge software project. I
was always hearing that a development methodolgy was being applied to the
project but never saw any sign of it being applied to documentation, which
was fine by me - I just got on an did some jolly good work.
After the project had been going for about 3 years and was 6 months over
deadline and way beyond any hope of ever breaking even, let alone making a
profit, meetings of developement managers were still being held to "finalise
the development methodolgy". The cost of one of these meetings would have
paid my salary for 2 years.
The project folded losing the company a fortune and my work went in the bin.
Damned fine stuff this process/methodology/.. wake me up when it's time to
go home...
