Scrum

We Want Agile Processes

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
Read more about the article Retrospectives for Teams with Multiple Customers

Retrospectives for Teams with Multiple Customers

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!

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!
Read more about the article Self-assessing How Agile You Are

Self-assessing How Agile You Are

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

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

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

Wat brengt 2014 ons? Agile en Lean!

Een nieuw jaar is begonnen. 2013 was een jaar met mooie resultaten met Agile, verbetering, workshops, advies en de publicatie van mijn 1e boek over retrospectives. Wat gaat 2014 ons brengen? Voorspellen is lastig, vooral als het om de toekomst gaat :-) Daarom geen voorspellingen, we gaan het gewoon doen: Meer resultaten met Agile en Lean!

Continue ReadingWat brengt 2014 ons? Agile en Lean!