Kanban 101
Jul. 13, 2010•0 likes•7,267 views
Report
Business
Technology
Education
Introduction to Kanban for Knowledge Work: Kanban is emerging in Software Development and IT Operations as a method of improving transparency, predictability, and value. Learn how to get started with Kanban. See how Kanban can help you achieve the benefits of Pull, Value-Focus, and Capability-Improvement. Find out if Kanban is right for you.
Dennis StevensFollow
More Related Content
What's hot
How to start an Agile TransformationFranky Redant
Agile 101beLithe
What is Scrum?Fredrik Fjällström
Overview of Agile MethodologyHaresh Karkar
Agile Methodology in Software DevelopmentRaghav Seth
Scrum ProcessJohn Lewis
Viewers also liked
Kanban six core practicesAnders Beskow
Kanban 101 - An Introduction to Planning with Little's LawJack Speranza
Personal Kanban 101Jim Benson
Keep It Lean - TCUK 2015Mattias Sander
OOP 2012 - Kanban at Scale and why traditional approaches set you up for failureDavid Anderson
2014 02 kanbans not-so-hidden agendas 2Mike Burrows
Similar to Kanban 101
Fllow con 2014 gbgruver
Kanban Intro & OverviewJeff Kosciejew
DevOps and AWSShiva Narayanaswamy
Continuous DeploymentBrian Henerey
2014 toronto-torbugc.titus.brown
Bugfest!TechWell
![[Webinar] Test First, Fail Fast - Simplifying the Tester's Transition to DevOps](https://cdn.slidesharecdn.com/ss_thumbnails/testfirstfailfastfinal-170323164615-thumbnail.jpg?width=2048&height=1162&fit=bounds)
More from Dennis Stevens
Agile2013 sustainable changeDennis Stevens
Beyond functional silos with communities of practiceDennis Stevens
Agile and the nature of decision makingDennis Stevens
Agile FundamentalsDennis Stevens
Coffee maker workshopDennis Stevens
Deciding what to buildDennis Stevens
Recently uploaded
2023-09 Bloomerang Academy Text Fundraising Presentation.pdfBloomerang
James Feldman - AII Powered Business Tools.pdfSOLTUIONSpeople, THINKubators, THINKathons
California Carpet Stewardship Program Q2 2023 ResultsCarpet America Recovery Effort
Industrial Tech Startups In The SF Bay AreaChristian Dahlen
Eddie Tofpik's TA Presentation at SEEMT Sep 2023TOFPIK
You Don't Have to Be Big to Leverage Data - Lessons and Confessions from a Fo...saastr
Kanban 101
- 1.
- 2.
- 3.
- 4.
- 5.
- 6.
- 7.
- 8.
- 9.
- 10. Manual Testing Okay
- 11. PO Acceptance
- 12. Doco Complete
- 13. Design Complete
- 14. Test Case Examples Done
- 15. UIX Input Ready
- 16. Code Complete
- 17. Source Checked In
- 18. Unit Tests Green
- 19.
- 20.
- 21. Manual Testing Okay
- 22. PO Acceptance
- 23. Doco Complete
- 24. Design Complete
- 25. Test Case Examples Done
- 26. UIX Input Ready
- 27. Code Complete
- 28. Source Checked In
- 29. Unit Tests Green
- 30.
- 31.
- 32. Manual Testing Okay
- 33. PO Acceptance
- 34. Doco Complete
- 35. Design Complete
- 36. Test Case Examples Done
- 37. UIX Input Ready
- 38. Code Complete
- 39. Source Checked In
- 40. Unit Tests Green
- 41.
- 42.
- 43. Manual Testing Okay
- 44. PO Acceptance
- 45. Doco Complete
- 46. Design Complete
- 47. Test Case Examples Done
- 48. UIX Input Ready
- 49. Code Complete
- 50. Source Checked In
- 51. Unit Tests Green
- 52.
- 53.
- 54. Manual Testing Okay
- 55. PO Acceptance
- 56. Doco Complete
- 57. Design Complete
- 58. Test Case Examples Done
- 59. UIX Input Ready
- 60. Code Complete
- 61. Source Checked In
- 62. Unit Tests Green
- 63.
- 64.
- 65. Manual Testing Okay
- 66. PO Acceptance
- 67. Doco Complete
- 68. Design Complete
- 69. Test Case Examples Done
- 70. UIX Input Ready
- 71. Code Complete
- 72. Source Checked In
- 73. Unit Tests Green
- 74.
- 75.
- 76. Manual Testing Okay
- 77. PO Acceptance
- 78. Doco Complete
- 79. Design Complete
- 80. Test Case Examples Done
- 81. UIX Input Ready
- 82. Code Complete
- 83. Source Checked In
- 84. Unit Tests Green
- 85.
- 86.
- 87. Manual Testing Okay
- 88. PO Acceptance
- 89. Doco Complete
- 90. Design Complete
- 91. Test Case Examples Done
- 92. UIX Input Ready
- 93. Code Complete
- 94. Source Checked In
- 95. Unit Tests Green
- 96.
- 97.
- 98. Manual Testing Okay
- 99. PO Acceptance
- 100. Doco Complete
- 101. Design Complete
- 102. Test Case Examples Done
- 103. UIX Input Ready
- 104. Code Complete
- 105. Source Checked In
- 106. Unit Tests Green
- 107.
- 108.
- 109.
- 110.
- 111.
- 112.
- 113.
- 114.
- 115.
- 116. Manual Testing Okay
- 117. PO Acceptance
- 118. Doco Complete
- 119. Design Complete
- 120. Test Case Examples Done
- 121. UIX Input Ready
- 122. Code Complete
- 123. Source Checked In
- 124. Unit Tests Green
- 125.
- 126.
- 127.
- 128.
- 129.
- 130.
- 131.
- 132.
- 133.
- 134.
- 135.
Editor's Notes
- A physical whiteboard or corkboard although electronic boards can also be usedKanbans indicate where in the process a piece of work isThe board is typically organized into columns, each one of which represents a stage in the process or a work buffer or queueOptional rows indicating the allocation of capacity to classes of serviceEach kanban should have sufficient information, such as the name and ID of the work item and due date (if any), to enable project-management decisions by the team without the direction of a managerThe goal is to visually communicate enough information to make the process self-organizing and self-expediting at the team level. The board is directly updated by team members throughout the day as the work proceedsHigh-level blocking issues are discussed during daily stand-up meetings – the board provides status.
- Limiting work in progress reduces average lead timeImproves the quality of the work produced and thereby increasesoverall productivity of your teamReducing lead time also increases your ability to deliver valuable functionality frequentlywhich helps to build trust with your stakeholdersEvery team is different, you will have different WIP limits that you'll need to set and then evolve yourself based on empirical results from experimentation