Tom Poppendieck

+ Follow
since Oct 03, 2006
Cows and Likes
Total received
In last 30 days
Total given
Total received
Received in last 30 days
Total given
Given in last 30 days
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Tom Poppendieck

Chu -

Your approach may already be pretty lean as you describe frequent delivery of small increments of capabilities.

To look more deeply, look at the subtitle, " - From Concept to Cash" A lean approach will work to minimize Cycle Time from when a capability is requested to when it is in production. If things sit in a big queue waiting for you to get started to them or if there is a long integration, testing and deployment process after you complete "your part" then you have opportunities to get much better.

Similarly, if you are working on many small projects at the same time, then you would probably be taking more time than necessary to deliver each one. The critical measure is elapsed time, not applied time. The focus is on the throughput of delivered benefit (cash flow), not on utilization of applied people.

In our classes, we often ask how many people have ever been a member of a high performance team and usually a handful of people say they have. Then we ask how many have ever been a member of a high performance work group and the response is usually laughter. The idea that a group of people merely doing tasks someone tells them to do without passion and mutual commitment would achieve outstanding results in addressing a complex situation is wishful thinking.

We invested heavily in refactoring the text to remove duplication, to communicate clearly, and verifying by testing in our classes that the discussion was effective in addressing the issues they presented us with.
Gian -

We see many large and small organizations faced with serious competition adopting Lean in other areas of their manufacturing, office processes, logistics and supply chain processes and usually, they run into IT as a barrier to making improvements in their operations in other areas so they look into applying Lean to their software development. Lean is a system of management, not a collection of practices or a methodology. The starting point is to understand Lean thinking. The last slide in our classes lists 7 books we find most valuable to address issues commonly faced in implementing Lean in their software development work.

1. Taiichi Ohno - "Toyota Production System" - The book from the person who initially put together the ideas we now call Lean.

2. "Lean Software Development - An Agile Toolkit" - 21 thinking tools for applying Lean thinking to software development.

3. Michael Kennedy - "Product Development for the Lean Enterprise" - A business novel similar to Goldratt's "The Goal". Software development is much more like product development than manufacturing. Kennedy reports how Toyota does PRODUCT development.

4. Mike Cohn "Agile Estimating and Planning" - a masterpiece which lays out approaches to ensuring reliable delivery by effective application of agile techniques.

5. Michael Feathers - "Working Effectively with Legacy Code" - A fundamental practice of lean is mistake proofing processes so mistakes do not cause defects and slow the work. Agile uses TDD as a major tool to mistake proof its work and ensure that design decisions are not inadvertently broken by later work. This is notoriously difficult for legacy systems which we define as those which were not developed using TDD. Michael Feathers offers powerful strategies for dealing with this situation.

6. Rick Mugridge and Ward Cunningham - "Fit for Developing Software" - Xunit tests specify the behavioral design intent of the people writing the code. Fit Tests specify the behavioral design intent of the team members who are designing the product or business process. Rick and Ward offer a marvelous introductory book which both explains how Fit works (including Fit Library extensions) and how Fit works for an agile team in focusing interaction between the "customer" members and the "implementor" members of the team.

7. "Implementing Lean Software Development - From Concept to Cash" - The topic of our class which shares what we have learned from the organizations we have interacted since we published our first book.

Depending on your specific context and problems, we often recommend other books as well.
When it comes to effectively eliminating waste and delivering value to the customer, we are all beginners, even Toyota. Our books are intended to help people make effective decisions about how to deliver real value as a whole team. Many teams will include relative beginners at the start. This state will not last too long if the team frequently delivers working, tested, integrated, deployment ready code. Studies have shown that the maturity and effectiveness of a developer is related to the number of release cycles they have participated in, not to the length of time they have been doing software.