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.
> I work in a Dev team that uses the XP (Agile) development methodology.
> Given that, in XP, there is a focus on little to no documentation
> during the design/build of the software, I've been pondering how the
> Publications team can fill that gap, namely by writing as complete a
> draft as early as possible and getting buy-in from the Dev team that
> they'll use the user docs whilst developing the software.
> Sound odd?
Not to me.
Years ago, when I was running an engineering-consultation company, I did exactly what you're suggesting... Not because we were (gag) XP developers, but because most of my clients weren't trained engineers, so it was really difficult for them to write good functional specs for the products they wanted me to build.
Writing the User's Manual first, and using that as the functional spec, was VERY beneficial for all involved.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-