The Kanban Method
Visual Workflow Management for Continuous Improvement
The Kanban Method at Elasticbrains
Kanban is a visual system for managing work processes that originated in the Toyota production method and is now widely used in software development. At Elasticbrains, we use Kanban to promote continuous flow, identify bottlenecks, and improve predictability.
The Core Principles of Kanban
Workflow Visualization
Through a visual board, all work steps and statuses are transparently displayed so the entire team can see the current status at any time.
Work-in-Progress Limits
By limiting simultaneously processed tasks, we avoid multitasking and promote throughput and quality of work.
Flow Management
Workflow is continuously measured and optimized to eliminate bottlenecks and improve predictability.
Explicit Process Rules
Clear and transparent rules for the work process ensure a common understanding within the team.
Feedback Loops
Regular reviews and adjustments enable continuous improvement based on data and experience.
Collaborative Improvement
The entire team is involved in optimizing the work process and develops a shared understanding of improvement potential.
Structure of a Kanban Board
Backlog
WIP: ∞In Development
WIP: 3Code Review
WIP: 2Testing
WIP: 2Done
WIP: ∞A typical Kanban board at Elasticbrains with different work phases and WIP limits (Work-in-Progress limits). The cards represent tasks to be completed, moving from left to right through the different phases.
Kanban Metrics and Control
To enable continuous improvement, we measure and analyze various aspects of our workflows:
Lead Time & Cycle Time
We measure how long tasks take from backlog to completion (Lead Time) and how long they are actually in progress (Cycle Time). These metrics help us improve predictability and provide realistic time estimates.
Throughput
We measure how many tasks are completed within a certain time period. This metric helps us identify trends and better understand the team's capacity.
Cumulative Flow Diagram
This diagram shows the number of tasks in each phase over time and helps us visualize bottlenecks and changes in workflow.
Blocked Tasks
We track tasks blocked by external factors to identify and resolve systemic issues.
Kanban vs. Scrum - When Do We Use What?
At Elasticbrains, we choose the approach that best fits the project and team:
| Aspect | Kanban | Scrum |
|---|---|---|
| Rhythm | Continuous flow | Timeboxes (Sprints) |
| Role Definition | Flexible, no predefined roles | Fixed roles (Scrum Master, Product Owner, Development Team) |
| Changes | Possible at any time | Ideally not during the Sprint |
| Planning | Just-in-time, as needed | Sprint Planning at the beginning of each Sprint |
| Metrics | Lead Time, Cycle Time, Throughput | Velocity, Burndown Charts |
| Ideal Use Case | Support, maintenance work, continuous services | Product development with clear increments |
In many projects, we also use a combination of both approaches, known as "Scrumban", to leverage the benefits of both methods.
Benefits of Kanban for Our Customers
Shorter Lead Times
Through focus and WIP limits, tasks are completed faster, shortening time-to-market.
Better Predictability
By measuring and analyzing lead times, we can make more precise predictions about delivery dates.
Higher Quality
By focusing on fewer simultaneous tasks, work quality is improved and error rates are reduced.
Transparency
The visual board gives all stakeholders a clear overview of current project status and potential issues.
The use of Kanban revolutionized our support team. The visual display and WIP limits halved lead times and significantly improved predictability. Our customers benefit from faster response times and more transparency. - Thomas, Kanban Coach at Elasticbrains
Ready for More Efficiency and Transparency?
Contact us for a non-binding conversation about Kanban and how it can optimize your project.