BIO

Ben Linders is an Independent Consultant in Agile, Lean, Quality, and Continuous Improvement, based in The Netherlands. Author of Getting Value out of Agile Retrospectives, Waardevolle Agile Retrospectives, What Drives Quality, The Agile Self-assessment Game, and Continuous Improvement. Creator of many Agile Coaching Tools, for example, the Agile Self-assessment Game.
As an adviser, trainer, and coach, he helps organizations with effectively deploying software development and management practices. He focuses on continuous improvement, collaboration and communication, and professional development, to deliver business value to customers.
Ben is an active member of networks on Agile, Lean, and Quality, and a well-known speaker and author. He shares his experiences in a bilingual blog (Dutch and English), as an editor for Culture and Methods at InfoQ, and as a practitioner in communities like Computable, Quora, DZone, Stackoverflow, and TechTarget. 

Talk

Improving Software Quality with Retrospectives

Agile Retrospectives can be used to investigate quality issues or to perform actions that improve the quality of the software that is delivered. They complement debugging and testing and provide solutions to learn and build quality in from the start.

An agile retrospective is a practice for teams to reflect, learn, and to continuously become better in what they do. They focus on the process and way of working to help testers and developers to collaboratively improve products and deliver more value.

In this presentation, Ben Linders provides suggestions with examples of what you can do in your agile retrospectives to improve software quality.

What can attendees learn:
• How to prepare and facilitate an agile retrospective
• 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