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.
One of the perennial problems... The following won't help with the problem,
but it might help you in putting up with it...
Wally Glassett
Software Development Process
> >
> >
> > 1. Order T-shirts for the Development team.
> >
> > 2. Announce availability.
> >
> > 3. Write the code.
> >
> > 4. Write the manual.
> >
> > 5. Hire a Product Manager.
> >
> > 6. Spec the software. (Writing the specs after the code helps
to ensure that the software meets the specifications.)
> >
> > 7. Ship.
> >
> > 8. Test the software. (The customers are a big help here.)
> >
> > 9. Identify bugs as potential enhancements.
> >
> > 10. Announce the upgrade program
