Question

A project team is looking at identifying the root cause of bugs detected in UAT. They conducted a brainstorming session
within the team and collected sticky notes listing the various causes that could have resulted in the UAT defects.

Answer 1

Answer:

I don't understand the question

Answer 2

Various causes that could have resulted in the UAT defects.

Explanation:

• To treat UAT as a validation exercise that exists outside the Scrum framework.

• At least once in a sprint, the development team creates a potentially releaseable increment and the Product Owner can choose to release this increment. In this particular case, the Product Owner will issue the increment to UAT. I recommend properly recording any findings to identify deviations in expected behavior versus modifications based on experience.

• However, some teams consider completion of UAT as part of their definition of complete. A one week UAT cycle at the end of the sprint can make this more difficult. In this case, the UAT feedback will be concluded or resolved prior to the Sprint Review and the end result will be an enhancement, which can be issued at the decision of the Product Owner.