User Story Testing

[bhaueter]

So we are new to Jira and SCRUM, but we have created a few epics, multiple user stories, tasks and run a few sprints.

The question I have is when user stories are deemed complete, and the epic enters a testing phase, potentially a new sprint, how do you handle the situation where the testing phase finds problems with a user story? Do we re-open the user story? do we create tasks to fix the user story? The SCRUM process is flexible and iterative, so how do we track this flexibility?

[Jimmy Seddon]

Hi @bhaueter,

Welcome to the Community!

It is one of those tougher questions to answer because there isn't a right or wrong answer.  You will need to choose the process that best works for your team and build that into issue types and workflows as needed in Jira.

However, I can share with you how our development teams are working as a starting point for you to make that decision.

For us, stories aren't considered "Done" until they have met all acceptance criteria.  If bugs are discovered before the story is complete and the Product Owner feels this would cause the story to not meet the acceptance criteria, an additional "Task" is added as a sub-task to the story to be completed.

Once a story has been closed, if a bug is found it is added a an independent "Bug" type to be prioritized along with the other items in the backlog for the next sprint.

This is by no means the only solution, and this might not be the best fit for your company depending on how long your sprints are or how often you release, but this should give you somewhere to start to think about how you want things to work.

Good luck!

-Jimmy