Is UAT not able to complete in the sprint?

Scrum Master Challenges and Solution

Most of the scrum masters face this issue that the team is unable to complete UAT in the same sprint.

As most of the time, UAT is done by the end-user and the end-user may take time more than two weeks, due to the story come out of the sprint as an incomplete story.

Practically why this issue comes, because the current problem is UAT is part of the definition of done and UAT takes time for more than two weeks.

So to overcome this issue there are two approaches.

1. We should remove UAT from the sprint definition of done (DOD) and add it into the release’s definition of done(DOD).
UAT should be a continuous process, So while doing release planning, we should consider all done stories with UAT completion for the upcoming release.
With this approach, we overcome this challenge.

2. Another approach if you are using SAFe framework, then we have to remove UAT from sprint’s definition of done (DOD) and add to the PI level definition of done(DOD),

So while completing PI, We should cover UAT for sprint-level done stories and with this approach, we can come over to this challenge.

So with these two practical real-life options scrum masters can come over with these UAT challenges.

Also to improve this problem from a long-term perspective, ask yourself, Why UAT is taking time, what is the issue with the user? Why user is not able to give sign-off to UAT in the same sprint as the Product owner gives his PO Approval? Do further analysis on this and see how we can understand the user’s pain to provide UAT on time and then take further action.

I hope this is useful for you, In case you are following any other alternative for this then feel free to comment.

Thanks
Kshitij Yelkar