Kanban
Integrating Lean Into Software Project Delivery
Why should I care• Improve current process (in
increments)• Reduce task switching• Detect bottlenecks• Predict instead of react• Priorities change rapidly
Origins
Photo By ColinCC BY-SA
What is Kanban1. Visualize workflow2. Limit work in progress3. Manage flow4. Make Policies explicit5. Feedback loops6. Evaluate improvement with models
Key Concepts
Photo By badrkhanCC BY
Story 1 Story 2Story 3 Story 4
Story 5Story 6
Story 7
Story 8
Story 9
Workflow Visualization
Workflow
Backlog Develop QA Deploy Done
Priority
WIP Limits• Limit work in progress for each
activity• Reduce context switching• Expose bottlenecks– Upstream tasks – Drives pulling
• Forces addressing blocked items
WIP Workflow
Story 1 Story 2Story 3 Story 4
Story 5Story 6
Story 7
Story 8
Story 9
Backlog Develop QA Deploy Done6 3 3 2
Story 10
Story 11
Flow Management (Measure)
• Every work item timed per state– Outliers may expose problems with work
breakdown
• Measure lead and cycle time• Keep a cumulative flow diagram– See cycle time over project’s life– Predict based on trends
Cumulative Flow Diagram
Story 1 Story 2Story 3 Story 4
Story 5Story 6
Story 7
Story 8
Story 9
Backlog Develop QA Deploy Done
7/31
/14
8/1/
14
8/2/
14
8/3/
14
8/4/
14
8/5/
14
8/6/
14
8/7/
14
8/8/
14
8/9/
14
8/10
/14
8/11
/14
8/12
/14
8/13
/14
8/14
/14
8/15
/14
8/16
/14
8/17
/14
8/18
/14
8/19
/14
8/20
/14
0
5
10
15
20
25
30
BacklogDevelopment2QADeployDone
Lead Time Cycle Time
WIP
Remain
Explicit Process Policies• Start with existing policies • Definition of done• Visible• Explicit policies are a handhold for
change.• Leverage your tools
Process Improvement• Hold retrospectives• Listen to the team• Watch the data• Don’t hesitate to adjust• Revert changes that don’t work
Sample Policies
Develop Feature
• Code is reviewed by another developer
• Unit test coverage at 80%
• Design impacts documented
Test Feature
• Integration tests reviewed by other QA developer
• Test cases documented in test case managament tool.
• Feature reviewed with BA to ensure completeness.
Incremental Improvement• Periodically review the process • Follow the data– Set goal and measurement– Data should determine success or failure
• Retrospectives should influence process
Real world examples
PhotoBy Super touristCC BY
Scrum Development
Cross-func matrix enterprise team
Cross-func evolved
IT Operations
Q&A
“Sometimes the questions are complicated and the answers
are simple.” ― Dr. Seuss
