We need to log the time of every team member in Jira. Today we do this by adding a QA type sub-tasks to every story, and log the time they spent on testing the issue here.
It has worked pretty good until now.
As we are in the process of moving to the new rapid boards, this becomes a challenge. Until now we have estimated sub-tasks using story points, not hours. In order to get the rapid boards to work optimal I understand that this is the way forward:
- Estimate user stories in story points
- Estimate sub-tasks in hours
However, what do we do with the QA tasks? They usually do not estimate their effort on the different user stories, so all the time they spend will lead to the fact that the majority of the estimates will "miss" as additional unestimated QA hours are added to the totals. The way I understand it, this will destroy everything.
Are there any suggestions to how we can continue to track QA time, without necessarily having to estimate the QA effort as well during sprint planning?
So we baisically ended up with this strategy:
- Team lead/Component lead estimate the issue when created in Jira. This includes expected QA effort
- During sprint planning, sub-tasks of QA time is added to the issue. One for "Create test case" and one for the actual test.
Then the QA sub-tasks are completed as ordinary work.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
I am gathering information about resources available for Atlassian product knowledge transferring for a presentation in our local Atlassian User Group. I want to group them in four categories From ...
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!
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