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!
A 1 word retrospective is a technique that helps if a team is struggling with the way they collaborate, or if there are issues which are not dealt with. All team members state in 1 word how they feel about the sprint, and a discussion is facilitated. It is an effective way for the team to discuss what is hampering them, and agree on how to deal with it and get it out of the way.
A list of the success factors that helped organizations to get Scrum implemented and used, and to make a difference.
Having a "toolbox" of retrospectives helps you as a retrospective facilitator to deliver value to a team. You can plan a retrospective meeting, and think about the technique that you want to use, but be open to change it on the spot when needed.
Hoe ziet organisatie eruit zonder hierarchie en managers, waarin iedere medewerker vrij kan beslissen wat hij/zij wel of niet doet. Een kijkje in de keuken van een Self-Organizing Organization, en de succesfactoren van self-organizing.
One technique often used in agile retrospectives is to ask questions to the Scrum team. It's a technique that is easy to learn, but the effectiveness depends on the questions that you ask to the team. Which Questions do you ask?
What do you think: Should the scrum master come from the team, or should it be (former) project managers?
Bij het invoeren van Agile is aandacht voor menselijke factoren belangrijk om Agile succesvol toe te passen. Bijvoorbeeld om tot teams te komen, waarin professionals effectief samenwerken.
Listening to people and understanding their reasons to resist to change has worked for me, not only with agile, but with all kinds of (process) improvement. What works for you?
Is er bewijs waaruit blijkt dat Agile beter werkt? Een boekverslag van "Agile Werkt", over meten, analyseren en benchmarken van IT-projecten, en andere onderzoeken naar de resultaten van Agile werken.