Testing in Iterations
One of the important Agile ceremonies is iteration or sprint planning. In this event, all team members specify how much work they can deliver from the prioritised product backlog items for the next Iteration. Planning for the next iteration helps to organize the work and defines the commitment to the customers for the next iteration.
In iteration planning sessions, the product owner and customers optionally attend to describe the stories and requirements. If it’s not possible, people close to customers such as business analysts represent the customers in the session and help in making the decision and explaining the requirements. The stories are handled from highest to lowest priority.
Each story is discussed through conversations among the people attending the session. Customers explain the stories by examples and testers turn them into high level tests. Through conversations among team members, it is guaranteed that all the people have the same understanding of the story. Different aspects of the story are seen and it becomes clarified for all people including programmers, testers, the product owner and the customers. The stories are sized as well. They should not be too big. If so, they should be split into smaller stories.
The Definition of Done (DoD) is defined for each story by writing user acceptance tests. These tests are high level and are written by the Agile team in collaboration with stakeholders. If these tests are passed successfully, the story is considered as Done.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: