nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What to do with accepted user stories that have not been put into production?

Scott Porter_9kb74z

Hi - we are doing scrum and have three week sprints. We typically release to production once per quarter, sometimes more often depending on user needs, urgency, etc. We're having a bit of a problem keeping track of user stories that have been completed and accepted, meaning user testing is done and they are 'ready for production', but that have not been placed into production (done, done). Right now, we're carrying them over from sprint to sprint and they are messing up our velocity - because they are technically not 'done', and will need a final integration and UAT with all of the other items being put into a particular production release.

Our question is, where should we put these 'accepted' user stories - that are being held for a production release, which means they will likely have a training task, and final round integration test task, before they are released so that they don't 'hang around' in our current and past sprints?

Thanks in advance for your thoughts! SP

Accepted answers

Ollie Guan

Hi @Scott Porter,

Here are some of my suggestions for reference

First, the standard of deliverables has been reached. It should be considered that the sprint has been completed, then we can end the current iteration in Jira.

Second, the sprint that has ended is not easily tracked in the Scrum Board. It is recommended that you create Kanban for the version to manage these backlogs that have completed the sprint, and perform the release operation on the version after the project is launched.

All comments

Ollie Guan

Hi @Scott Porter,

Scott Porter_9kb74z

Thanks @Ollie Guan! So, we've set this up and I think this is exactly right in principle, but we're having some trouble in practice. we created a new Kanban board for Implementations. we want to put those issues that have been completed in the sprint (Done) and ok for implementation onto that Kanban board until they are released.

When an issue is marked as "Done" in the sprint (which it correctly is, it has been accepted and is complete in the sprint) how do we get it to show up on that Implementation Kanban? How is this part done;

"It is recommended that you create Kanban for the version to manage these backlogs" and "perform the release operation on the version after the project is launched"

That's the part we're struggling with. Thanks again for your help!

@Carr Oduro

Ollie Guan

My pleasure^_^

Scott Porter_9kb74z

So what do you think about how to get the Done issues on to the Kanban? Is there a good way to do it?

erick.coimbra

@Scott Porter You could have also created a filter choosing DONE issues withing a specific time period specified by you OR used some kind of labels system for the filter e.g DONE issue with a label like 'GoProduction'or something.