PSM-II · Question #14
Your organization requires all Increments to pass user acceptance testing (UAT) before it is allowed to be released to production. Is it a good idea to postpone UAT until the end of the project to…
The correct answer is A. No, because the state of the Product Increment won't be transparent and the feedback loop would. The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done". At the end of a Sprint, the new Increment must be "Done", which means it must be in useable condition and meet the Scrum…
Question
Your organization requires all Increments to pass user acceptance testing (UAT) before it is allowed to be released to production. Is it a good idea to postpone UAT until the end of the project to prevent the Development Team from being disrupted during the Sprints?
Options
- ANo, because the state of the Product Increment won't be transparent and the feedback loop would
- BIt depends on the team's Definition of Done.
- CYes, because the Development Team is a self-organizing team and should not be disrupted
- DYes, because UAT is done in a hardening Sprint before the release Sprint.
How the community answered
(46 responses)- A74% (34)
- B7% (3)
- C4% (2)
- D15% (7)
Explanation
The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team's current definition of "Done". At the end of a Sprint, the new Increment must be "Done", which means it must be in useable condition and meet the Scrum Team's definition of "Done". An increment is a body of inspectable, done work that supports empiricism at the end of the Sprint. If UAT is a part of the team or organizational standard, then any delay in this activity will reduce transparency and increase risk.
Topics
Community Discussion
No community discussion yet for this question.