How to implement QA time estimate in a simple manner

We held a discussion regarding the difficulties encountered by QAs. One of the identified issues that usually affects the team as a whole is that the rest of the team (specially the developers) are somehow "blind" when it comes to the complexity and/or amount of time that the QAs might be needing for a certain issue to be extensively tested. This is due to the fact that the estimation of story points are based on the developer's intuition and in turn partially disregards QA's perspective.

As such, QAs are proposing to have some sort of a "QA time estimate" on each JIRA issue so that the team would be better equipped with information as to the amount of time that the issue will consume for testing. This will also help us as a guide in identifying "issues (or story points) versus time remaining" in a certain sprint.

This can of course be done by just adding an additional field and add either story points for QA, time estimates or just enable it as a dropdown with default values. Or is there any other way?

2 answers

1 accepted

1 vote
Accepted answer

I'd be strongly tempted to create a sub-task type of QA and then use the timetracking in there. It'll roll up to the main issue and remain independent of the development work.

I guess I would have to estimate them in hours instead of story points to avoid them having an impact on the dev. burndown..?

Nice idea. And then estimate as "usual".

The issue sub-type is mostly a really useful construct here - your QA people can easily run filters for "QA stuff only", and your developers can ignore them :-) It also frees you up to have a different workflow and fields on QA items if you want. The only downside is remembering to create them...

Nice Idea Nic & Ivar

If I have an Enhancement, I want to promote it from BA-->Dev-->QA-->UAT and have a way to have 4 different time estimates and 4 ways to record time against the same issue while having them roll up to a single number. Adding 4 different subtasks to this single issue vastly overcomplicates what should be the standard SDLC scenario.

Please vote for this ticket which addresses this: https://jira.atlassian.com/browse/JRA-872

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,723 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you