Category: Lean & Kanban

16 May 2018 / Agile & Scrum
The 5 liberating whys

  Object of Play Some teams are struggling with re-enforcing behaviors and can’t seem to find why they can’t find the cause. If teams seem unable to reach the goal for their iteration, it’s good to go hunting for root causes.  The 5 why’s technique was formally developed in the 1930s by Sakichi Toyoda, one of the fathers of the Japanese industrial revolution. Here is...

25 January 2017 / Agile & Scrum
The Shocking Truth about Firefighting in I.T. Organizations!

Why are there so many IT people out there who have the feeling they're actually a firefighter? Why do they have the feeling to be jumping from one burning house to another? Why do they have the feeling work is driven by fire alarms? Why is it that the loudest voice in the office, the biggest fire, gets things done? A bunch of questions I...

23 March 2016 / Agile & Scrum
Surprise Surprise: Benefits of Cross-Functional Teams

Stage Backlog Refinement session.  Purpose  Our Product Owner came up with new stories to be estimated. 14 to be precise.  It required some preparation however.  We have 2 teams, and they do the Backlog Refinement together.  Around 20 people in one room, partly offshore, estimating together is quite a challenge! Meeting Progress The meeting was slowly progressing and at the same time the activity was...

10 February 2016 / Agile & Scrum
Splitting Backlog Items Part 2: Who

After XPDays 2015 in our session “Sharpen your story splitting skills”, we concluded that some additional framing was needed for our useful deck of cards with splitting patterns.  This article is the successor of the "Splitting Backlog Items Part 1: When" post, and will handle about the people and aims to help you understand dysfunctions that make item splitting a pain and the reasons for good practices. Background Quite frequently we see...

3 February 2016 / Agile & Scrum
Splitting Backlog Items Part 1: When

At XPDays 2015, we presented the session “Sharpen your story splitting skills”. In the end people left with the shared knowledge from the other attendents and as a cherry on the cake a useful deck of cards with splitting patterns.  This session can be called a success, but still I had the feeling this subject needed more attention to effectively help people. When the big stories do not fit...

27 January 2016 / Agile & Scrum
Why Sprint n-1 Analysis is a BAD idea…

(commonly known as the Scrummerfall anti-pattern) Consider the following familiar situation The team has taken a story in the sprint, and during the sprint, shit hits the fan. They rework, rework again several times to get it to done. Then the “we-could-have-avoided-this” feeling enters the minds of the team...  In the Retro the conclusion is clear:   We could have avoided this!! We had to analyse this better!...