QA Role in Agile/Scrum environment

1. Actively participation in user stories development
2. Read, comprehend and estimate testing of stories/functionality.
3. Help team refine and define stories, raise doubts, give suggestions to develop/redefined story to best fit for the customer requirement.
4. Define testing tasks from story like high level test case design, functional testing, system and UAT task.
5. Update story coverage daily on percentage bases or task bases whatever defined for your project.
6. Perform functional testing, system testing, perform defect management, retesting, regression testing.
7. Perform automation scripts development if any.
8. Finally UAT and closer of task and stories.

Based upon above points QA/testing tasks in different phases of iteration or sprint:

Task when current Iteration in Development phase:

• Read and review user stories, design high level scenarios/test cases including alternate paths of user story. Raise doubts until stories are not clear. This will enhance the quality of product.
• Automate previous iteration tests if any.

Task when Iteration is in integration phase(Build available for QA )

• Exploratory Testing: Simultaneously learn about the system’s behavior while pursuing faults and defects driven by challenging assumptions.
• Gorilla Testing: Functionality heavy testing on a particular module.
• Finalize & execute functional test cases.
• Continuously execute Automated Regression Scripts against new builds.
• Log Defects / Issues.

Tasks once current Iteration is in Acceptance Phase

• Execute Functional Test Cases to meet Acceptance Criteria (Fulfill User Story Requirements).
• Execute Automated Regression Scripts.
• Log Defects or Issues / Update and publish dashboards to Project Team.