On October 22 I will do a full day workshop Valuable Agile Retrospectives at Agile Tour London. For registration please see the Agile Tour London training page.
Het succesvolle boek Waardevolle Agile Retrospectives is nu ook in paperback formaat beschikbaar op Bol.com.
In this guest blog post on BenLinders.com David Horowitz, CEO and Co-Founder of Retrium, explores why you should do continuous agile retrospectives and how you can do them to establish continuous improvement.
The Leanpub bundle Agile Retrospectives offers great books to do amazing Agile Retrospectives. Together these books will make your Agile retrospectives rock! Teams will love to do them :-) And now you can get these books with a significant discount :-).
I sometimes hear of teams that have stopped doing retrospectives because they didn't see any improvements. When I talk with them it often turns out that they didn't have good actions coming out of the retrospectives, or that the actions weren't done and kept coming back in the retrospective. No actions leads to no improvement. Here are some suggestions on what you can do to assure that you will have actions from retrospectives that are doable and that those actions get done.
I gave a well received keynote at the QCon Beijing conference, in which I explained why continuous improvement is essential to deliver value with agile. QCon Beijing was the largest QCon conference so far with over 1600 attendants.
People are often afraid to make mistakes. They do things to prevent that something might go wrong and avoid doing things that might fail. And if it does go wrong then they don't talk about it. Is it really bad if once in a while something goes wrong? If something can go wrong, let arrange for it to happen as soon as possible, because then you can quickly learn from it. Create a culture where failure is allowed so that we can all learn from it and find ways to make fewer mistakes!
2014 was a great year for me. I've helped organization to effectively deploy Agile and Lean and improve their ways of working, my first book became a bestseller and I've inspired professionals all around the world by sharing useful knowledge and experience on my blog and via InfoQ. Let's reflect on what 2014 has brought and do a futurespective to visualize the opportunities of 2015.
The aim of an agile retrospective is to define actions for the next iteration that will improve the way of working and help teams to deliver more value to their customers. This retrospective exercise can be used within agile frameworks like Scrum, SAFe, XP or Kanban to have teams agree upon the vital few improvement actions that they will do.
Agile werken kan je helpen om organisatiedoelen te bereiken. Agile tot een doel verheffen werkt meestal niet, het doel is om resultaten te bereiken, niet om agile te worden. Het is belangrijk om goed te weten waarom je de agility van je organisatie wilt vergroten en wat je met een agile werkwijze verwacht te bereiken.
Agile Retrospectives help teams to continuously improve to become better in what they do. As they are a learning experience for the team the atmosphere in a retrospective meeting is usually positive. But when there have been major problems in an iteration, maybe even conflicts between team members, then team morale can be low and negativism can occur in the retrospective meeting. This is the story of how a reader of our book on Valuable Agile Retrospectives dealt with negative issues in his retrospective.
Change is often hard. But it is also important and much needed. That is why agile software development suggest to frequently inspect and adapt and promotes the usage of retrospectives to continuously improve the things that teams do. Retrospectives help teams to make changes that stick in the organization, leading to sustainable improvement.