It is very important to carry out tests on IT products. It is the only way to prevent bugs from being discovered by end users, with image and financial damage

• guarantee quality standards (QA) within the team in order to release a bug-free and usable product
• the responsibility to approach the product from the point of view of the end users (usability)
• make sure that the User Stories contain Acceptace Criteria that favor both technical and functional development
• having a Business Facing Test approach for developing User Stories to be testable (where possible)
• Determine appropriate metrics in Test processes (Test Plan / Use Case / Test Case)
• Development Exploratory Test and Disaster Scenarios to fully test the functionality of the products

These are the Quadrants of the Agile tester: a mapping of the areas of competence of an Agile Tester . We believe that it is not easy to find a figure that can fully cover all the areas because we move from a systemic figure, to a developer, to a designer. Surely our work experience makes me very confident in Q2 and Q3

Plan
Scenarios are defined during planning (or grooming)

Desing
Development of tests (UAT / TC or Trace Bullet of an automatic test)

Test
At the end of the sprint the developed tests must pass

Review
The User Stories are “put in done”: presentation to the stakeholders