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.
> How do you cope when you see your organization making very, very, basic errors?
> Like adding a major feature to a release halfway through development, without changing the schedule or personnel, with the entirely predictable result that everyone works like crazy for six months, some people quit (schedule still doesn't change), and the product as released is barely stable enough to call a beta?
Wow! You get a whole half of a project worth of padding for this???
I'm jealous! ;-)
> Or having *no* requirements defined for a project and no one in charge, so that the design phase fiddles on for an extra two months while everyone and their brother chimes in with what they consider to be an important capability, all of which get in because no one has the authority to say "no"?
Ah, yes... cats without a shepherd.
> It seems to me that the software industry, and many individual companies, have now been around long enough that there's no excuse for this. There are entire libraries of books written about how to plan a software project. Companies hold project post mortems and "lessons learned" sessions all the time. And still the same mistakes....
Post mortems and lessons learned only work when you have responsible
people in charge who are accountable for putting that type of
information to good use.
> I find this very frustrating, even when it's not a project that I'm on. I don't like the waste of time and energy, or the half-baked products, that inevitably seem to result from poor planning. What do you do to combat the problem, or the frustration?
Beer. Very, very good beer. ;-)
> It's been a long week, I'm sick, and it's Friday....
Rest, feel better, and then work for change. :-)
--
Bill Swallow
HATT List Owner
WWP-Users List Owner
42.8162,-73.7736 http://techcommdood.blogspot.com
============================
I support Char James-Tanny for STC Secretary.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Now Shipping -- WebWorks ePublisher Pro for Word! Easily create online
Help. And online anything else. Redesigned interface with a new
project-based workflow. Try it today! http://www.webworks.com/techwr-l
Doc-To-Help 2005 now has RoboHelp Converter and HTML Source: Author
content and configure Help in MS Word or any HTML editor. No
proprietary editor! *August release. http://www.componentone.com/TECHWRL/DocToHelp2005
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-
