Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start 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.

DeleteCancel

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.

No, thanks

Kanban 101

No description
by

Aaron Murrell

on 5 May 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Kanban 101

Kanban
Visualize Workflow
Limit Work in Progress
Measure and Optimize Flow
Recipe for Success
1. a just-in-time manufacturing process in which the movements of materials through a process are recorded on specially designed cards

2. any of the cards used for ordering materials in such a system
Kan-ban (kænbæn):n
Make Process Policies Explicit
When can new work be added?

Can low priority scope expire?

Different kinds of work go through
different processes?
Crystal Clear
Scrum
Agile Unified Process
Dynamic Systems Development
Method
Feature Driven Development
Extreme Programming
Focus on Quality
Reduce Work in Progress
Deliver Often
Balance Demand against Throughput
Prioritize
Reduce Variability
Iteratively Eliminate Waste
"Just in time Automation with a human touch"
Why Kanban?
Don't build features that nobody needs RIGHT NOW

Don't write more specs than you can code

Don't write more code than you can test

Don't test more code than you can deploy
Continuous Improvement at equilibrium with
Sustainable Pace!
vs
"Students who were assigned 7 digits were nearly twice as likely to choose the cake..."
Case Study: Microsoft XIT Team
155 day Lead time on new requests
New requests arriving uncontrollably
More than 90% of lead time was queuing
Mixed Sizes and Priorities of Work
"Why does agile development produce better
economic outcomes than other approaches?"
Pull System
Limit work in progress
Experiment with WIP
Visualizing the Workflow using a Kanban Board
Emergent Behavior with Kanban
Process tailoring per value stream
Tolerance for Process Experimentation
Decoupled Cadences or "Iterationless" development
Work scheduled by opportunity cost of delay
Classes of Service emerge
Quantitative Management
Spread of Kanban
Small teams merged for more liquid labor pools
Classes of Service
Expedite
Standard
Fixed Delivery
Date
Measure the rate of flow
Full transcript