Re: Agile, Jira tickets, and document planning

Subject: Re: Agile, Jira tickets, and document planning
From: Jonathan Baker <jbaker2525 -at- gmail -dot- com>
To: Stuart Conner <stuart2 -at- stuartconner -dot- me -dot- uk>
Date: Tue, 3 Apr 2018 16:40:26 -0400

Yup. I've had first hand experience with each option. Options 2 or 3 are
the better options. Option 1 is guaranteed to fail. Personally, I'd always
choose Option 3, since it seems to be the most flexible. But, there has to
be an understanding that you will run behind the development release
schedule.

On Tue, Apr 3, 2018 at 3:01 PM, Stuart Conner <stuart2 -at- stuartconner -dot- me -dot- uk>
wrote:

> I'm in a new job where I need to plan and produce some documentation in an
> Agile environment.
>
>
>
> I have a known number of documents to produce within the next 3 months,
> with
> each sprint being 2 weeks long. The order in which the documents are
> produced is not critical.
>
>
>
> Each document will require the following sequence of activities: (1) A
> developer SME either writes an initial draft of the document or conveys
> that
> information to me verbally, (2) I produce a good draft of the document,
> gathering further information from the SME as needed, (3) review, further
> rework and eventually sign-off. All the usual stuff.
>
>
>
> The main pain-point is going to be getting developer time to work on the
> documentation, as they have code to develop as well. We'll raise a Jira
> ticket for each document so the necessary time can be planned into each
> sprint.
>
>
>
> My question relates to the best way to track things in Jira:
>
>
>
> (1) We could say that for each sprint, the developer and I will work on
> documents A, B and C, and we raise Jira tickets for these. But doing this,
> developer time will be needed early in the sprint if he/she is to do their
> part leaving enough time for me to rework and finish the draft before the
> end of the sprint. If the developer gets tied up with other stuff during
> the
> first week of the sprint and can't look at the documentation until the
> second week, then I won't have time to complete the documents before the
> end
> of the sprint.
>
>
>
> (2) We could separate the developer's time on the documents from my time.
> So
> for each sprint, the developer will work on initial drafts for documents A,
> B and C, and I work on the drafts the developer produced in the last
> sprint.
> More flexible, more likely to finish the work scheduled for each sprint,
> but
> double the number of Jira tickets to be tracked.
>
>
>
> (3) We could say that for each sprint, the developer will work on documents
> A, B and C, but I will work 'outside' the sprints, being flexible on how I
> work on the drafts produced by the developer. I track my progress on the
> documents separately. We don't drown in Jira tickets. But to some extent
> I'm
> working outside the Agile team.
>
>
>
> Anyone been in a similar situation and have any advice on what worked for
> them?
>
>
>
> Thanks,
>
>
>
> Stuart.
>
>
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | http://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as jbaker2525 -at- gmail -dot- com -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
> http://www.techwhirl.com/email-discussion-groups/ for more resources and
> info.
>
> Looking for articles on Technical Communications? Head over to our online
> magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public
> email archives @ http://techwr-l.com/archives
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives


Follow-Ups:

References:
Agile, Jira tickets, and document planning: From: Stuart Conner

Previous by Author: Documentation titles
Next by Author: Re: dealing with inflated ego
Previous by Thread: Agile, Jira tickets, and document planning
Next by Thread: Re: Agile, Jira tickets, and document planning


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads