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: The Works From:Becca <becca_price -at- yahoo -dot- com> To:tech2wr-l <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Fri, 17 Aug 2012 12:59:03 -0700 (PDT)
I would never presume to simply start a project without a good statement of work. I just was wondering what kinds of things to suggest to them so that they can better define what "the works" means to them.
> From: "jimmy -at- breck-mckye -dot- com" <jimmy -at- breck-mckye -dot- com>
>To: techwr-l -at- lists -dot- techwr-l -dot- com
>Sent: Wednesday, August 15, 2012 6:28 PM
>Subject: Re: The Works
>Ask your stakeholder, and get it signed off in a formal Statement of
>Never, ever rely only on what you "think" a client request entails -
>even if seems common sense. Similarly, get clarification on any feedback
>or requests that refer to unmeasurable criteria.
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.
Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.