Built in Quality by Michael Ballé - Lean IT Summit 2013

6,043 views

Published on

Do you use kanban to visualize workflow, measure and manage flow, limit work in progress...? This is not why Taichi Ohno invented kanban! Kanban is a tool of Kaizen: The point of kanban is the discipline of learning everytime we reduce the batch.
Through the example of an Agile team, Michael Ballé from Institut Lean France explains how the company manager started involving everyone in the problem solving.
Michael Ballé's presented "Lean or Agile: using kanban to build in quality" at the Lean IT Summit 2013. Watch the video here: http://www.youtube.com/watch?v=BBANsmeam8w&list=UUS_BXp5Zg9td-ZfczI1BgZw&feature=share&index=17
Discover more Lean IT stories on www.lean-it-summit.com

Published in: Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
6,043
On SlideShare
0
From Embeds
0
Number of Embeds
4,096
Actions
Shares
0
Downloads
89
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Built in Quality by Michael Ballé - Lean IT Summit 2013

  1. 1. Build in Quality with Kanban Dr. Michael Ballé © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  2. 2. Agile development? Start lean © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  3. 3. Purpose Agile Lean Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between selforganizing, crossfunctional teams. From Wikipedia Lean is a series or related activities aimed at improving safety, quality, flexibility and productivity through eliminating waste by involving all people all the time in problem solving. From Taiichi Ohno © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  4. 4. Lean & agile LEAN DELIVERY UX COCONSTRUCTION TEAMWORK AGILE HUMAN INTERFACE © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  5. 5. Leap of faith Agile • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan Lean In order to develop products, first you have to develop people © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  6. 6. Built-in-quality Quality at every step Quality of customer experience © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  7. 7. Built-in quality I can judge OK vs. NOK on the spot, I can move to the next step with certainty, I can be confident Make every customer smile, every day on every product Quality of customer experience © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  8. 8. What is the problem? Start lean © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  9. 9. Voice of customers © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  10. 10. Kanban? 1. Visualize workflow 2. Limit work-in-progress 3. Measure and Manage Flow 4. Make process policies explicit 5. Use models to recognize improvement opportunities © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  11. 11. And burn-down charts? • Work through that backlog! • Make progress visible • Check progress against predictions • Cut the scope? Extend the schedule? © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  12. 12. Let’s think lean Are we making the right product? Are we developing people the right way? © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  13. 13. Don’t argue with one-piece-flow • Only one task at a time! • Because of downtime, here, you can see three slots = two too many • Task by task is the only way to really focus on QUALITY © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  14. 14. Visual management is about learning from seeing problems, not scheduling • Engineers used to keep projects on their desk, • Now in the kanban board, one-piece-flow • It’s an anti-boss technique to avoid asking for miracles • It doesn’t solve capacity or flow issues © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  15. 15. Develop people by solving problems one-by-one together Visualize activities Study countermeasures Formulate problems Seek root cause © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  16. 16. Lead-time control: ask ‘why?’ PLANNED ACHIEVED CORRECTLY ON TIME LATE FAILED © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  17. 17. Backlog control: ask ‘why?’ • The parking lot holds the backlog – it’s a stock • Items are picked as needed • This is where capacity issues appear © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  18. 18. Formulate problems • Specify problems (one per day) • What did we stumble on? • What is the immediate cause? • What can we do to fix it quickly? • What is the possible root cause? © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  19. 19. Learning to see!!! © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  20. 20. Write standards • At code level • NOT procedures • But detailed ways to do specific jobs • With specific tricks of the trade © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  21. 21. Teach standards • Identify core coding tasks each person does every day • Define a team way of doing so • Teach every person • Challenge and improve © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  22. 22. Hansei • Once the code is delivered and accepted ? • Was it really what they wanted? • Are they pleased with it when they use it • What did we get right? What did we miss? © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  23. 23. Understanding value • Software = product • What are customers preferences? • How good are we at satisfying these preferences? • What technical choices do we need to challenge? © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  24. 24. Tech innovation Before After • Human Interface developed in house • Vision separated from machine control • Vision and machine control and interfaces seen as one block • Framework Human Interface is Pharma standard, to be purchased • No make/buy architecture • Make/buy architecture © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  25. 25. Not easy! Managers must be teachers What does the world look like from up here? • Must be able to envisage ideal situation • And to identify waste • To come up with kaizen ideas together • And experiment quickly with the team • In a worksite willing to accept changes • So we develop the kaizen spirit, every one, every day © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  26. 26. The CEO must master lean leadership © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  27. 27. Lean lessons STRATEGY STRUCTURE SYSTEMS IMPROVE: SAFETY QUALITY FLEXIBILITY PRODUCTIVITY + CONTINUOUS IMPROVEMENT INITIATIVE LEAN TOOLS LEAN TOOLS to involve EVERY ONE EVERY DAY STRATEGY ORGANIZATION SYSTEMS © Copyright Institut Lean France. Textes et illustrations tous droits réservés
  28. 28. Thank you, any questions? © Copyright Institut Lean France. Textes et illustrations tous droits réservés

×