Kanban

Definition and Overview

Concept

Kanban: visual scheduling system managing work items by cards on a board. Origin: Lean manufacturing adapted to software engineering. Purpose: enhance workflow transparency, limit work in progress, optimize delivery.

Scope

Applies to software development teams, IT operations, maintenance, knowledge work. Focus: continuous flow, incremental improvements, avoiding bottlenecks.

Structure

Board divided into columns representing workflow stages. Cards denote tasks or features. Movement left-to-right signifies progress.

Historical Background

Origins

Developed by Taiichi Ohno at Toyota in 1940s-50s for Just-In-Time production. Visual signals (kanban cards) controlled inventory and workflow.

Adaptation to Software

David J. Anderson introduced Kanban to software in early 2000s. Emphasis on evolutionary change, not radical overhaul.

Evolution

Kanban gained traction in Agile and Lean communities. Expanded from manufacturing to knowledge work and IT service management.

Core Principles

Start with What You Do Now

Respect existing roles, processes, responsibilities. Incremental, evolutionary change favored over disruption.

Agree to Pursue Incremental, Evolutionary Change

Continuous improvement through small, manageable steps. Avoids risk of large-scale transformations.

Respect Current Processes, Roles, Responsibilities

Kanban overlays current workflows, enabling visualization without immediate restructuring.

Encourage Leadership at All Levels

Empower team members to identify and act on improvement opportunities.

Kanban Workflow Structure

Board Layout

Columns represent process states: e.g., Backlog, Ready, In Progress, Review, Done. Customizable per team needs.

Cards

Visual task units: user stories, bug fixes, features. Contain details: description, assignee, priority, due date.

Swimlanes

Horizontal lanes grouping cards by class of service, team, priority, or type of work.

Policies

Explicit rules define entry/exit criteria for columns or lanes, ensuring clarity and consistency.

Work-In-Progress (WIP) Limits

Definition

Maximum number of cards allowed in a workflow state simultaneously. Controls capacity and flow.

Purpose

Prevent multitasking, reduce context-switching, expose bottlenecks, improve throughput.

Enforcement

Teams define and agree on limits. Visual signals indicate limit breaches to trigger corrective action.

Impact

Limits drive focus, improve quality, accelerate cycle time.

Roles and Responsibilities

Team Members

Execute tasks, update cards, respect WIP limits, collaborate to optimize flow.

Service Delivery Manager

Facilitates Kanban process, removes impediments, monitors metrics, drives continuous improvement.

Product Owner

Prioritizes backlog, clarifies requirements, aligns workflow with business goals.

Stakeholders

Provide feedback, validate deliverables, support process transparency.

Implementation Steps

Map Current Workflow

Visualize existing process stages and task statuses.

Create Kanban Board

Set up columns, cards, swimlanes, policies reflecting mapped workflow.

Set WIP Limits

Define capacity constraints per workflow stage based on team capability.

Start Flow

Begin moving cards as work progresses. Track bottlenecks and delays.

Measure and Improve

Collect metrics, review regularly, implement incremental improvements.

Key Metrics and Measurements

Lead Time

Elapsed time from task request to delivery. Indicator of responsiveness.

Cycle Time

Time spent actively working on a task. Measures process efficiency.

Throughput

Number of tasks completed per time unit. Reflects team productivity.

Work In Progress

Count of active tasks. Helps enforce WIP limits and detect overload.

Blocked Time

Duration tasks remain stalled. Identifies impediments.

Popular Kanban Tools

Trello

Cloud-based visual board, card system, easy customization, collaboration features.

Jira Software

Comprehensive Agile tool with Kanban boards, issue tracking, reporting, integration.

Azure DevOps

Microsoft platform with Kanban boards, pipelines, dashboards, work item tracking.

Kanbanize

Enterprise-grade Kanban tool, advanced analytics, portfolio management, automation.

LeanKit

Visual management for Lean and Kanban, supports multiple boards, metrics, and workflow policies.

Advantages and Benefits

Transparency

Visual boards expose workflow and task status, improving communication.

Flexibility

Adapts to existing processes, no forced roles or ceremonies.

Focus on Flow

Emphasizes continuous delivery and reducing cycle time.

Reduced Bottlenecks

WIP limits highlight overloads and delays, enabling timely intervention.

Continuous Improvement

Data-driven feedback loops promote gradual process optimization.

Challenges and Limitations

Initial Setup Complexity

Mapping workflows and defining policies can be time-consuming.

Resistance to Change

Teams may struggle to adopt new visualization and WIP discipline.

Scope Creep

Without strict backlog management, Kanban can lead to uncontrolled work expansion.

Limited Prescriptiveness

Lacks defined roles or ceremonies, potentially causing coordination issues.

Scaling

Large organizations require additional frameworks to coordinate multiple teams.

Comparison with Other Agile Methods

Kanban vs Scrum

Kanban: continuous flow, no fixed iterations, flexible WIP limits. Scrum: fixed sprints, roles (Scrum Master, Product Owner), ceremonies.

Kanban vs Lean

Kanban: implements Lean principles visually. Lean: broader philosophy focusing on waste elimination, value stream mapping.

Kanban vs XP (Extreme Programming)

XP: emphasizes engineering practices (pair programming, TDD). Kanban: workflow optimization without prescriptive engineering methods.

Kanban with Scrum

Hybrid use common: Scrum manages sprint cadence, Kanban controls flow within sprints.

Comparison Table:+-------------------+--------------------------+---------------------------+| Feature | Kanban | Scrum |+-------------------+--------------------------+---------------------------+| Iterations | Continuous flow | Fixed length sprints || Roles | No prescribed roles | Defined roles || WIP Limits | Explicitly enforced | Implicit via sprint scope || Ceremonies | Optional | Required (Sprint Planning, Review, Retrospective) || Change Management | Evolutionary, incremental| Iterative, sprint-based |+-------------------+--------------------------+---------------------------+ 

References

• Anderson, D.J., "Kanban: Successful Evolutionary Change for Your Technology Business," Blue Hole Press, 2010.
• Kniberg, H., "Kanban and Scrum - Making the Most of Both," C4Media, 2010.
• Leach, L.P., "Critical Chain Project Management Improves Project Performance," Project Management Journal, vol. 32, no. 4, 2001, pp. 39-51.
• Poppendieck, M., Poppendieck, T., "Lean Software Development: An Agile Toolkit," Addison-Wesley, 2003.
• Little, A.D., "Kanban in Action," Manning Publications, 2018.