User Acceptance Testing

Owned by Maria Kutkina
Last updated: Jan 10, 2024
2 min read

 

Built-in Quality

Throughout the release cycle, the Contractor ensures compliance with relevant standards, including facilitating audits and approvals during the Release UAT cycle.

At the end of UAT, Contractor updates the Requirement Traceability Matrix and Test Closure Report for approval, marking the conclusion of test activities.

left shift testing.png

 

Release UAT Cycles

  • The Contractor plans to use a release cycle that typically includes four sprints per release, adjustable based on project needs and minimum viable product requirements

  • At the end of each two-week sprint, newly developed functionalities are demonstrated to identified stakeholders. Feedback is evaluated for immediate action or potential inclusion as a new user story.

  • In addition to sprint UAT cycles, the team will facilitate release UAT cycles for epic-level testing. This so-called left-shift testing approach allows users to validate entire blocks of functionality, providing a broader context for business requirement satisfaction.

  • An example cycle would involve users testing various aspects of a feature across different sprints and then testing them collectively in the release UAT to ensure comprehensive functionality.

 

Final UAT and Production Promotion

  • After the final sprint in a release cycle, Contractor dedicates time to fix outstanding defects and prepare the official UAT release.

  • A formal 15-day UAT cycle follows, serving as both final acceptance testing and a regression test.

  • The Contractor collaborates with stakeholders to finalize the release schedule.