Intro to Kanban Workshop Flipchart Pages - Paul Klipp

! ! ! ! !

Introduction to ! !

!

!

!

!

!

!

K!A N B A N ! ! ! ! with Paul Klipp 

This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/.

What do we already know?" ! ! ! ! ! ! ! ! ! ! ! ! What do you we want to learn today? 


What is Kanban?"

! Principles" ! Start with what you do now! ! Respect the current process! ! Agree to pursue incremental, evolutionary ! change! ! Rules" ! Visualize workflow! ! Limit WIP! ! Manage flow! ! Make process policies explicit! ! Improve collaboratively using models and ! the scientific method! ! Implement feedback loops  This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/.

Types of Work" ! ! ! ! ! ! ! ! ! ! ! What can go on a task card?" ! !


Backlog

Coding

Testing

Done

! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! features take two days; testing takes one day; average of two bugs per feature  This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/.

Little’s Law"

! WIP! ! Cycle Time = ! ___________! ! ! Throughput ! !


Bottlenecks" ! Every system has them! ! Stable system = stable bottlenecks! ! Look for: !broken WIP limits! ! ! ! starved stages! ! ! ! ! ! Input Queue

Design

Dev

QA

Done

Ready

! ! ! ! ! ! ! ! ! ! ! ! ! !


Five Focussing Steps"

! ! Identify! ! Exploit! ! Subordinate everything else! ! Elevate! ! Prevent inertia (is there a new bottleneck)! !

source: The Goal by Goldratt"

! ! !


Metrics" ! Lead Time! ! ! ! Cycle Time! ! ! !

! ! !


Reading a Cumulative Flow Diagram (CFD) 


Waste" ! !

Muda! wasted effort

Mura! variability! unevenness

Muri! overburden

!


Cost of Delay"

! Normal! The sooner we do it, the sooner! we benefit!

! ! ! Expedite! This hurts every day that! we don’t have it!

! ! ! ! Fixed Date! It’s gonna hurt if we’re not ready!

! ! ! ! ! Intangible! someday we’ll need this


Quality Assurance Practices _________________________ Code Quality

Architecture

Is the solution the best? Are we following appropriate conventions?

Is the structure stable, extensible, maintainable?

Usability

Requirements

Does it make sense? Is it a pleasure to use?

Are we building the right thing?

Other

Ideally, practices should be explicit including who should do them and when. Higher value QA practices catch issues more quickly. The best keep them from ever happening.