Several components of the sprint should be included for discussion in a retrospective meeting:
- Processes – planning and execution
- Communications – within the scrum team, with key stakeholders and with end users
- Environment – work logistics and system infrastructure
- Artefacts – documentation created and,
- Tools – ensuring that the team has what is needed to work effectively.
Testers will have additional input to the retrospective including review of:
- Prioritisation of features – complexity and usage
- Schedule – time allotted for testing
- Test Driven Development – ability to create test cases used in the development of features.
The retrospective ceremony should be used to evaluate areas of improvement and highlight processes that went well and should be continued. If a scrum team does not identify changes during a retrospective, then the team should feel comfortable moving forward into the next sprint using the current set of components. Since the retrospective is held at the end of each cycle, scrum team members will have a chance to evaluate at multiple times during the life-cycle of the product development.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: