...
Here is an overview of what is expected from QA Analyst on the project. It is mainly focused on different phases on the project, but please be sure expectations from QA Analyst is also connected with allocation on the project, as all QA work should be billable not the project:
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Sales
...
nothing is expected from you here to test
...
QA Analysts
...
may occasionally be asked to answer
...
questions from the customer
...
, usually about
...
the QA methodology,
...
tools, or
...
specific testing
...
scenario. Nothing is expected from you here to test
Handover
...
The goal for the QA of participating in a handover meeting is to simply listen and gain basic knowledge about the customer and
...
their needs.
Foundation Sprint
During the kick-off meeting be there to listen and gain first information about the project, scope, customer needs, potential risks, customer’s experience in software testing, …
In case you have an opportunity, check with the customer his view on UAT, and offer him help (test management, reporting bugs, preparing for UAT, tips and tricks are just few topics to discuss). If the customer is interested in some help but you don’t feel comfortable discussing the topic with him, ask your Competence Leader or Principal/Senior QA Analyst for help.
In case the customer is interested, test automation discussion can start here, even a first Cypress demo can be organized to clarify benefits and answer all customer’s questions
...