Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Do you really want to delete this prezi?
Neither you, nor the coeditors you shared it with will be able to recover it again.
Make your likes visible on Facebook?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
Kanban in 5 minutes
Transcript of Kanban in 5 minutes
WANT Predictability Process Excellence Reduced Risk Make promises you can deliver on, time after time after time Compete on the basis of Better Decisions Faster make Effective Why does speed makes us more effective? Because in order to focus on speed rather than just throughput we are forced to deal with problems. This is Lean at its core. Versatility in order to focus firepower on the most important things at the moment
In order to be able to quickly respond to changing needs Obstacle Removal so fast flow can be maintained We want to have maximum visibility to risks, as well as enable tight feedback loops in order to surface maximum risk early on, and have a chance to deal with it. Addressing Bottlenecks Stop Starting start Finishing What Visualize work Limit Work in Process Measure and optimize Flow Explicit Policies video of jumping control chart, CFD How do Agile in Agile Minimal steps needed to start improvement engine then let the next steps emerge Why Classes of Service Pull Priorities Definition of Done Swimming Lanes As you can imagine, this is not trivial to make happen. Focusing on fewer things is HARD! Typical challenges are specialization, obstacles that block the work, and bottlenecks. All are things we typically sweep under the carpet and just take on more work to stay utilized. The first step in creating a Kanban system is to visualize the work and its flow. Identify the work items, steps from start to finish, and enumerate all work in the system. This is visualized on Kanban boards - Each item is a card. Each Step is a Vertical Lane. Start to use the kanban board as your main system to track work. You will start noticing things you weren't aware of and improving already. BUT don't stop here... the really good stuff is yet to come... WARNING: Some teams do stop here. They are only doing kanban partially and are not really getting the benefits of the Kanban change management system. Kanban is about Facing the Pain & Improve Collaboratively
(Using Models) Kanban doesn't tell you which model to use, is just an enabler for improvement, and is highly compatible with the above YOU choose? People ask me "what is the diff between Lean & Kanban?"
Answer: Lean is a destination,
Kanban is a means to get there David J Anderson
@AgileManager http://twitter.com/#!/agilemanager @YuvalYeret Based on Better Data, Visibility, and Explicity Policies enabling decentralized decision-making First, Lets see what happens before we limit Work in Process (WIP)... Queues Fill Up Work is Trashed as there is no capacity to process it Swarm to deal
with huge inventory We get a force/policy that drives the system to prefer flow over inventory, and gets things out the door faster Where DOING something
about it Complex Enterprise Software Development Software Maintenance Knowledge-Intensive Service Operations Kanban is quite insensitive to context, but currently hotspots of practice seem to be: Program & Portfolio Management Highly Agile SaaS Operations Limited WIP and the Kanban Change Management have quite general applicability. Items can be Tasks, Features, Projects, Assignments, Incidents, whatever... We quickly flush out issues that affect our performance with Visibility and Clarity that are hard to ignore... Bottlenecks, Defects, Variability, etc. and we have a system that encourages us to By reducing amount of change needed up front, and de-emphasizing roles and organizational structures... Continuously Improve on factors with clear impact Kanban is an excellent catalyst to a more Lean/Agile culture Changes in roles and structures might emerge from actual need and context Learn More http://www.limitedwipsociety.org/ http://agilesparks.com/kanban http://www.kanban101.com/ Personal Productivity With Limited WIP... kanban changes things for the better Kanban works Kanban Works Integrated HW and SW Product Development / System Houses http://yuvalyeret.com/category/kanban/ you DO in Kanban http://www.leankanbanuniversity.com/ http://www.leanssc.org/ Through continuous improvement of Speed and Agility