Best practice for capturing Dev and QA story points

[Rajesh Kumar]

Currently I am using single story (a Jira Ticket) to capture combined effort estimate (story points), for both engineering and QA efforts. 

For example if a story needs 10 story points for Eng and 5 story points for QA, it is recorded as one story point i.e. 15, against that story.   

This is creating issues, as during sprint planning there is no way of knowing of Eng or QA resources are under allocated or over allocated. I am currently managing it, by a separate spread sheet.  Not ideal.    

Also, if eng is completed, but story gets rolled over to next sprint - this creates another complexity i.e. all of story points (in this case 15) is getting moved to next sprint. This affects team velocity.

Just wondering if its god practice to have one story - but 2 separate tasks under that i.e. one for engineering (with 10 points) and another one for QA (with 5 points)?  

That way Eng ticket can be assigned to Eng resource and QA ticket can be assigned toQA resource. That way both resource allocation and story points can be managed better. 

Please advise. 

[Ravi Sagar _Sparxsys_]

@Rajesh Kumar Yes, your thinking is good. You can create a separate task for ENG and QA. This may seem cumbersome but it will help you estimate and plan properly. Also there will be separation of duties with clear ownership.

You can also use automation to create a linked QA task from the ENG task after certain stage in the workflow (like once it is approved).

I hope it helps.

[Rajesh Kumar]

Thanks Ravi.