Why dedicated Full-Time Scrum masters are hard to implement – and what’s the alternative

  • Post published:August 11, 2015

More and more organizations are implementing agile with Scrum. They define teams and assign Scrum masters to the teams to start working agile and become self-organized. Although agile looks easy, to implement the Scrum master role often turns out to be problematic. Let's discuss what makes it so difficult to work with full-time Scrum masters and explore the alternative of having technical people taking the Scrum master role.

Continue ReadingWhy dedicated Full-Time Scrum masters are hard to implement – and what’s the alternative

Getting Retrospective Actions Done

  • Post published:June 25, 2015

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.

Continue ReadingGetting Retrospective Actions Done

Retrospective Prime Directive in many languages

  • Post published:May 18, 2015

The retrospective prime directive is a sentence that is used by facilitators to establish safety in a retrospective meeting. Safety is crucial if you want people to speak up and be open, which is an important precondition to reflect and learn which is what agile retrospectives are all about. Since our book is being translated into many languages we now have translations of this unique and important statement.

Continue ReadingRetrospective Prime Directive in many languages

What if we fail?

  • Post published:April 18, 2015

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!

Continue ReadingWhat if we fail?

Guest blog: Retrospective Doughnut! A fun way to measure team’s response to Retrospectives.

  • Post published:April 2, 2015

Retrospective Doughnuts can be used to make the adoption rate of retrospectives and the value that they deliver visible. This support organizations in using retrospectives to establish a routine feedback loop leading to continuous improvement. A guest blog post from Mukyul Vyas.

Continue ReadingGuest blog: Retrospective Doughnut! A fun way to measure team’s response to Retrospectives.

How Futurespectives Help Teams to Reach Their Goals

  • Post published:February 10, 2015

Many agile teams are doing retrospectives at the end of their iterations to reflect on their way of working and find things that can be improved. But what if teams are starting up and trying to figure out how to do their work? A futurespective exercise can help teams teams to find ways to reach their goals, agree upon their way of working and define a Definition of Done.

Continue ReadingHow Futurespectives Help Teams to Reach Their Goals

A Retrospective of 2014 and Futurespective of 2015

  • Post published:January 15, 2015

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.

Continue ReadingA Retrospective of 2014 and Futurespective of 2015

Retrospectives in Remote Teams

  • Post published:December 23, 2014

When you are working with an agile team where people are not co-located you still want to do valuable agile retrospectives. As gathering everybody in one location for the retrospective is not feasible, you need to take a different approach. The dispersed team questions retrospective exercise is a variant of the questions-based retrospective for teams consisting of members working from different locations, for example team members working from home or working in different offices, countries or even continents.

Continue ReadingRetrospectives in Remote Teams