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
Methodologies
Supporting disciplines
Tools

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 and 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 Lean manufacturing.[2]

The Kanban method[edit]

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. It 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.
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.

Open Kanban[edit]

An open source, Agile and Lean based method to deliver value for knowledge work like Information Technology, Software Development, Business, Product Development or Personal organization. On the Lean side it is inspired on the work of Taiichi Ohno (Toyota Production System), Eliyahu Goldratt (Theory of Constraints) and Edward Deming. On the Agile side it takes inspiration from the Agile manifesto signers, and in addition contributions from Alan Shalloway’s Kanban for Teams, Corey Ladas Scrumban and David Anderson's early Kanban work.

It innovates by making the whole method fully open source and free to improve or modify. Open Kanban was written by Joseph Hurtado, and it has been translated by members of the community to French, Italian, Russian and Ukrainian.

Kanban board example[edit]

Kanban Software Development Workflow[5] 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
Login
User Story 567
User Story 214
User Story 857
User Story 654
User Story 75
User Story 754
Register
User Story 244
User Story 751
Password Recovery
User Story 624
User Story 245
User Story 782
Billing
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

See also[edit]

References[edit]

  1. ^ Toyota Production System Toyota Production System: Beyond Large-Scale Production
  2. ^ The Machine That Changed the World
  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. ^ Jasper Boeg (2012-02). "Priming Kanban" (in English). InfoQ. Retrieved 2014-02-17. 

External links[edit]