This is my second Q&A post for my #Agile2014 session: How to improve Flow Efficiency, Remove the Red bricks! In this, my previous and upcoming posts I will answer some of the questions I have received as session feedback after the session.
Q2: The presentation gave a full demonstration of the issue and how to address the problem. However the only issue I had with it is that it is essentially teaching to have your highly skilled, highly paid people sit and wait for work when it is ready. I would like to see the real metrics when you consider the overhead of these highly skilled people. But in general, I think you did a really good job of pointing out the issue and ways to address it. Entertaining presentation as well.
Yes, I am proposing that for some organizations, based on their context, it is a valid business/operational strategy to focus more on having the flow units (e.g. user stories, features, MVP, project) being worked on all the time over having our highly skilled, highly paid people utilized all the time.
Thank you all of you who attended my #Agile2014 session: How to improve Flow Efficiency, Remove the Red bricks! In this, and upcoming posts (part 2) I will answer some of the questions I have received after the session.
Q1: I was hoping to better understand how to improve flow efficiency when the number of resources varies on our scrum process. For example, we have more developers than testers. We typically have a bottleneck in the test step. Not sure I got my answer.
This question is not necessarily a flow efficiency question. It may be more of a balance demand to capacity question. Nevertheless, let us explore the flow efficiency side first, as this was the main focus of the session. First, a short description of flow efficiency.
Here are some book recommendations for your summer vacation. I have divided them into four categories: The must reads!, Great reads!, Lean & Leadership and finally Change & Coaching
The must reads!
This is Lean by Niklas Modig, Pär Åhlström
Kanban by David J. Andersson
The Goal by Eliyahu M. Goldratt
Toyota Kata by Mike Rother
The Toyota Way by Jeffrey Liker
Great reads! Read more…
Best of DevSum presentation – What can traffic in Stockholm teach you about your development process?
Here is the slides for the presentation I gave at Best of DevSum in Gothenborg on the 14th of November.
Lean Kanban Central Europe 2011 presentation – What can traffic in Stockholm teach you about queuing theory?
Here is my slides from my presentation at Lean Kanban Central Europe 2011
Update: Audio is now added to the slides
This is the recording of my presentation at the 2nd Bathtub Conference where I talked about Queueing theory in software development
I try to read a lot of books but I’m not a fast reader. I also spend some time more or less every day walking the dog, doing grocery shopping, commuting to and from work and so on. I have found that listening to audio books and podCast are a great way to learn. Here is a list of highly recommended audio books I have read.
James P. Womack
- Lean Thinking- Banish Waste and Create Wealth in Your Corporation, Revised and Updated
- Lean Solutions- How Companies and Customers Can Create Value and Wealth Together
Stephen A. Ruffa
- Predictably Irrational- The Hidden Forces That Shape Our Decisions
- The Upside of Irrationality- The Unexpected Benefits of Defying Logic at Work and at Home
Eliyahu M. Goldratt
- The Goal- A Process of Ongoing Improvement- Revised Third Edition
- Beyond the Goal- Theory of Constraints
Dan & Chip Heath
John P. Kotter
- A Sense of Urgency
- The Heart of Change- Real-Life Stories of How People Change Their Organizations
- Our Iceberg is Melting- Changing and Succeeding Under Any Conditions
- Buy-In- Saving Your Good Idea from Getting Shot
Daniel H. Pink
- A Whole New Mind- Why Right-Brainers Will Rule the Future
- Drive- The Surprising Truth about What Motivates Us