Kanban is a Lean methodology used by agile development teams as a pull system for quick cycle times and tasking. This presentation is meant as a primer on Kanban.
5. Gain agreement on the problem
Gain agreement on the direction
for a solution
Gain agreement that the solution
solves the problem
Agree to overcome any potential
negative ramifications
LEAN PRINCIPLES: Kaizen principle of Lean
Agree to overcome any obstacles
Theory of Constraints: "Process of Ongoing Improvement"
to implementation
7. • ITERATIONS ARE OPTIONAL
• If you have a need for it in your context.
• ESTIMATION IS OPTIONAL
• If you have a need for it in your context.
• KANBAN IS JUST A PROCESS TOOL
• There is no such thing as a universally good or
bad tool
• It all depends on your context
• KANBAN IS ABOUT MANAGING WORKFLOW
• It drives change
• Process
• Visualize it
• Introduce WIP limits
• Measure the lead time
10. Not Started Impeded In Progress Done
4 Limit Indicators
! 2 3
X1234
X5678
X8901
11. Not Started Impeded In Progress Done
4 2 3
Y1234
TASK Tasks
X5678 Y5678
Status Type
X8901 Y8901
Status Type
12. Not Started Impeded In Progress Done
4 2 3
X1234
Identifying #
8 Y1234 8
TITLE 4
Status Type
TITLE 1 Title/Description
Status Type
X5678 4 Y5678 8
TITLE 5 TITLE 2
Status Type Status Type
X8901 16 Effort
TITLE 6
Status Type
13. Not Started Impeded In Progress Done
4 ! 2 Warning Indicators
3
X1234 8 Y1234 8
TITLE 4 TITLE 1
Status Type Status Type
X5678 4 Y5678 8
TITLE 5 TITLE 2
Status Type Status Type
X8901 16 Y8901 4
TITLE 6 TITLE 3
Status Type Status Type
X1234 8
NEW TASK
Status Type
Warning Indicators
14. Not Started Impeded In Progress Done
4 ! 2 3
X1234 8 Y1234 8
TITLE 4 TITLE 1
Status Type Status Type
X5678 4 Y5678 8
TITLE 5 TITLE 2
Status Type Status Type
X8901 16 Y8901 4
TITLE 6 TITLE 3
Status Type Status Type
I
NEW TASK Pull System Pull not Push
15. Not Started Impeded In Progress Done
4 ! 2 3
X1234 8 Y1234 8
TITLE 4 TITLE 1
Status Type Status Type
X5678 4 Y5678 8
TITLE 5 TITLE 2
Status Type Status Type
X8901 16 Y8901 4
TITLE 6 TITLE 3
Status Type Status Type
I
NEW TASK Pull System
Rules to keep flow going one direction
16. Trips through process
Kanban should improve performance by team over time
{
trip #1
trip #2
trip #3
0% x time 100%
52. WHAT FEATURES ARE MISSING?
• Cross-product and/or status sharing
• Ability to D&D a task a long distance
• Connectivity with other tools (calendar, lists?)
• Chart/Report integration directly inside the board
• Lack of well-designed & comprehensive types of
reporting (minimum treatments only)
• Ways to ‘split’ a single board into parts
55. “We had tripled productivity
and reduced the turnaround
time by 90%”
-David Anderson, author of “ Kanban -
Successful Evolutionary Change for
Your Technology Business”, speaking of
the introduction of Kanban into the
workflow at Microsoft
56. “Anything that got into the
system that then got
canceled, got reported as
wasted capacity.”
See me discuss it here >