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: Using jira for documentation development workflows
Subject:RE: Using jira for documentation development workflows From:"McLauchlan, Kevin" <Kevin -dot- McLauchlan -at- safenet-inc -dot- com> To:John G <john -at- garisons -dot- com>, "shawn -at- cohodata -dot- com" <shawn -at- cohodata -dot- com> Date:Mon, 14 Jul 2014 09:26:21 -0400
I blinked when I saw âzero fibâ. Zero is zero, after all. Only in cosmology are there degrees of none-ness... :-)
OK, maybe some obscure branch of philosophy.
Some of our groups use the Fibonacci numbered cards for Agile poker/voting, but thereafter we just refer to the effort estimates as... estimates or, in our more truthful moments, as SWAGs.
Hmm. Perhaps at the next wild-ass guestimation session, Iâll hold up a card representing quantum vacuum fluctuation... er.... ah.... wait on that...
From: vwritert -at- gmail -dot- com [mailto:vwritert -at- gmail -dot- com] On Behalf Of John G
Sent: July-12-14 9:13 PM
To: shawn -at- cohodata -dot- com
Cc: McLauchlan, Kevin; techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Using jira for documentation development workflows
We have a documentation epic as part of all our products' releases, and I create doc stories and assign subtasks to developers, product managers, etc. The beauty of this approach is that my stories are zero fib and don't affect the team velocity if they carry over from one sprint to the next.
We use this to hand off links to confluence files for our translators too.
When there's a development task that has a doc/ui/ux element to it, they check the box on the story for "Affects documentation" and I can run a script to scoop those up.
Works well with minimal impact ... for us.
On Fri, Jul 11, 2014 at 4:04 PM, Shawn <shawn -at- cohodata -dot- com<mailto:shawn -at- cohodata -dot- com>> wrote:
Kevin (et al),
I noticed that you mentioned "Jira" and "documentation" in a single
thought. Kind of a rarity, it seems.
I changed the subject so that I am not hijacking the other thread. :)
Being the sole tech writer in a hard-core Linux engineering team, Jira is
pretty central to all the development work here. Unfortunately, the current
Jira configuration doesn't really meet my documentation workflow
requirements. Additionally, I have found very little about this subject on
Can you/anyone offer advice (or web URLs) on how best to use Jira for
On Mon, Jun 23, 2014 at 12:00 PM, McLauchlan, Kevin <
Kevin -dot- McLauchlan -at- safenet-inc -dot- com<mailto:Kevin -dot- McLauchlan -at- safenet-inc -dot- com>> wrote:
> Starting from a history of waterfall-ish development, and after more than
> two years in-progress, we are in water-agile-fall(**), trying to get to
> agile, and one outcome of that is that EVERY new thing I add to the docs is
> supposed to be captured as some kind of Jira issue (story, bug, task...).
> So, I never used to ask permission, and now I still don't, directly, but
> the indirect effect is that that's how it now works.
> I have (as we say around here) a whack of issues in my backlog that aren't
> assigned to any sprint, that aren't supposed to be implemented unless I've
> got nothing to do. That doesn't happen, of course.
> In reality, they'll get snuck into a DOC sprint that we writers are
> assigning to ourselves, packed among structural and other sanctioned
> stories and issues. But I thought I'd check which way the winds blow for
> the rest of y'all*. :-)
> (*I'm not southern - I just like to say "y'all" sometimes)
> (**actually, some product teams, here, are frighteningly agile, while
> others are still getting onboard - I'm in two that are at different places
> along that spectrum; if I had rhythm, you could call what I do "dancing"...
> but no )
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.
Read about how Georgia System Operation Corporation improved teamwork, communication, and efficiency using Doc-To-Help | http://bit.ly/1lRPd2l