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.
The advantage of having a doc story in the tracking system is that you
can assign tasks to engineers to check the docs, and they have to
complete them before the end of the sprint.
In my last job I always sized my doc stories as zero points, unless
there was a significant development component, such as the code
changes required when we switched from RoboHelp to WebWorks.
On Fri, Oct 11, 2013 at 1:01 AM, Jen <jennee -at- gmail -dot- com> wrote:
> My former company wasn't doing Agile very well, I suppose, so there were a
> few hitches.
>
> Tech writers were invited to scrum meetings, but doc tasks weren't tracked
> anywhere and the writers usually weren't asked for a status. ...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
New! Doc-to-Help 2013 features the industry's first HTML5 editor for authoring.
