SDLC Stories & Story Point across multiple disciplines (Dev & QA)

Question

Good Day,

I am wondering how others use JIRA tickets & Story points to track burndown in a sprint.

My organization creates a Story and comes up w/ and estimate based on the LOE agreed on by development (web & backend) and QA. The challenge is that the Story often will be in more than one sprint as the development is completed and then the testing takes place.

This makes the sprint burndowns always end with story points not completed and sprints always having a higher initiated work than completed.

Have others run into this challenge and if so what is you approach to try and avoid so many stories spanning multiple sprints?

Appreciate any feedback.

~Jim

James Gould_3cuq4p · Answer

@Danut M _StonikByte_You are a scholar and a gentleman, much appreciated.

~Jim

Danut M _StonikByte_ · Answer

Hi @James Gould,

I could offer these details in a private discussion.

Perhaps the via the LinkedIn chat. Please sent me an invite.

Danut Manda

James Gould_3cuq4p · Answer

Thanks @Danut M _StonikByte_

Appreciate that.

If you dont mind me asking, do you have a single team or multiple teams?

How big are the teams?

Are you running 2,3,or 4 week sprints?

Full stack developers or discipline specific developers (Web/Back End)?

Do developers help test(beyond unit), dont pick up another ticket until the one being tested is done/done, or do they move to the next priority ticket in the sprint?

If they move on how do you avoid the waterfall effect?

If they dont move on does that impact the team throughput (developers not developing)?

How often do your teams deploy to production?

~Jim