<aside> 💡 Business Stakeholders will perform the Users Acceptance Test to validate if the build matches their expected results. Think of this as an expanded version of your Sprint Review, needed before you move the build to the production environment.
</aside>
<aside> 💡 Provide a brief project introduction and documentation purpose.
</aside>
The Hybrid Project Management using Waterfall and Agile project aims to establish an end-to-end process supplemented with tools to guide users on how to implement based on a hybrid method.
<aside> 💡 Fill in this matrix for every new UAT test scenario.
</aside>
<aside> 💡 Click the Add a New UAT Scenario button to add a new template.
</aside>
| Project Name | |||
|---|---|---|---|
| Test ID | Provide a unique UAT Scenario ID | ||
| Test Name | Provide a unique UAT Scenario Name | ||
| Business Requirement Mapping | Provide the Business Requirement ID where this test scenario is related to | ||
| Functional Design Mapping | Provide the Functional Design ID where this test scenario is related to | ||
| Created On | DD/MM/YYYY | ||
| Last Update | DD/MM/YYYY | ||
| Author | Last Name, First Name | ||
| Tester Name | Last Name, First Name | ||
| Overview | Brief description of the test scenario | ||
| Expected Results | Describe the output expected for this scenario to pass | ||
| Step No. | Description | Pass or Fail Y/N | Tester Notes |
| 1 | Describe the step to test this scenario | Describe steps to replicate (for Failed cases), restrictions, conditional pass requirements, etc. | |
| 2 | |||
| 3 | |||
| 4 | |||
| 5 |
| Project Name | |||
|---|---|---|---|
| Test ID | Provide a unique UAT Scenario ID | ||
| Test Name | Provide a unique UAT Scenario Name | ||
| Business Requirement Mapping | Provide the Business Requirement ID where this test scenario is related to | ||
| Functional Design Mapping | Provide the Functional Design ID where this test scenario is related to | ||
| Created On | DD/MM/YYYY | ||
| Last Update | DD/MM/YYYY | ||
| Author | Last Name, First Name | ||
| Tester Name | Last Name, First Name | ||
| Overview | Brief description of the test scenario | ||
| Expected Results | Describe the output expected for this scenario to pass | ||
| Step No. | Description | Pass or Fail Y/N | Tester Notes |
| 1 | Describe the step to test this scenario | Describe steps to replicate (for Failed cases), restrictions, conditional pass requirements, etc. | |
| 2 | |||
| 3 | |||
| 4 | |||
| 5 |
| Project Name | |||
|---|---|---|---|
| Test ID | Provide a unique UAT Scenario ID | ||
| Test Name | Provide a unique UAT Scenario Name | ||
| Business Requirement Mapping | Provide the Business Requirement ID where this test scenario is related to | ||
| Functional Design Mapping | Provide the Functional Design ID where this test scenario is related to | ||
| Created On | DD/MM/YYYY | ||
| Last Update | DD/MM/YYYY | ||
| Author | Last Name, First Name | ||
| Tester Name | Last Name, First Name | ||
| Overview | Brief description of the test scenario | ||
| Expected Results | Describe the output expected for this scenario to pass | ||
| Step No. | Description | Pass or Fail Y/N | Tester Notes |
| 1 | Describe the step to test this scenario | Describe steps to replicate (for Failed cases), restrictions, conditional pass requirements, etc. | |
| 2 | |||
| 3 | |||
| 4 | |||
| 5 |
| Version | Date | Author | Role | Description |
|---|---|---|---|---|