Designing Valuable Agile Retrospectives

  • Post published:May 5, 2014

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.

Continue ReadingDesigning Valuable Agile Retrospectives

Agile leren met eduScrum

  • Post published:April 7, 2014

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.

Continue ReadingAgile leren met eduScrum

We Want Agile Processes

  • Post published:March 28, 2014

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.

Continue ReadingWe Want Agile Processes

Retrospectives for Teams with Multiple Customers

  • Post published:March 6, 2014

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?

Continue ReadingRetrospectives for Teams with Multiple Customers

500 Leanpub Readers of Valuable Agile Retrospectives!

  • Post published:March 3, 2014

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!

Continue Reading500 Leanpub Readers of Valuable Agile Retrospectives!

Self-assessing How Agile You Are

  • Post published:February 11, 2014

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.

Continue ReadingSelf-assessing How Agile You Are

Continu Verbeteren met Kanban en Retrospectives

  • Post published:February 6, 2014

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.

Continue ReadingContinu Verbeteren met Kanban en Retrospectives

Success Factors for Root Cause Analysis in Software Development

  • Post published:January 28, 2014

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.

Continue ReadingSuccess Factors for Root Cause Analysis in Software Development

Agile Veranderen door sterktes te gebruiken

  • Post published:January 20, 2014

De trend die ik in 2013 heb gezien van kleinere en snellere verbeteringen in organisaties zal zich doorzetten in 2014. Een Agile manier van veranderen, mbv Scrum, maakt het mogelijk om samen te verbeteren: medewerkers en managers. Het stimuleert zelf-organisatie en benut de kracht van de medewerkers om organisatiedoelen te bereiken. We gaan het gewoon doen in 2014: Sterktes gebruiken om op een Agile manier te veranderen!

Continue ReadingAgile Veranderen door sterktes te gebruiken