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.

1. KANBAN
Overview of the competition

3. VISUAL CARD
SIGNBOARD
SIGNAL

4. General Theory Behind Kanban
We should know where everyone is coming from

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

6. SOME THINGS TO KEEP IN MIND:

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

8. Some Necessary Ingredients
Suggested absolute requirements for Kanban boards

9. Not Started Impeded
Status Columns
X1234

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%

17. TRELLO

18. NORMAL

19. RESIZED SMALL HORIZONTAL

20. RESIZED SMALL VERTICAL

21. DOZEN COLUMNS

22. TRELLO: TASK LAYOUT

23. TASK LAYOUT: COLOR LABELING

24. TASK LAYOUT: MOVING TASK

25. TASK LAYOUT: ARCHIVING TASK
INSTANT

26. KANBANERY

27. NORMAL

28. RESIZED SMALL HORIZONTAL
Collapsed Columns

29. RESIZED SMALL VERTICAL

30. DOZEN COLUMNS

31. KANBANERY: NEW TASK LAYOUT

32. NEW TASK LAYOUT: ESTIMATE

33. NEW TASK LAYOUT: DEADLINE

34. ADD NEW COLUMN

35. TASK TOGGLED OPEN

36. LEANKIT

37. NORMAL

38. RESIZED SMALL HORIZONTAL

39. RESIZED SMALL VERTICAL

40. DOZEN COLUMNS

41. LEANKIT: TASK LAYOUT

42. TASK LAYOUT: COLOR LABELING

43. TASK LAYOUT: MOVING TASK

44. STATUS LIMIT REACHED: TASK LEVEL

45. STATUS LIMIT REACHED: BOARD LEVEL

46. FILTERING

47. BUG REPORT

48. HELP FEATURES

49. CLEAR/UNCLEAR INDICATORS?

50. OPTIONS/SETTINGS

51. SEARCH

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

53. REFERENCE SITES
AGILE BOARD
http://www.agileboard.com/iagileboard.html
TRELLO
https://trello.com/board/welcome-board/4e7376ec43ea1d807700a089
LEANKIT
https://schubox.leankitkanban.com/Boards/View/16983313
KANBANERY
https://schubox.kanbanery.com/projects/6224/board#

54. SOME INTERESTING CASE STUDIES:
brought to us by a Kanban expert

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 >

57. “The Kanban board takes on
a life of it’s own”

58. “Scrum/Kanban Hybrid”

59. I KAN HAS BAN