Improve Software Quality with Retrospectives
An agile retrospective is a practice for teams to reflect, learn, and to continuously become better in what they do. Although retrospectives are most often used to explore the current way of working, they can also be used to investigate quality issues or to agree upon actions that can improve the quality of the software that is delivered.
Here are suggestions of what you can do in your retrospectives to improve software quality:
- Explore major or repeating problems with a Root Cause Analysis.
- Do a futurespective for building an awesome product.
- Reflect on your quality practices with the Agile Self-Assessment Game.
- Solve quality issues with a Stop the Line exercise.
This article is based on the chapter Improve Software Quality with Retrospectives from the book What Drives Quality. This book explores how quality plays a role in all of the software development phases, it takes a deep dive into quality by listing the relevant factors of development activities that drive the quality of products. It provides a lean approach to quality, which analyses the full development chain from customer request to delivering products.
