CREATING THE PROJECT DELIVERABLES FOR TESTERS
As with the product backlog, the release plan could also be updated with high-level issues that had been encountered in previous releases. The testers should work with the Product Owner to ensure that these issues, if not planned for fixing in the current Sprint, are included in the release plan.
Sprint Backlog
Because an Agile project would consist of Sprints that would make up a release, each Sprint would have its own goal and backlog for the team to work on. The Sprint backlog lists the user stories, issues, and tasks scoped for completion within the Sprint. As with the Product Backlog, the Sprint Backlog is also prioritised and estimated to help ensure that the team will be able to focus on the more valuable items first and take in work that fits their capacity.
During Sprint Planning, everyone on the team – including testers – should give estimates on the user stories and bugs that are scoped for fixing within the Sprint. This is the best place for negotiating the scope and clarifying the acceptance criteria to ensure that the team will be able to accommodate the work within their capacity.
Testers should ensure that when they are giving estimates, they take into consideration their testing tasks such as data creation, test design, and bug fixing. If they haven’t discussed during some of the bugs or user stories in Product Backlog Refinement, they could use this time to provide feedback on them.
Throughout the Sprint, the tester should update it with ticket statuses and add tickets for bugs found during testing. They should also help with ensuring that backlog items meet the Definition of Done before they close or mark them as “Done.”
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: