Kanban-metoden

1. Kanban is a change management method that focuses on the
following principles:
What is Kanban?
1
Start with what you do now
Agree to pursue incremental, evolutionary change
Respect for the current process, roles, responsibilities, titles
Leadership at all levels
Driving change
Those of you familiar with Lean will recognize many of these principles as
being the foundation for a Lean pull system and the building of a continuous
improvement (Kaizen) culture. What Kanban first and foremost does is serve
as a catalyst to introduce Lean ideas into software delivery systems.

2. What is Kanban?
- Visualize every step in your value chain from vague
concept to releasable software.
Visualize Workflow
Visualizing workflows supports proper understanding of changes planned and
helps to implement them according to this plan. A common way to visualize the
workflow is to use a card wall with cards and columns. The columns on the
card wall represent different states or steps in the workflow.

3. What is Kanban?
- Set explicit limits on the amount of work allowed in each
stage.
Limit Work-In-Progress (WIP limits)

4. What is Kanban?
- Measure and Manage Flow to make informed decisions
and visualize consequence
Measure and Manage Flow

5. What is Kanban?
- Make the policies you are acting according to explicit.
Until the mechanism of a process is made explicit, it is often hard or impossible
to hold a discussion about improving it
Make Policies Explicit

6. What is Kanban?
- Create a Kaizen culture where continuous improvement is
everyone’s job.
Identify Improvement Opportunities

7. Visualizing benefits
Visualizing your workflow gives a number of benefits
Focus on “The Whole”
It becomes visible exactly how your work affects others, and
vice versa.
Transparency
Everybody knows exactly what is going on and no information is
hidden.
Identifying waste
You naturally start to question why you are doing things the way
you are

8. Benefits gained
What have we gained
First things first - able to react fast on changes
Deadline of high priority tasks can be reached
Initial time estimate can be used as a starting point for the
actual project.
We are able to improve during a project
Overview for people deeply involved in the project as well as
people on a managing level.
Easy to collaborate with colleagues and customers on different
locations (shared board)

9. Benefits gained
What have we gained
Less pressure on development
Metrics can be used for prediction of future resource needs
Easy to se where the flow stops (tasks are blocked)
Easy to add resources because of overview
Less time spend on management, spread between team members
For more info contact:
Thomas Nørby
Email: Thomas.Noerby@br-automation.com