Agile projecten gebruiken vaak retrospectives, waarin ze vragen stellen zoals: 'wat gaat er goed', en 'wat kan beter'? Met het eerste gebeurd vaak niet zoveel. 'Leuk om te horen' is de reactie. Een gemiste kans! Want weten wat er goed gaat en begrijpen waarom, de onderliggende sterktes, kan je helpen om dingen te verbeteren die (nog) niet goed gaan.
Software development organizations need to become more agile and lean, to deliver products that satisfy the needs of their customers. An agile approach where you change your way of working in small directed steps is often the most effective way to implement agile. Are you ready to go on an Agile trip?
We moeten onze kennis beter gaan delen, vaker leren van elkaar hoe je dingen kunt doen, hoe het beter kan. Kennis delen en toepassen, wielen (her)gebruiken om ermee te gaan rijden. Ben je benieuwd hoe je dat kunt doen?
Agile retrospectives can be used by teams to inspect and adapt the way of working. Here's an introduction to agile retrospectives, to help you to get started with them.
Another technique for Getting Value out of Agile Retrospectives is "Asking Why?". "Why" is one of the most valuable question that I use in retrospectives. It gives insight in peoples behavior and their feelings and motives that drive them, helps to find root causes of problems, and reveal the strengths that people have. And helps teams to see common goals, and find ways to collaboratively reach them.
The book Peopleware by Tom DeMarco and Tim Lister has been released in a 3rd edition, and the topics addressed in it are still very important. Software development is about people: when, how and where they can work together. If you truly are concerned with people, and looking for ways to improve how you collaboratively develop and deliver software, then this book is a must read.
What can agile projects do to improve collaboration between teams, and increase their contributions in the project? Doing retrospectives of retrospectives is a way to share learnings across a project, and to solve problems that a project is facing.
Als een een probleem moet worden opgelost bedenkt men vaak zelf iets nieuws Leren van collega’s gebeurd te weinig. Waarom zijn nog steeds zoveel mensen bezig om het wiel opnieuw uit te vinden? Er zijn wielen zat, in alle soorten en maten, dus laten we ze (her)gebruiken om ermee te gaan rijden!
How can you become an excellent team that is able to deliver and exceed customer expectations? By continuously becoming better in the things that you are doing great, using a strengths based retrospective. This technique helps teams to improve themselves by focusing on their personal and team strengths.
The 2nd blog in the series "Retrospective Benefits" explains how team benefit from retrospectives by finding those improvement actions that matter to them, and help them to do their work better. Agile retrospectives give the power to the team, where it belongs!
When you have problems that keep coming back in your sprints, you can try the five times why technique. It helps you to get to the root causes of the problems, and to define effective actions that prevent them from happening in future sprints. This is one of the retrospective technique that will be included in the Pocket Book on Agile Retrospectives, your feedback can help us to improve it!
Together with Luis Gonçalves I am writing a pocket book about "Getting Value out of Agile Retrospectives".We value your feedback, so please let us know what you think of our initiative, our previously published blogs and which topics you would like to have covered in the pocket book?