In Agile retrospectives gebruik je oefeningen waarmee je als team kunt verbeteren. Het boek Waardevolle Agile Retrospectives bevat 13 oefeningen die je in retrospectives kunt toepassen. Deze blog post beschrijft een nieuwe retrospective oefening die gebruikt kan worden om de kwaliteiten van (Scrum) teams zichtbaar te maken, ze te bespreken en vervolgens te kijken hoe je ze kunt benutten.
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é.
I gave a talk about Nuggets for your Continuous Improvement Journey at the Agilia 2016 conference in Olomouc, Czech Republic, and a full day workshop on Valuable Agile Retrospectives that was very well received.
I met Hugo Messer a couple of years ago, when I connected with Bridge Global who started publishing guest posts from me. We talked about working with remote teams to find out that our thoughts on this are quite similar. In this guest post Hugo explores how Scrum can help distributed software development teams.
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 :-)
Agile teams gebruiken retrospectives om hun manier van werken te reflecteren en te verbeteren. Veel Scrum teams sluiten iedere iteratie af met een retrospective. Teams die Kanban gebruiken doen veelal wekelijks een retrospective of doen zo vaak als nodig is een mini-retrospective om van een probleem te leren en in kleine stapjes te verbeteren. Hoe vaak doen jouw teams agile retrospectives?
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.
I recently received a question whether Product Owners should participate in agile retrospectives. An interesting discussion took off about how "it should be by the book" and "common sense" which I have summarized in the below blog post.
We've teamed up with the Agile Retrospective Kickstarter book to help you to do better retrospectives. Retrospectives that your teams love to do, that will help them to improve and deliver value to their customers and stakeholders.
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.
Two great books on agile retrospectives are now available in the book bundle rétrospectives agiles on Leanpub: Tirer profit des rétrospectives agiles by Luis Gonçalves and Ben Linders and Donnez un coup de fouet à vos Rétrospectives Agile by Alexey Krivitsky.
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.