UAT workflow

[Arvind Soni]

Hi,

We work on 2 week sprint and at the end of the sprint we deliver increment which contains, Bugs, BAU and project work items. We pass them to business user who perform UAT which is outside the sprint and take longer, due to other business priorities. Issues are marked done when our development cycle completed (Dev+QA), how I can accommodate UAT cycle which is outside my control area. Work items to be deployed in production once UAT is completed. How I can achieve this objective?

We are small firm and it's difficult for us to pay for different plugins, apart from Jira + Confluence licenses which we are paying already, so please avoid plugin suggestions. We are new to Jira, so appreciate if you give can detail steps.

[Mark Segall · Accepted solution]

Hi @Arvind Soni

A sprint is intended to be inclusive of user acceptance from a product owner and with their blessing, the issue gets closed out to keep the sprint clean.  In the event of a more waterfall UAT process, you can still close out the issues to keep the sanctity of the sprint.  I typically take these couple steps:

1. Pick what works for you to publish what was completed in the most recent sprint (Confluence page, filter subscription, dashboard)
2. Let the users perform their UAT and if they find anything, capture as bugs linked to the work you just performed and prioritize accordingly for a future sprint

That's pretty much it.

[Arvind Soni]

Thanks, Mark.