This is general info about what is QA responsibilities and what can be expected from QA Analyst during the project phases. Also other project roles responsibilities are mentioned here as they were discussed during Competence Leaders meeting.
Roles and responsibilities on the project:
Note QA Analyst responsibilities can vary on different projects as sometimes we have lower allocation we would need to do everything we would like to. Therefore responsibilities for QA Analyst are divided into 2 sections - mandatory and optional.
Project role | Description | Responsibilities |
|---|---|---|
PM | Project manager | · Lead the project team · Define and maintain project plan and timeline · Manage project communications, status reporting, and escalations · Responsible for sprint execution and delivery (kick-off, stand-ups, etc.) · Accountable for up-to-date project documentation · Selected individuals to support pre-sales activities & SoW creation |
SA | Solution Architect | · Define solution architecture · Responsible for user story development and management (w/ Customer) · Advise and guide solution development · Accountable for solution quality · Mentor technical team members · Support scope estimations |
CE | Configuration Engineer | · Configure solution according to Solution Architecture and user stories · Collaborate with the project team to resolve issues · Performs unit testing of the delivered solution |
QA | Quality assurance (role is QA Analyst) | Mandatory: · Reporting and retesting bugs · Performing regression testing after bug fixes · Performing smoke tests after deployments to a new partition · Checking risks connected with testing of the solution · Prepares testing strategy for the solution · Delivering key testing artefacts (test plan, test cases, test report, bug report) Optional: · SPOC for PFX project team for customer testing during UAT · Prepare and present sw demo for the customer during Feature Sprints · Communicates with PM, SA, CE and the customer due to understanding of the user stories and the customer needs · Use X-Ray to manage all testing activities on the project · Perform integration testing at early stages of the project · Prepare autometed tests (using Cypress) for later regression testing · Help with impact analysis and priotization of bugs and user stories |
BA | Business Analyst |
Project phases and QA involvement:
Note that we respect every project and every customer is different, it can mean also we have lower allocation on the project we would like to have. So please take following activities as optional, if there is not enough allocation for QA Analyst on the project, obviously we will need to prioritize our tasks and deliver what is possible according to our allocation.
· Sales
o Possible help of QA Analyst with certain allocation can be discussed here - based on discussions with the customer
o Recommendation or consulting from QA can be requested
· Handover
o No QA involvement is expected
o QA is on the meeting (if he is known) to get first information about the project
o QA can introduce the role to the customer
· Foundation Sprint
o QA attends Kick-off meeting to gain first information about the project, scope, customer needs, risks, …
o QA resource planned
o Our tips about UAT project phase are handed over to the customer (what is expected during UAT, tips for successful progress, how to organize tests, how to report bugs, …)
o QA can get first information about user stories from the customer, our SA or BA here. It will help start preparing test strategy sooner for the project.
· Preparation and Setup
o Approach to testing is chosen and discussed with project team – PM, SA, CE
o Draft of Test plan document is created from template, not everything must be clarified in this phase, but we need to know what is clear so far and what we are still missing (from QA point of view)
o Perform integration testing if it is needed on the project
o Configure Jira and X-Ray, set-up basic structure for test documentation on the project - if X-Ray is part of QA delivery
o Deliverable: draft of Test Plan, Integration test report
· Feature Sprint
o Test plan document should finished at the beginning of the phase
o Test cases are prepared for user stories in the current Feature Sprint
Checklist style in Jira or Excel
Linked to user stories
Contain what is tested, expected result, and if needed also test data
X-Ray can be used for this test case documentation - but only with sufficient allocation
o Regression tests prepared within high level point of view in agreement with SA, CE (they should reflect project risks and expected difficulties)
o Log Bugs to Jira and retest them as they are fixed
o In later Feature Sprints scripts for test automation can be created and verified
o Test report is created before UAT to clarify what was tested and which bugs are currently opened (to be transparent to the customer)
o QA can help the customer understand standard testing approach and discuss possible steps for UAT preparation based on our experience. QA can also discuss steps they are doing during UAT preparation.
o QA will prepare and deliver SW demo to the customer
o QA can be SPOC for testing related issues for the customer
o Deliverables: Test Plan, Test Cases, reporting Bugs, Bug report, Test report
(Test report will be checked on the first project if it has added value for the team, maybe JIRA is enough)
· UAT
o SPOC for the customer for bug reporting and issues checking
o Supporting customer in UAT testing (onsite if needed)
o Retesting bugs reporting by the customer, return change requests to the customer and hand over bugs to Pfx team
o Deliverable: Daily report about current bugs and their status, if needed (sometimes it is done directly by PM)
· Cutover
o Smoke test provided after deployment to PROD partition and report from the test created and handed over to the customer
o QA team is ready to help with retesting bugs from customer
o Final version of automated tests can be verified here - the tests can be part of the project documentation and help with basic regression testing after next changes on the project
o Deliverable: Smoke test report, Automated tests for regression testing
· Stabilization
o QA can be SPOC for the customer for bug reporting and issues checking