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.
- +1 RT @TomJohannesBang: #leancoffeeoslo torsdag kl 08:00 @stockfleths @ketilj @storstad @turido @hauge2 @JHauglum @evjohnsen - posted on 01/05/2013 22:48
- RT @cwfreeman: Was told recently that we're in 'that' [bug-fixing] phase of the project. Can this no longer be a thing, please? - posted on 26/04/2013 09:13
- RT @erlingwl: 4 interesting topics covered in 4 x 10 mins at this morning's #leancoffeeoslo. Follow hashtag #leancoffeeoslo and join us ... - posted on 18/04/2013 11:33
- Topic 4: How to get effective transfer of knowledge when replacing ppl on the team? #leancoffeeoslo - posted on 18/04/2013 10:28
- Topic 3: Can electronic boards with "personal views" and "assigned responsibles" prevent team improvements? #leancoffeeoslo - posted on 18/04/2013 10:28
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 ...