Managing Stories that are QA done but not deployed on Prod

[Raghav Rajagopal]

Hello Team,

I have a project wherein the stories are Developed and Tested within the sprint but are deployed on Prod at least a week or two after due to PO Approval UAT Testing and Production deployment process, etc. Sometimes Prod deployment happens with features developed in 2-3 sprints ( as part of a single Release)

We have another Kanban board where we track the statuses after QA.

So it goes like this:

Board 1: To Do --> In Progress --> QA --> Ready for PM Acceptance

Board 2: Ready for PM Acceptance - UAT - Prod - Done

As for our team, we have completed the work picked up in the sprint so it is 'Done' for the Sprint. However, when we close the Sprint after testing, the stories/issues are not considered as completed by the Sprint Reports. Jira still considers them as Spill overs and it impacts the velocity.

How do we handle such scenarios? Any suggestions / advice is truly appreciated. Thanks in advance!

[Pasam Venkateshwarrao]

Hi @Raghav Rajagopal 

As my understanding you need to set the sprint goal and the start and end date then it will show like this.i Hope this will help