Less is More with Retrospectives

The aim of agile retrospectives is to come up with improvement actions. Having too many actions from retrospectives makes it harder for teams to improve, it’s actually better to come up with less actions in stead of more in a retrospective. It’s quality over quantity for actions. Here’s some ideas on how to come up with less actions to get more done. Continue reading

Wat managers kunnen doen om agile en lean in te voeren

Ik zie regelmatig organisaties die besluiten dat ze agile en lean in willen voeren. Wat mij betreft een prima ontwikkeling, gezien de voordelen die een agile en lean werkwijze kan bieden. Waar het echter vaak mis gaat, is de manier waarop managers besluiten om agile en lean in te voeren: Top down, vooraf gepland, en met te weinig inbreng van de professionals. Dat moet en kan anders. Continue reading

Getting Into Reflection Mode

I chaired a session about getting into reflection mode at the Retrospective Facilitators Gathering 2016. In this session we discussed what facilitators can do to help people to look back and reflect in an agile / Scrum retrospective meeting or at other occasion where they want to learn from how they are doing. Continue reading

Verbeter Testen met Agile Retrospectives

Agile teams gebruiken retrospectives om continu te verbeteren. Verbeteracties richten zich vaak op de manier waarop het team samenwerkt om de productiviteit te verbeteren. Uit een retrospective kunnen ook acties komen om de kwaliteit van het product te verbeteren. Bijvoorbeeld door verbetering van de manier waarop er getest wordt. Continue reading

Agile retrospective exercise for a new team

RetrospectiveQuestion

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. Continue reading

Ontdek de Kwaliteiten van je Team met een Agile Retrospective

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. Continue reading

Guest blog: 4 Reasons Why to Focus on Scrum for the Success of Distributed Teams

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. Continue reading

Yes in agile means that you will deliver

NO and YES are two simple words, yet practice shows that professionals often have difficulties in using them. Actually it’s very easy, certainly when you want to work in an agile way. Dare to say NO when you are unsure if you can do what’s requested. When you say YES it means that you will deliver the product, on time with the right quality. Continue reading

Agile Retrospectives: Hoe vaak doe je ze?

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? Continue reading

Doing a retrospective when you can’t get the team to meet?

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. Continue reading

  • Ben Linders – Independent Consultant Agile, Lean, Quality, and Continuous Improvement

    Ben Linders
    Ik help organisaties om effectiever software te ontwikkelen. Neem contact op voor mijn diensten.

    I help organizations to effectively develop software. Contact me to hear about my services.