Kanban market overview

1,877 views

Published on

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.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,877
On SlideShare
0
From Embeds
0
Number of Embeds
652
Actions
Shares
0
Downloads
17
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Kanban market overview

  1. 1. KANBANOverview of the competition
  2. 2. VISUAL CARDSIGNBOARD SIGNAL
  3. 3. General Theory Behind Kanban We should know where everyone is coming from
  4. 4. 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 ramificationsLEAN PRINCIPLES: Kaizen principle of Lean Agree to overcome any obstacles Theory of Constraints: "Process of Ongoing Improvement" to implementation
  5. 5. SOME THINGS TO KEEP IN MIND:
  6. 6. • 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
  7. 7. Some Necessary IngredientsSuggested absolute requirements for Kanban boards
  8. 8. Not Started Impeded Status ColumnsX1234
  9. 9. Not Started Impeded In Progress Done 4 Limit Indicators ! 2 3X1234X5678X8901
  10. 10. Not Started Impeded In Progress Done 4 2 3 Y1234 TASK TasksX5678 Y5678 Status TypeX8901 Y8901 Status Type
  11. 11. Not Started Impeded In Progress Done 4 2 3X1234 Identifying # 8 Y1234 8 TITLE 4 Status Type TITLE 1 Title/Description Status TypeX5678 4 Y5678 8 TITLE 5 TITLE 2 Status Type Status TypeX8901 16 Effort TITLE 6 Status Type
  12. 12. Not Started Impeded In Progress Done 4 ! 2 Warning Indicators 3X1234 8 Y1234 8 TITLE 4 TITLE 1 Status Type Status TypeX5678 4 Y5678 8 TITLE 5 TITLE 2 Status Type Status TypeX8901 16 Y8901 4 TITLE 6 TITLE 3 Status Type Status TypeX1234 8 NEW TASK Status Type Warning Indicators
  13. 13. Not Started Impeded In Progress Done 4 ! 2 3X1234 8 Y1234 8 TITLE 4 TITLE 1 Status Type Status TypeX5678 4 Y5678 8 TITLE 5 TITLE 2 Status Type Status TypeX8901 16 Y8901 4 TITLE 6 TITLE 3 Status Type Status Type I NEW TASK Pull System Pull not Push
  14. 14. Not Started Impeded In Progress Done 4 ! 2 3X1234 8 Y1234 8 TITLE 4 TITLE 1 Status Type Status TypeX5678 4 Y5678 8 TITLE 5 TITLE 2 Status Type Status TypeX8901 16 Y8901 4 TITLE 6 TITLE 3 Status Type Status Type I NEW TASK Pull System Rules to keep flow going one direction
  15. 15. Trips through processKanban should improve performance by team over time { trip #1 trip #2 trip #3 0% x time 100%
  16. 16. TRELLO
  17. 17. NORMAL
  18. 18. RESIZED SMALL HORIZONTAL
  19. 19. RESIZED SMALL VERTICAL
  20. 20. DOZEN COLUMNS
  21. 21. TRELLO: TASK LAYOUT
  22. 22. TASK LAYOUT: COLOR LABELING
  23. 23. TASK LAYOUT: MOVING TASK
  24. 24. TASK LAYOUT: ARCHIVING TASK INSTANT
  25. 25. KANBANERY
  26. 26. NORMAL
  27. 27. RESIZED SMALL HORIZONTAL Collapsed Columns
  28. 28. RESIZED SMALL VERTICAL
  29. 29. DOZEN COLUMNS
  30. 30. KANBANERY: NEW TASK LAYOUT
  31. 31. NEW TASK LAYOUT: ESTIMATE
  32. 32. NEW TASK LAYOUT: DEADLINE
  33. 33. ADD NEW COLUMN
  34. 34. TASK TOGGLED OPEN
  35. 35. LEANKIT
  36. 36. NORMAL
  37. 37. RESIZED SMALL HORIZONTAL
  38. 38. RESIZED SMALL VERTICAL
  39. 39. DOZEN COLUMNS
  40. 40. LEANKIT: TASK LAYOUT
  41. 41. TASK LAYOUT: COLOR LABELING
  42. 42. TASK LAYOUT: MOVING TASK
  43. 43. STATUS LIMIT REACHED: TASK LEVEL
  44. 44. STATUS LIMIT REACHED: BOARD LEVEL
  45. 45. FILTERING
  46. 46. BUG REPORT
  47. 47. HELP FEATURES
  48. 48. CLEAR/UNCLEAR INDICATORS?
  49. 49. OPTIONS/SETTINGS
  50. 50. SEARCH
  51. 51. 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
  52. 52. REFERENCE SITES AGILE BOARD http://www.agileboard.com/iagileboard.html TRELLOhttps://trello.com/board/welcome-board/4e7376ec43ea1d807700a089 LEANKIT https://schubox.leankitkanban.com/Boards/View/16983313 KANBANERY https://schubox.kanbanery.com/projects/6224/board#
  53. 53. SOME INTERESTING CASE STUDIES: brought to us by a Kanban expert
  54. 54. “We had tripled productivityand reduced the turnaroundtime by 90%”-David Anderson, author of “ Kanban -Successful Evolutionary Change forYour Technology Business”, speaking ofthe introduction of Kanban into theworkflow at Microsoft
  55. 55. “Anything that got into the system that then got canceled, got reported as wasted capacity.” See me discuss it here >
  56. 56. “The Kanban board takes on a life of it’s own”
  57. 57. “Scrum/Kanban Hybrid”
  58. 58. I KAN HAS BAN

×