Kanban


Kanban is a highly visual agile development methodology that emphasizes controlling work in progress and visualizing work.

  • use Kanban to
    • control work in progress (WIP) levels
    • manage workflows in software and other business processes

6 Core Practices

  1. Visualize work
    • create a Kanban board that shows the specific phases that work moves through on your team
    • create the actual pieces of work that are moving through the stages
  2. Limit WIP
    • allows team members to focus and increases throughput
    • reduce context switching and increase focus
  3. Make policies explicit
    • clearly define how work gets completed and moves from one phase to another
    • create a shared understanding of the work and the workflow
  4. Manage flow
    • look for and eliminate bottlenecks in your workflow
    • embraces Kanban’s roots in lean and reduces waste in the system.
  5. Implement feedback loops
    • build feedback into the system to stay informed about the system’s performance
    • Create and measure metrics and the flow of work across the Kanban board
    • help you identify bottlenecks and changes in your system
  6. Improve collaboratively, evolve experimentally
    • use the scientific method to test ideas and measure the results in the Kanban signals
    • goal is to start now and keep improving
    • whatever the organization is doing now is a good starting point because the team will keep improving the workflow

4-Part Workflow

  1. The product owner prioritizes and orders the backlog
  2. A team member selects the top-ordered item in the backlog and pulls it into progress
  3. The team moves the work item through the workflow, keeping within the WIP limits
  4. When the team is ready to start new work, they select the next item in the backlog

Strengths

  • simplest agile framework to learn
  • can be applied to any industry
  • lightweight and focuses on routine work over iteration planning
    • governed by clearly defined, transparent policies and metrics

Weaknesses

  • can suffer if teams are oversized or have high turnover
  • Inaccuracies or changes between work items can disrupt the team’s focus
  • cycle times may stretch out in the absence of set iterations, if performance is not properly managed

Use Cases

  • Kanban fits teams where the backlog or worklist changes often
  • Teams that work well with less structure would thrive with Kanban
  • Kanban works best with relatively stable workflows