Kanban 101

at LeadingAgile
Jul. 13, 2010
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
Kanban 101
1 of 35

More Related Content

What's hot

How to start an Agile TransformationHow to start an Agile Transformation
How to start an Agile TransformationFranky Redant
Agile 101Agile 101
Agile 101beLithe
What is Scrum?What is Scrum?
What is Scrum?Fredrik Fjällström
Overview of Agile MethodologyOverview of Agile Methodology
Overview of Agile MethodologyHaresh Karkar
Agile Methodology in Software DevelopmentAgile Methodology in Software Development
Agile Methodology in Software DevelopmentRaghav Seth
Scrum ProcessScrum Process
Scrum ProcessJohn Lewis

Viewers also liked

Kanban six core practicesKanban six core practices
Kanban six core practicesAnders Beskow
Kanban 101 - An Introduction to Planning with Little's LawKanban 101 - An Introduction to Planning with Little's Law
Kanban 101 - An Introduction to Planning with Little's LawJack Speranza
Personal Kanban 101Personal Kanban 101
Personal Kanban 101Jim Benson
Keep It Lean - TCUK 2015Keep It Lean - TCUK 2015
Keep It Lean - TCUK 2015Mattias Sander
OOP 2012 - Kanban at Scale and why traditional approaches set you up for failureOOP 2012 - Kanban at Scale and why traditional approaches set you up for failure
OOP 2012 - Kanban at Scale and why traditional approaches set you up for failureDavid Anderson
2014 02 kanbans not-so-hidden agendas 22014 02 kanbans not-so-hidden agendas 2
2014 02 kanbans not-so-hidden agendas 2Mike Burrows

Similar to Kanban 101

Fllow con 2014 Fllow con 2014
Fllow con 2014 gbgruver
Kanban Intro & OverviewKanban Intro & Overview
Kanban Intro & OverviewJeff Kosciejew
DevOps and AWSDevOps and AWS
DevOps and AWSShiva Narayanaswamy
Continuous DeploymentContinuous Deployment
Continuous DeploymentBrian Henerey
2014 toronto-torbug2014 toronto-torbug
2014 toronto-torbugc.titus.brown
Bugfest!Bugfest!
Bugfest!TechWell

More from Dennis Stevens

Agile2013 sustainable changeAgile2013 sustainable change
Agile2013 sustainable changeDennis Stevens
Beyond functional silos with communities of practiceBeyond functional silos with communities of practice
Beyond functional silos with communities of practiceDennis Stevens
Agile and the nature of decision makingAgile and the nature of decision making
Agile and the nature of decision makingDennis Stevens
Agile FundamentalsAgile Fundamentals
Agile FundamentalsDennis Stevens
Coffee maker workshopCoffee maker workshop
Coffee maker workshopDennis Stevens
Deciding what to buildDeciding what to build
Deciding what to buildDennis Stevens

Recently uploaded

2023-09 Bloomerang Academy Text Fundraising Presentation.pdf2023-09 Bloomerang Academy Text Fundraising Presentation.pdf
2023-09 Bloomerang Academy Text Fundraising Presentation.pdfBloomerang
James Feldman - AII Powered Business Tools.pdfJames Feldman - AII Powered Business Tools.pdf
James Feldman - AII Powered Business Tools.pdfSOLTUIONSpeople, THINKubators, THINKathons
California Carpet Stewardship Program Q2 2023 ResultsCalifornia Carpet Stewardship Program Q2 2023 Results
California Carpet Stewardship Program Q2 2023 ResultsCarpet America Recovery Effort
Industrial Tech Startups In The SF Bay AreaIndustrial Tech Startups In The SF Bay Area
Industrial Tech Startups In The SF Bay AreaChristian Dahlen
Eddie Tofpik's TA Presentation at SEEMT Sep 2023Eddie Tofpik's TA Presentation at SEEMT Sep 2023
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...You Don't Have to Be Big to Leverage Data - Lessons and Confessions from a Fo...
You Don't Have to Be Big to Leverage Data - Lessons and Confessions from a Fo...saastr

Recently uploaded(20)

Kanban 101

Editor's Notes

  1. 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.
  2. 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