Kanban (development)

From Wikipedia, the free encyclopedia
Jump to: navigation, search
This article is about the process management and improvement method. For the lean manufacturing process, see Kanban.
Software development process
Core activities
Paradigms and models
Methodologies and frameworks
Supporting disciplines
Standards and BOKs

Kanban is a method for managing knowledge work with an emphasis on just-in-time delivery while not overloading the team members. In this approach, the process, from definition of a task to its delivery to the customer, is displayed for participants to see. Team members pull work from a queue.

Kanban in the context of software development can mean a visual process-management system that tells what to produce, when to produce it, and how much to produce - inspired by the Toyota Production System[1] and by Lean manufacturing.[2]


The name 'Kanban' originates from Japanese[看板], and translates roughly as "signboard" or "billboard". It was formulated by David J. Anderson[3][4] as an approach to incremental, evolutionary process and systems change for organizations. It uses a work-in-progress limited pull system as the core mechanism to expose system operation (or process) problems and stimulate collaboration to continuously improve the system. Visualisation is an important aspect of Kanban as it allows understanding of the work and the workflow.[5]

Kanban is rooted in four basic principles:

Start with existing process
The Kanban method does not prescribe a specific set of roles or process steps. The Kanban method starts with existing roles and processes and stimulates continuous, incremental and evolutionary changes to the system. The Kanban method is a change management method[citation needed].
Agree to pursue incremental, evolutionary change
The organization (or team) must agree that continuous, incremental and evolutionary change is the way to make system improvements and make them stick. Sweeping changes may seem more effective but have a higher failure rate due to resistance and fear in the organization. The Kanban method encourages continuous small incremental and evolutionary changes to your current system.
Respect the current process, roles, responsibilities and titles
It is likely that the organization currently has some elements that work acceptably and are worth preserving. The Kanban method seeks to drive out fear in order to facilitate future change. It attempts to eliminate initial fears by agreeing to respect current roles, responsibilities and job titles with the goal of gaining broader support.
Leadership at all levels
Acts of leadership at all levels in the organization, from individual contributors to senior management, are encouraged.


Kanban Software Development Workflow[6] complements the Scrum, XP and Waterfall models.

Workflow ⇒ Inbox Specification Ready for Development Development
(e.g. using Scrum and XP)
Code Review Test on Local System Test on Pre-Production System Ready for Deployment Deployed
WIP Limit ⇒ 5 2 2 3 2 2 2
Feature In progress Done Planned In Progress Done In progress Done In progress Done In progress Done
User Story 567
User Story 214
User Story 857
User Story 654
User Story 75
User Story 754
User Story 244
User Story 751
Password Recovery
User Story 624
User Story 245
User Story 782
User Story 657
User Story 38
User Story 858
Policies ⇒ Write acceptance criteria Plan developer pairing Note cycle start time TDD and Refactoring Note cycle end time Check Policies Tester and Product Owner needed Check only code functionality
  • Remove Ticket
  • Note lead end date
  • Review deployment
  • Update statistics
  • Reprioritize user stories based on new estimates

Outside of software development[edit]

While developed for software development and software teams, the Kanban method (as distinct from Kanban) has been applied in other areas of knowledge work.[7] As a visualization and control mechanism, any repeatable and consistent workflow can be tracked, regardless of complexity or subject area. Business functions that have applied Kanban include:

  • Human Resources[8] and recruitment[9] teams
  • Sales and marketing teams[10]
  • Organisational strategy and executive leadership teams[11]
  • Audit teams
  • Sales to Goods delivery process[citation needed]
  • Procurements to Goods receipt process[citation needed]
  • Contracts to Project execution process
  • Accounts receivable & payable processes

See also[edit]


  1. ^ Taiichi Ohno (1988). Toyota Production System: Beyond Large-Scale Production. ISBN 978-0915299140. 
  2. ^ James P. Womack (2007). The Machine That Changed the World. ISBN 978-1847370556. 
  3. ^ Anderson, David (September 2003). Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results. Prentice Hall. ISBN 0-13-142460-2. 
  4. ^ Anderson, David (April 2010). Kanban - Successful Evolutionary Change for your Technology Business. Blue Hole Press. ISBN 0-9845214-0-2. 
  5. ^ Scotland, Karl. "Aspects of Kanban". Retrieved 13 November 2014. 
  6. ^ Jasper Boeg (February 2012). "Priming Kanban". InfoQ. Retrieved 2014-02-17. 
  7. ^ Leybourn, E. (2013). Directing the Agile Organisation: A Lean Approach to Business Management. London: IT Governance Publishing: 160–166.
  8. ^ "Kanban for Short Intense Projects: How We Used Kanban to Visualize Our Hiring Process Workflow and Make Our Lives Easier". Personal Kanban. 2011-01-19. Retrieved 2012-08-17. 
  9. ^ "Kanban and Recruitment". The Social Tester. 2014-08-06. Retrieved 2015-06-08. 
  10. ^ "Building an Agile Marketing Team" (PDF). Intland. 2014-03-27. Retrieved 2015-06-08. 
  11. ^ "New Zealand Post Group – An Agile Executive!". Agile Business Management Consortium. 2013-12-02. Retrieved 2015-06-08.