Op 5 juni 2014 is het boek Waardevolle Agile Retrospectives gepubliceerd, het 1e Nederlandstalige boek met oefeningen voor Retrospectives. Je kunt de Nederlandse uitgave downloaden via Leanpub en Amazon.nl. Het Nederlandstalige boek is ook te koop op benlinders.com als Paperback en op bol.com (paperback/ebook).
In December 2013 we published Getting Value out of Agile Retrospectives: a pocket book full of Retrospective Exercises. More than 1000 readers have downloaded this book in the first five months after publication from Leanpub and many more have downloaded it from InfoQ: there are 5000++ readers worldwide of our book on Valuable Agile Retrospectives. A big thanks to all of our readers!
The key Scrum ceremony that helps the team reflect on its behaviour is the retrospective. In my view, this is not any new concept or jargon the team needs to master -- but yes, in reality it sometimes becomes challenging to keep the momentum lively at all times! Let us look at the reasons why this happens and discuss a few ideas for making these meetings effective.
As a retrospective facilitator it's important to have a toolbox of retrospective exercises which you can use to design a retrospective. Before having a retrospective meeting, you want to prepare yourself by considering which exercises would be most suitable. That depends on the team, the situation at hand, and on what the team would like to work on. Here are some tips for designing valuable agile retrospectives that help addressing specific situations.
Een agile manier van werken is prima geschikt voor het ontwikkelen van software. Maar dat is niet het enige wat je met agile kunt doen. Scrum kun je ook prima toepassen in het onderwijs. eduScrum is een leuke en effectieve manier om agile les te geven met zelf-organiserende teams van leerlingen. Als partner en vriend van eduScrum mocht ik een kijkje in de keuken nemen bij het Ashram college in Alphen aan den Rijn en sprak ik met leerlingen over hun ervaringen met eduScrum.
There are organizations which think that Agile or Scrum can be the solution to solve all IT problems that they have. Senior management has decided that their whole organization has to become agile. To realize that they demand that all existing (waterfall) processes will be replaced by Agile processes. Even if they succeed to do that (which is often not the case) they are usually not getting the expected business benefits out of Agile. Replacing processes doesn't make an organization Agile.
Eind vorig jaar is mijn eerste boek Getting Value out of Agile Retrospectives gepubliceerd. In de eerste 100 dagen zijn er meer dan 5000 exemplaren gedownload via InfoQ en Leanpub. Mede door dit succes hebben de auteurs Luis Gonçalves en ik besloten om het boek in meerdere talen uit te brengen, waaronder ook Nederlands.
In an ideal world agile teams are working with one product owner or customer. But there are also teams which have more than one customer, maybe even multiple product owners. Due to that all the team members are often not working together on a daily base. Is it useful for such teams to do a retrospective together? How can they define actions that will be beneficial for the complete team?
Our book Getting Value out of Agile Retrospectives has reached 500 readers on Leanpub. There are also many more readers that have downloaded our book from InfoQ. Readers have rated our book 4.6 out of 5 on Goodreads. A big THANKS to all of our readers from Leanpub and from InfoQ: having so many readers interested in doing Valuable Agile Retrospectives makes use very happy!
Do your teams want to know how agile they are? And what could be the possible next steps for them to become more agile and lean? In an open space session about Agile Self-Assessments organized by nlScrum we discussed why self-assessments matter and how teams can self-assess their agility to become better in what they do.
Veel van mijn artikelen gaan over verbeteringen om sneller de juiste producten en diensten met goede kwaliteit aan klanten te leveren. Verbeteren doe je niet door een doel te stellen. Een CMMI niveau is geen effectief verbeterdoel. Wat wel werkt is regelmatig reflecteren en met de feedback continu verbeteren in kleine stapjes. Kanban en Retrospectives zijn effectieve manieren om dat te doen.
Root Cause Analysis can be used in software development to build a shared understanding of a problem to determine the first or “root” causes. Knowing these causes helps to identify effective improvement actions to prevent similar problems in the future. You can also do Root Cause Analysis in agile to stop problems that have been bugging your team for too long.