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.
There are so few software projects that conform to timelines anyway. Do you
think they will realistically have the product finished so that your work
will be required in that four weeks, or will this discussion of requiring it
in four weeks soon be moot?
I was once working on a job where there was an amazingly close deadline to
finish a huge manual. I was worried because the product was nowhere close to
finished, and thus hard to document. Another more experienced person on the
software project did not seem at all concerned. Since I had just started
working there, I didn't realize how artificial the deadline was. The product
still was not complete, eight months later.
Lois Patterson
Sharon wrote:
| I am looking for a reality check. The client seems
| immovable about the 4 weeks.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Attention ForeHelp and Doc-to-Help Users! Upgrade your existing product to
RoboHelp for only $299, through January 31st. RoboHelp can import your
existing Help projects! Learn how else RoboHelp can benefit you. www.ehelp.com/techwr
---
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.
