Kanban (Eng) - Waterdud/agilesed-tarkvara GitHub Wiki

📘 Overview

Kanban is a visual project management method that helps teams manage workflows more effectively. Originating from the Toyota Production System, it emphasizes continuous delivery, workflow visualization, and limiting work in progress.

🧱 Key Principles

  1. Visualize the workflow

  2. Limit Work in Progress (WIP)

  3. Manage flow

  4. Make process policies explicit

  5. Implement feedback loops

  6. Improve collaboratively, evolve experimentally

🗂️ Core Elements

  • Kanban Board: A board divided into columns (e.g. To Do, In Progress, Done) that shows the status of work items.

  • Cards: Represent individual work items or tasks.

  • Columns: Represent different stages of the process.

  • WIP Limits: Restrict the number of items in each column.

🔄 Workflow

Kanban encourages smooth flow of work by visualizing tasks and addressing bottlenecks. It is pull-based — tasks are "pulled" when capacity allows, rather than "pushed" into the next stage.

📈 Metrics

  • Lead Time: Time from task creation to completion.

  • Cycle Time: Time from task start to completion.

  • Throughput: Number of tasks completed in a given time.

  • Cumulative Flow Diagram (CFD): Visualizes stability and bottlenecks.

🧠 When to Use Kanban

  • When you want to improve existing processes without drastic changes.

  • To increase delivery predictability.

  • For maintenance or support work.

🧩 Comparison with Scrum

Feature | Scrum | Kanban -- | -- | -- Iterations | Fixed sprints | Continuous flow Roles | Defined roles | Flexible roles Planning | Sprint planning | On-demand planning Metrics | Velocity, Burn-down | Lead/Cycle time, CFD

📚 Further Reading

  • "Kanban" by David J. Anderson

  • kanban.university

  • agilealliance.org/glossary/kanban

⚠️ **GitHub.com Fallback** ⚠️