SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez nos Conditions d’utilisation et notre Politique de confidentialité.
SlideShare utilise les cookies pour améliorer les fonctionnalités et les performances, et également pour vous montrer des publicités pertinentes. Si vous continuez à naviguer sur ce site, vous acceptez l’utilisation de cookies. Consultez notre Politique de confidentialité et nos Conditions d’utilisation pour en savoir plus.
“All we are doing is looking at the timeline,
from where the customer gives us an order
to where we collect the cash. And we are
reducing the time line by reducing the non-
value adding wastes.
- Taiichi Ohno
•Maximize customer value
•Optimize the Value Stream
•Project - Product - Problem
•In groups of three people that don’t know
each other, introduce yourselves, then tell
what project you are working on, what
product or service your provide, what’s the
problem you are solving and for whom
•Extra points if you can do that for your
company and for you as a professional /
individual: what team are you part of?
What service do you provide? What
problem do you solve?
•In short: mostly everything is waste
•Muda: Not needed / not value adding
•Mura: Unevenness, irregular, unbalanced
•Muri: Overburden / irrational
Flow Efficiency = VAT / LT
Exercise: 30 minutes
• Client calls requesting a feature. PO schedules meeting within 1 or 2 weeks
(call time: 20 minutes)
• Meeting takes place (2 hours). PO writes brief.
• PO meets team within next week. Gets initial quotation (2 hours)
• PO schedules meeting with client within 1-2 weeks
• Meeting takes place. Client accepts (1 hour). PO schedules meeting of client
and team for requirements refinement (20 min call).
• Meeting takes place in 2 weeks. Refinement takes 4 hours.
• During the next 2 weeks, team will work in a final proposal (8 hours).
• When the proposal is done, PO will schedule a meeting with the client (1
weeks). Final proposal will be presented and accepted in this 2 hour
• PO will tell team to start development. Team will introduce it in the next
Sprint (starts in 1 week). They will dedicate 25% of their capacity during 4
2-week sprints to do it.
• Client will come to final demo (2 hours). Refinements and modifications will
be discovered. Team will dedicate 25% of their next sprint to them.
• Client will come to SP5’s demo (2 hours). Accepts.
• Team asks infrastructure department to release the feature into production.
They will schedule it on the next release, 1 week from now (4 hours)
What can be improved?
(15 minutes + 5 minute briefing)
Value Stream + Kanban
Rdy RdyOn On
Optimizing Value Streams
• Remove waste
• Remove impediments (flow!)
• Remove unnecessary steps
• Start earlier / parallelize
• Work in smaller / more frequent batches
• Remove bottlenecks (ToC)
• Subordinate to the pacemaker and free
• As a final option, only when all the others
have been done, add resources
How can we solve?
• Enforce value maximization, both by
communication, rewarding right behaviors
and pointing out wrong ones
• Enforce long term thinking & planning
• Involve leadership and form cross-
• Define relevant metrics
• Consider the hidden cost of “not doing”
This presentation is based upon the ideas and
work of many people. And while I’ve tried to
recognize copyrights and give credit and
attribution where possible, I cannot possibly
list them all, so if you feel like there’s
something that should be added, changed or
removed from this presentation, please drop
me an e-mail at
All drawings and materials in this presentation
are CC BY-NC-ND by Angel Medinilla. You are
free to use them in the terms of this license.