QA Team Best Practice: MoM (Date: 22/12/2023)

Requirements Gathering:

1. Need to have a weekly meeting thrice with Saravanan to gather requirements and finalize it
2. Requirements for current sprint and next sprint should be tracked
3. Requirements should be well thought through and 1st set of questions should be raised and
tracked through Jira
4. Requirements should be finalized only after a green signal from Business Team, Dev and QA
5. Any red flag regarding requirements should be communicated to Muthu / Murali / Pavan
6. Requirements should be finalized and converted to Test cases only after Reverse KT within
QA

Test Case Writing:

1. Test Cases should be well written by each QA individual

2. Beta Testing cases should be tagged
3. Sync Cases should be well thought through using the Impact Analysis sheet
4. Impact Analysis sheet should be finalized only after discussion within QA
5. Automated Cases should be marked as well
6. New Cases raised in Jira as bugs should be converted to Test Cases periodically
7. Any test cases that comes from Ad-hoc Testing should be captured in Test Cases
8. Any requirements changes should be tracked and converted to Test Cases periodically
9. Test Case status should be inspected by Muthu periodically

Regression / Feature / Smoke Testing & Bug Testing practices:

1. Testing status should be shared by each QA individual in common group with detailed
report. Follow a template shared by Muthu.
2. Any backlog bugs, On-hold bugs should be communicated in each scrum meeting
3. All the Ad-hoc testing and production issue testing should be priority
4. Any ad-hoc defect and production defects should be tracked in the current sprint list and
such defects should be raised for that sprint timeline

General Practices:

1. Each QA individual try to work within office hours following the best practices listed here
unless any emergency situations
2. QA should take ownership for each of their modules, scheduling tasks, requirements,
reverse knowledge transition, test case writing and updating
3. QA should make use of any free time to complete any of their own pending tasks.
4. Every status updates and reports should be communicated to Muthu and Team by QA
individuals themselves without having to questioned by others
5. Any tedious tasks/ requirements/ modules should be informed to Muthu
6. Every open Production bugs should be addressed in Morning Scrum Meeting
7. Every open bugs from every sprint should be moved to Backlog
8. Previous sprint backlogs should discussed in requirement gathering to finalize for the
sprint
9. Estimated time should be followed for test cases writing, to go through requirements. If
faced any delay, try to intimate Muthu to take action
10. Status Update should include open bugs, hold requirements for every sprint
11. For every build push, dev team need to intimate with release notes