Kanban (development)

Kanban (development)
Jennifer Falco · CC BY 4.0 · source
Name	Kanban (development)
Origin	Toyota Motor Corporation
Introduced	1940s
Domain	Software development

Kanban (development) is an evolutionary workflow management method for software delivery that emphasizes visualization, flow, and continuous improvement. It originated from manufacturing practices and was adapted to software engineering and IT operations to manage work items through a pull-based system. Practitioners use boards, explicit policies, and metrics to optimize delivery and respond to changing priorities while minimizing waste.

History

Kanban traces lineage to the production techniques at Toyota Motor Corporation during the post-war period and the work of Taiichi Ohno and Shigeo Shingo on the Toyota Production System. Concepts from Just-in-Time manufacturing and lean manufacturing influenced adoption in knowledge work during the late 20th century, with insights from figures associated with Lean Enterprise Institute. The technique migrated into software engineering communities alongside practices from Extreme Programming and Agile software development, gaining visibility through conferences such as Agile Alliance gatherings and publications by practitioners from Corbis and Microsoft teams who adapted visual pull systems for IT operations and product development.

Principles and Practices

Kanban in development rests on core principles adapted from lean manufacturing: start with existing processes, pursue incremental change endorsed by leadership like that of W. Edwards Deming-influenced organizations, and respect current roles while evolving policies. Practices include visualizing work with explicit policies, limiting work in progress inspired by Toyota Production System heuristics, managing flow with cues used in Toyota factories, making process policies explicit as advocated by David J. Anderson and others, and implementing feedback loops similar to those in Deming Prize frameworks. The method interoperates with frameworks such as Scrum (software development) and DevOps to support continuous delivery.

Kanban Board and Workflow Visualization

The Kanban board is a visual management tool rooted in production control tactics used at Toyota Motor Corporation and adapted by software teams at organizations like Microsoft and Spotify. Boards map stages such as Backlog, Analysis, Development, Testing, and Done, mirroring workflow models found in Value Stream Mapping and Six Sigma initiatives. Cards represent work items similar to KANBAN cards used in factories; swimlanes and columns enable teams influenced by Scaled Agile Framework or SAFe to visualize service classes and expedite policies. Teams draw inspiration from visual controls used in Lean Six Sigma projects and portfolio boards practiced at Atlassian and Google engineering groups.

Work-in-Progress Limits and Flow Management

Limiting Work-in-Progress (WIP) derives from lean manufacturing constraints championed by Taiichi Ohno and was formalized in software contexts by proponents associated with Lean Software Development. WIP limits reduce context switching and expose bottlenecks identified through techniques used in Theory of Constraints and Value Stream Mapping. Flow management employs policies for pull initiation, explicit service-level expectations akin to Service-level agreement concepts in ITIL, and classes of service inspired by Kanban Method literature. Organizations like Netflix and Etsy have publicized flow-centric practices that emphasize minimizing cycle time and handling blocked work through policies that resemble escalation paths in ISO 9001 quality systems.

Metrics and Continuous Improvement

Kanban emphasizes quantitative metrics—cycle time, lead time, throughput, and cumulative flow diagrams—paralleling performance measurement practices in Six Sigma and Total Quality Management. Teams use Cumulative Flow Diagram and Control Chart techniques derived from statistical process control popularized by Walter A. Shewhart to identify variance and improvement opportunities. Continuous improvement cycles incorporate retrospectives inspired by Agile software development events and change management approaches aligned with Kotter's 8-Step Process for Leading Change in organizational contexts. Measurement-driven improvements are common in enterprises influenced by Lean Startup experimentation and portfolio management at firms such as Spotify and Amazon.

Implementation in Software Development

In software development, Kanban adapts to product backlog management, release pipelines, and incident response processes within DevOps toolchains used by teams at Google, Facebook, and Microsoft. It complements Continuous integration and Continuous delivery pipelines by smoothing work arrival and reducing integration risk, and fits with testing practices from Extreme Programming and deployment strategies used in Cloud computing platforms like Amazon Web Services and Microsoft Azure. Organizations integrate Kanban with role structures from Scrum (software development) when practicing Scrumban hybrids, and apply governance patterns familiar to ITIL and COBIT for enterprise alignment.

Tools and Integrations

A wide ecosystem supports Kanban boards and metrics, including commercial and open source offerings from vendors like Atlassian (Jira), Trello (Atlassian product lineage), Azure DevOps (Microsoft), GitHub Projects, and GitLab. These tools integrate with Continuous integration servers such as Jenkins (software), CircleCI, and Travis CI and with observability platforms like Prometheus and Grafana to surface flow metrics. Enterprise integrations link to portfolio management suites used by Scaled Agile Framework implementers, issue tracking systems employed by Red Hat and IBM, and communication platforms such as Slack (software) or Microsoft Teams to functionally support WIP governance and feedback loops.

Category:Software development