If I ask people who facilitates their agile retrospective, most tell me that it's their Scrum master. Some even look surprised, as if their could be anybody else who leads their retrospectives? Yes there can be. In some situation it's even better if somebody else than the Scrum master facilitates the agile retrospective.
The practices in the workshop Getting More out of Agile and Lean will help you to develop the right products for your business and customers, reduce your delivery time, increase the quality of your software, and create happy high performing teams.
I will be covering the GOTO Amsterdam conference for InfoQ. GOTO Amsterdam is a practitioner-driven enterprise software development conference designed for team leads, architects, and project management and is organized "for developers by developers".
I regularly get questions on agile retrospectives, which I'm more than happy to answer. In this blog post I'll discuss the question that I got from someone who attended one of my workshops on valuable agile retrospectives. He was planning a retrospective with a new team, and wanted my advice on which exercise to use and how to facilitate the retrospective.
Five great French books on agile have bundled up on Leanpub and are now offered for a significantly reduced price. Together these books provide insight into agile retrospectives, coaching, managing requirements in agile, and programming by kids. Take a look at Livres français sur l’Agilité.
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.
In this workshop you will learn how to scale agile retrospectives, doing them with multiple teams from a project, product or organization, practice facilitation skills with different retrospective exercises, and learn how you can introduce and improve retrospectives. You will also learn to do agile self-assessments and readiness checks and to design and facilitate retrospectives that help organizations to increase their agility.
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.