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:
I don’t have any agile certificates. As an independent coach, trainer, and consultant, I apply whatever makes sense and looks like a valuable solution in a given context.
In this article, I’ll question the need to be certified in agile, discuss the alternatives, and explain how I deliver quality and value to the people that I work with.
This is not a regular “tips and ideas” blog post in which I share my experiences for you to use in your daily work. It’s a personal cry out in which I share my thoughts on a delicate but important topic. …
What if you need to deliver the best possible software products? High-quality products that do everything that your users need in a great way, products that your users will love? Here’s a futurespective exercise that you can use in your agile retrospectives if your teams want to build awesome products.
Teams place themselves in the future by imagining that their goal has been reached.
Next, they will discuss their imaginary past and explore how they have gotten to their goals, by exploring the things that have helped them to get there and the things which made it hard to reach their goal. …