Re: Agile Epics & Stories & TechPubs

[Charlotte Claussen <charlotteclaussen -at- gmail -dot- com>]

I think that depends on the dev team you work with. I have worked with
engineers who were very good at filtering information and providing exactly
the information I needed. I have also worked with teams that ignored all
checkboxes (and all agreed processes), and I have worked with some who did
their best but found it difficult to determine which stories required docs
work.

One thing you need to know about agile is that there are almost as many
opinions of what agile is, or should be, as there are engineers. Your best
bet is to figure out how the engineers are working in your organisation and
then decide how you can work around that.

Feel free to reach out to me 1:1 if you want to have a chat about your
specific situation. I don't have all the answers, but I've worked in
different agile environments and made my own mistakes :)

/Charlotte

On Fri, 26 Mar 2021 at 13:01, John G <vwritert -at- gmail -dot- com> wrote:

> One of the additions we made to our Agile tracking software (we use Jira)
> was to add a "Requires change to user documentation " checkbox for epics
> and stories. It certainly helps us find things we need to track.
>
> I'm doing a session at the STC Summit on Making Agile Work for You FWIW.
>
> Carla - I think I remember you from DDI back in the day ...
>
>
> JG
>
> On Fri, Mar 26, 2021, 8:53 AM Annette Reilly <annetterieee -at- gmail -dot- com>
> wrote:
>
> > For comprehensive guidance on information development in agile teams, see
> > ISO/IEC/IEEE 26515 https://ieeexplore.ieee.org/document/6170923
> >
> > For advice on developing an information plan, see ISO/IEC/IEEE 26511 ,
> > https://ieeexplore.ieee.org/document/8584518
> >
> > Yes, you would need to pay for these, but compare the cost to the hours
> or
> > weeks of staff time it would take to get up to speed on this.
> >
> > But I think your question is really, what epics/ stories are being
> > developed
> > for the product and need to be worked into the stories assigned to the
> > information developer, either in parallel with the product developers,
> or a
> > sprint or two behind their work. So your team member needs to be working
> > closely with the project team during the initial planning (Sprint zero).
> >
> > That is quite a sizable body of work for one person. Is that typical for
> > your team? Do you have content management to reuse material (embedding
> > videos in user guides for example).
> >
> > Good luck,
> >
> >
> >
> >
> >
> > -----Original Message-----
> > From: Martinek, Carla <CMartinek -at- zebra -dot- com>
> > Sent: Thursday, March 25, 2021 2:37 PM
> > To: TechWhirl (techwr-l -at- lists -dot- techwr-l -dot- com) <techwr-l -at- lists -dot- techwr-l -dot- com
> >
> > Subject: Agile Epics & Stories & TechPubs
> >
> >
> >
> > It's happened. We're finally getting entire projects developing through
> > Agile (software has been doing it for a while, but most of what my team
> > supports is hardware). In the very first project we're working with, one
> of
> > my coworkers is expected to create Epics and Stories for a project. Known
> > deliverables are 4 user guides, 2 quick start guides, 2 regulatory
> guides,
> > and a dozen or so videos.
> >
> >
> >
> > While we've had an intro to the Agile Framework, this is one of those
> areas
> > where it's really hard to know what to do until you've done it at least
> > once. We need some handholding references on how we should proceed and
> > break
> > the deliverables down. Can anyone recommend some good sources to go to?
> >
> >
> >
> > Thx
> >
> > Carla
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ________________________________
> >
> > - CONFIDENTIAL-
> >
> >
> >
> > This email and any files transmitted with it are confidential, and may
> also
> > be legally privileged. If you are not the intended recipient, you may not
> > review, use, copy, or distribute this message. If you receive this email
> in
> > error, please notify the sender immediately by reply email and then
> delete
> > this email.
> >
> >
> >
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > Visit TechWhirl for the latest on content technology, content strategy
> and
> > content development | https://techwhirl.com
> >
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > You are currently subscribed to TECHWR-L as vwritert -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 | https://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as charlotteclaussen -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 | https://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