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.
RE: How Do You Decide How Long Things Will Take (in a SCRUM Shop)?
Subject:RE: How Do You Decide How Long Things Will Take (in a SCRUM Shop)? From:"Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com> To:<techwr-l -at- lists -dot- techwr-l -dot- com> Date:Wed, 17 Jun 2009 15:33:07 -0400
> -----Original Message-----
> From: Pro TechWriter
> Sent: Wednesday, June 17, 2009 3:17 PM
> To: Guy McDonald
> Cc: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Re: How Do You Decide How Long Things Will Take (in
> a SCRUM Shop)?
>
> ... One other idea that goes with agile is "Make it good enough;
> not perfect." That means that there may be bugs in the
> software, and there may be errors in the documentation, but
> we will make it better next time."
>
> I know agile is a shock after working other ways...
>
I've never worked at a company where the software had to be perfect to
be released.
Errors in documentation are different: There's an assumption that if you
find one, you can usually fix it quickly (unless you've already printed
15,000 manuals...). But software bugs can be judged too expensive or
time-consuming to resolve in the current build.
This message contains confidential information intended only for the use of the addressee(s). If you are not the addressee, or the person responsible for delivering it to the addressee, you are hereby notified that reading, disseminating, distributing, copying, electronic storing or the taking of any action in reliance on the contents of this message is strictly prohibited. If you have received this message by mistake, please notify us, by replying to the sender, and delete the original message immediately thereafter. Thank you.
Free Software Documentation Project Web Cast: Covers developing Table of
Contents, Context IDs, and Index, as well as Doc-To-Help
2009 tips, tricks, and best practices. http://www.doctohelp.com/SuperPages/Webcasts/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-