How to track Business Analyst work for writing user stories?

Question

We have Jira enterprise, with Portfolio add-on.

We have 6 developer teams. We use time tracking for developers to estimate their level of effort for each ticket. We would like the same set of time tracking fields to be added for "BA Time Tracking) to give us a glimpse of how long it took for Business Analysts to write the user story and how many hours did they estimated before writing it.

Do you know of a tool within Atlassian that could help us track hours (log work) for business analysts user story writing efforts?

Peter Jessen · Answer

Hi @Zena Majid,

You are very welcome. I assumed you knew it wasn't very agile, but it bore saying. :-)

It's the only solution I can think of that is relatively simply, uses your existing tools, and doesn't lead to stories spanning multiple sprints due to the BAs doing the work in sprints prior to the team consuming them.

Good look.

Regards,
Peter

Zena Majid · Answer

Thanks for your Peter!

I would like to preface by saying That when I asked the question, I absolutely recognized that the request was not the agile way of doing things. However, with the situation at work currently,  the need came up where we were instructed to report on that activity specifically.

Your solution might work to satisfy our needs, but I fear for the extra administrative burden business anaylsts will have to do to make this reportable.

Thanks again!

Peter Jessen · Answer

Hi @Zena Majid,

As a coach, I will simply state that this is a completely non-agile anti-pattern, but that is me wearing my coach hat.

A possible (EXTREMELY NON-AGILE) solution: A way to do what you are asking in Jira is to have the BAs have their own sprints parallel to the dev team. They would create, sub-task, and refine the stories in their sprints. Use the same fields as you use with the dev team.

When the stories are ready to be consumed by the dev team, clone the stories over to the dev team sprints and remove the BA-specific sub-tasks once cloned.

The BA sprints will contain stories with their hours on their sub-tasks. The dev sprints will contain stories without the BA sub-tasks and hours.

Like I said, this is extremely non-agile, but should give you what you want without messing with your dev metrics.

Regards,
Peter