What to do with Stories when they are QA deployed at the end of the Sprint?

[Jagadeesh Sunkara]

Some of our user stories get deployed to QA at the end of the Sprint.  We used to move the story as is to the next sprint at the sprint closure.  But this caused our metrics show that we have carried stories over many sprints.  What should we do with the stories when QA is not completed at the end of the Sprint? 

[Alexey Pavlenko _App Developer_]

Hello @Jagadeesh Sunkara ,

Most likely, you’ll need to adjust the sprint length or task decomposition. The end of a sprint typically implies deployment to production.

However, if you’d prefer to stick with your current setup, you need the app supporting this flexibility - for example, this one - Multi-team Metrics & Retrospectives, which is developed by me. Using custom JQL metrics, you can build reports that exclude tasks in specific statuses from being treated as carry-overs:

Best regards,
Alexey

[Matteo Vecchiato]

Hi @Jagadeesh Sunkara ,

Welcome to Atlassian community and thank you for your question.

In Scrum framework this metric is what is expected, in every sprint the goal is to close all the stories that initially the team took the compromise to do. It measures how good the team was respecting what planned.

So, your metric is working correctly, it's warning you about some stories are not closed on time.

You can adapt the stories depending on your situation and set the DoD accordingly. If, for same reasons, you need to flag the stories as closed before the QA deploy, you could create separate tasks for deployment and consider the stories closed before it.

All depends on the DoD.

I hope it helps