Tracking Estimations for PM, Development and QA in JIRA software

[Kavita Sarma]

We use JIRA software and we are about a medium sized company. The ticket moves from the backlog to the scrum board for a product owner to work on it. Product owners estimate in Story points and we use that field to fill in the story points estimates. We also need to estimate developer time and QA time. We use the original estimate for developer time but there is no place to track QA time. Would love to hear options and thoughts on how others are tracking level of effort for PM, Development and QA within JIRA. Thanks.

[Libu B]

Hi Kavita,

Couple of comments on this. 

1. Typically, we move and issue from the backlog to scrum board for the team to work on during a sprint . This is usually done in the Sprint planning. Product Owner's job is mainly around firming up the issue, providing more clarity on requirements etc before the sprint starts( the issue sits in the backlog during this time). Having said that, PO provide ongoing support during the sprint ( clarifications, reviews etc) 
2. Estimates on story ( storypoints) is the overall estimate for that story to complete ( meeting the definition of done). We dont put individual estimates ( dev,test,PM etc) in the story. You can create sub-tasks within a story and have individual estimates in subtasks. eg - a sub-task for developement, a sub task for testing etc. 

Hope this helps.

Cheers,

Libu

[Kavita Sarma]

Thanks for the reply. It does help some. We do the same thing - moving the issue from the backlog to the scrum board and then we move it into the developers queue once its done in the sprint. We don't create separate QA tickets. Perhaps we need to consider that. 

[Sunit]

@Kavita Sarma  were you able to to solve the problem would love to hear from you on this. I am trying to setup the same using a custom field for qa estimation.

[Celine Hau]

@Libu B the subtask idea is perfect for tracking QA time. thanks!