Agile Retrospectives
In Agile development, a retrospective is a meeting that takes place at the end of each iteration to discuss what was successful, what could be improved, and how to incorporate the improvements and retain the successes in future iterations. Further, retrospectives cover topics such as the process, people, organizations, relationships, and tools.
Features of Agile Retrospectives
-
- Retrospectives can result in test-related improvement decisions focused on test effectiveness, test productivity, test case quality, and team satisfaction. They may also address the testability of the applications, user stories, features, or system interfaces.
- The timing and organization of the retrospective depend on the particular Agile method of the business. Business representatives and the team attend each retrospective as participants while the facilitator organizes and runs the meeting. Retrospectives ideally take place at the same place and same location every iteration.
- The retrospective meeting generally occurs immediately after the Sprint review meeting.
- Testers are an important part of the team and bring their distinctive perspective. Moreover, all team members (testers and non-testers) can provide input on both testing and non-testing activities.
- Retrospectives must occur within a professional environment.
Get certified and unlock more opportunities. Practice and Validate your skills to become a Certified Agile Testing Professional Now!