Lean learning cycle

How can you make Lean work for you in different challenges, different environments and disciplines?
Looking for the logic and practical roadmaps to help you on your Lean journey?
Come to this Learning Session where you will learn about:
• the 8 key questions that guide companies in their Lean journey,
• about OSKKK, a practical roadmap for any Lean journey, big or small.
This Learning Session provides more in-depth knowledge and practical know-how for you as a Lean Leader and Practitioner.
The 8 Key questions look at the real business challenges organisations face, and which Lean methods and countermeasures can be applied for which kind of challenges. OSKKK stands for Observe-Standardize-Kaizen1-Kaizen2-Kaizen3 and provides you with a hands-on practical guide to work with your team.
A number of practical examples will be shown so you can see how these concepts work out in real life.

He serves on the advisory board of a number of technology startups, and has consulted to new and established companies as well as venture capital firms. In 2010, he was named entrepreneur-in-residence at Harvard Business School and is currently an IDEO Fellow. Previously he co-founded and served as CTO of IMVU, his third startup. In 2007, BusinessWeek named him one of the Best Young Entrepreneurs of Tech. In 2009, he was honored with a TechFellow award in the category of Engineering Lean Startup methodology has been written about in The New York Times, The Wall Street Journal, Harvard Business Review,Inc. (where he appeared on the cover), Wired, Fast Company, and countless blogs. He lives in San Francisco.

Well, first you need to perceive your project as a value stream. Value stream mapping can be an important tool for project management processes improvement. Then you need to ensure that the value is specified from the customer point of view. Project managers must also address those wastes by founding the best possible environment for its project team members. He will have to involve functional managers and to sensitize them so to eliminate wastes and to ensure project success. Finally, the project manager must manage customer's intimacy. Possibly, an extreme improvement would be that the project manager collocates with his customer.

If we let the person who’s best at performing the “specify” function handle more of that work, then we may also need to coordinate handoffs between ourselves. Adding the specify-complete column communicates to the team that a work item which was previously in the specify state is now ready to be pulled by anyone who wants to move it to the execute state. Work that is still in the specify state is not eligible to be pulled yet. If the owner of a ticket in the specify state wants to hand it off, he can put it in the complete buffer. If he doesn’t want to hand it off, he can move it directly into the execute state as long as capacity is available. It might be that the execute state is full, and the only eligible work is to pull another ticket from the ready queue into specify.

This is a good question. First, one lifecycle clearly does not fit all. Teams find themselves in a unique situation: team members are unique individuals with their own skills and preferences for working, let alone the scaling/tailoring factors such as team size, geographic distribution, domain complexity, organizational culture, and so on which vary by team. Because teams find themselves in a wide variety of situations shouldn’t a framework such as DA support several lifecycles? Furthermore, just from the raging debates on various agile discussion forums, in agile user groups, at agile conferences, and even within organizations themselves it’s very easy to empirically observe that agile teams are in fact following different types of lifecycles.

Lean learning cycle

lean learning cycle

If we let the person who’s best at performing the “specify” function handle more of that work, then we may also need to coordinate handoffs between ourselves. Adding the specify-complete column communicates to the team that a work item which was previously in the specify state is now ready to be pulled by anyone who wants to move it to the execute state. Work that is still in the specify state is not eligible to be pulled yet. If the owner of a ticket in the specify state wants to hand it off, he can put it in the complete buffer. If he doesn’t want to hand it off, he can move it directly into the execute state as long as capacity is available. It might be that the execute state is full, and the only eligible work is to pull another ticket from the ready queue into specify.

Media:

lean learning cyclelean learning cyclelean learning cyclelean learning cyclelean learning cycle