Do you have a question about doing agile retrospectives? Need some help on how to do them? I'm there to answer your questions. All you have to do is ask :-)
Over the years I've had some situations where I couldn't get a team to come together in a retrospective to meet and reflect on the sprint. I've seen two different kinds of reasons for this. One was that a team wasn't convinced that agile was suitable for them, so they questioned doing agile retrospectives. The other situation was that the team believed in agile and Scrum and wanted to do a retrospective, but was looking for an alternative solution where they would not have to meet physically. Something that also a dispersed team would consider when travelling isn't an option. Let's explore how you can recognize these situations and deal with them.
Who should be handling and solving impediments? Should it be the Scrum master? The team as a whole! Their agile coach? I prefer that team members recognize and solve impediments themselves. For most of them they don't need a Scrum master or coach. So if they see a problem, I expect team members to take action and solve it.
Agile teams use retrospectives to reflect, learn, and adapt their way of working. Facilitating retrospectives matters, it's important to have a skilled facilitator to assure that retrospectives become effective. Let's explore 7 good practices and tips that facilitators can use to help teams to get more value out of their agile retrospectives.
Het Agile Manifesto beschrijft dat teams frequent reflecteren om hun effectiviteit te verbeteren. Je kunt Agile Retrospectives gebruiken om te leren van hoe dingen nu gaan en de manier van werken in Agile-teams aan te passen om continu te verbeteren. Dit eerste artikel van een serie over agile retrospectives geeft een introductie in retrospectives en beschrijft hoe je kunt zorgen voor veiligheid zodat mensen open en eerlijk kunnen zijn.
Attend my workshop Getting More out of Agile & Lean in Melbourne, Australia to learn practices for teams and their stakeholders to develop the right products, deliver faster, increase quality, and create happy high performing teams.
Are you interested in learning practices for teams and their stakeholders to develop the right products, deliver faster, increase quality, and create happy high performing teams? Come to my workshop Getting more out of Agile & Lean in Sydney, Australia.
People often ask me what to do to prevent that teams get bored when doing agile retrospectives for a longer period. The short answer is: Make sure that you are getting value from doing your retrospectives. 5 practical tips that will assure that you keep getting value from your agile retrospectives.
Bij een Kanban veranderaanpak gaat je uit van wat er is en start je bij de medewerkers. Je werkt bottom up om in kleine stapjes effectief te veranderen.
To make Agile work organizations have to establish and develop self organizing teams. In many organizations, "command and control" management is a common practice when they start implementing agile practices. Coaching a team to become self organized can be a challenge for Scrum masters. Here are some tips for doing it.
Agile definitely needs coaching. But the way that people are coached can make a huge difference, it can be done more effectively with part-time coaching. It’s not about the coaches, it’s coaching and the coachees that matters!