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: SDLC Documentation Help Requested From:Reese <reeza -at- hawaii -dot- rr -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Sun, 27 Jan 2002 02:49:59 -1000
I'm sorry Andrew, but I've just recently signed on to this list and
I'm having trouble keeping up with the volume. So, I've been deleting
some mail unread, as a consequence I do not have Ed Manley's post and
frankly, I cannot tell where his text stops and yours begins in the
quoted email below.
Is there something you can do to differentiate between your own text
and text you are replying to? Most if not all email clients place a
mark somewhere, in the quoted text below there is a ">" in the left
hand column for example.
Sorry to be a bother, but it is in the interest of clarity in the
written word.
Reese
At 02:14 AM 1/27/2002 -0800, Andrew Plato wrote:
>"Ed Manley" wrote
>
>To echo some of Michael's comments, I don't think you have a documentation
>problem. What you described is a management or personnel problem. It
>sounds like your firm needs some key people with experience guiding and
>managing development teams. A methodology cannot take the place of solid,
>experienced management.
>
>Once you have that, then you can start to address the "how to do things."
>Creating a flurry of documents that nobody will read will only waste time
>and eat up what resources you have.
>
>As for documentation, again experience is the key. You Most programming
>and development methodologies simply do not consider documentation needs.
>Or if they do it is a periphery consideration.
>
>You might consider hiring a writer or consulting firm with experience
>developing documentation sets for rapidly growing companies. After a few
>iterations, the writer should have an established system such that you can
>swap in less experienced writers and migrate the experienced writer into
>management or slowly devolve the out source relationship.
>
>While processes you're studying are all good "templates" for establishing
>internal dev processes, the ultimate task is to take the success you have
>already had and duplicate it. The only way you'll get there is with some
>seasoned veterans who understand how to build a corporate infrastructure.
>
>Good luck.
>
>Andrew Plato
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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.
