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: Making Agile work with remote resources From:"McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com> To:Kathleen MacDowell <kathleen -dot- eamd -at- gmail -dot- com> Date:Mon, 11 Jun 2012 15:32:31 -0400
> -----Original Message-----
> From: Kathleen MacDowell
> The part about Agile I really liked was the developer who kept making
> changes till 6 pm the night before we were supposed to be done. She
> was so fun to work with, especially when she changed specs w/o
> communicating to anyone, including the project manager. Snap!
Doesn't the ProDUCT Manager own the User Stories for the product, and therefore decide if a sprint is succeeding, or not?
Or do you work for one of those organizations that don't want to make the stories TOO specific, for fear of cramping the style of those free-wheeling developers?
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
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.