A huge team effort at the end of the sprint was the only reason we finished our user stories just in time for demo, but the hurry was at the expense of quality. By introducing WIP limits, the team effort was more evenly distributed over time – and the quality improved.
- RT @az1: @JornHunskaar thank you. This post in 6 words: bias, feedback, forecast, scale, expectations, control. In rainbow colours. - posted on 18/09/2014 15:17
- Inside a Lead Time Distribution, another great post by @az1. I'll get more coffee and read it again. #Kanban http://t.co/fHDPIIA3FL - posted on 18/09/2014 09:40
- Analyzing the Lead Time Distribution Chart. Great post by @az1 #Kanban http://t.co/t8l0EYPR25 - posted on 15/09/2014 09:38
- RT @ketilj: Reducing batch size is key to reduce risk when releasing software - posted on 13/09/2014 08:50
- We want to know what the minimal completed task looks like and then do that. Anything beyond is too much work. #agile http://t.co/ZlLowxSWp2 - posted on 09/09/2014 18:27
- Eliminate the voice inside your head. Read with your eyes. ONLY. #todo #notetoself #gtd #speedreading http://t.co/hMItxg4mXb - posted on 09/09/2014 18:11
Oslo Lean CoffeeAre you interested in lean and agile? Come meet us at Oslo Lean Coffee to share your thoughts and experiences!
- Dot-game for exploring WIP limits
- The Impediments Game
- Experimenting with Daily Standups
- How To Read a Cumulative Flow Diagram
- Running a Lean Coffee
- Facilitating An OpenSpace Conference
- Blocked tickets: WIP or not?
- How to use powerpoint for your product backlog
- Cumulative Flow Diagram – How to create one in Excel 2010
- Improvements on using a simple kanban for effective meetings ...