Day 1: During the first day of the iteration, the highest priority stories are picked from the product backlog. The QA tester , along with the rest of the team members and the Product Owner, work to define the acceptance criteria for each user story. High-level questions are asked, and the acceptance criteria is written as part of each story. In the second part of the planning session, the testing tasks for each story are identified and estimated. Some typical testing tasks are: “Define high level tests,” “Write automated tests, ” “Perform manual exploratory testing,” “Write a GUI smoke test,” and “Generate test data.” Days 2/3: On the 2nd and 3rd days of a sprint, the tester has conversations with the Product Owner to refine acceptance criteria for each story. The goal of these conversations is to elicit the details of what is expected from each feature . These conversations may go on the following day/s. Also, during days 2 and 3 of a sprint, the Tester st...