Sign Off & Conditional Sign Off
QA Sign Off
The main aim of a QA is to make sure that the software meets the customer’s needs without harming the application.
The formal way of declaring this process is Sign Off. The QA can acknowledge that they have reviewed and tested the application and now the application is ready to release.
Who all are responsible for Sign Off?
This process has been done after doing the complete testing of the software by the testing team.
When the testing team tests the application completely and when the exit criteria meet, they can send the mail/communicate for Sign Off.
Usually, the Test Manager, Project Manager, and Business Analyst takes the responsibilities and agrees to the QA Sign Off.
Criteria for QA Sign Off
As we know, QA can do Sign off after meeting the exit criteria, the exit criteria should be already mentioned in the Test Plan document. In exit criteria, the QA checks the following things:
- All the necessary test plans should Run.
- The software should meet Customer needs.
- There should be no High/Immediate/Urgent issues present in the Software.
- All the priorities task should get done.
- All the priority test cases should Run and should pass the execution.
- The level of Requirement coverage should meet.
- The development activities should not go beyond the cost of the project.
- The development activities should not cross the deadline.
Read more: https://tudip.com/blog-post/sign-off-conditional-sign-off/