Kanban presentation from the Dare to Learn 2018 workshop Agile Practices for Learning and Working with Change Collaboratively

1. responsiveorg.fi
POWERED BY

2. Kanban
Dare to Learn 18.9.2018 /
Agile Practices for Learning and Working with Change Collaboratively
Janne Heinonen

3. Source:
Lean

4. Kanban
• Adapted from the system Toyota
developed to improve how they
build cars - dating back more
than 50 years!
• Work items are represented
visually on a kanban board,
allowing team members to see
the state of every piece of work
at any time http://blog.toyota.co.uk/kanban-toyota-production-system

5. Principles
• Core principle is to visualize work
• The work of all kanban teams revolves around a kanban board
• Cadence = Continuous flow
• Roles = No existing roles
• Change philosophy = Change can happen at any time
It's the entire team's responsibility to ensure work is moving
smoothly through the process

6. Tasks move continuously from left to right on the board
as work progresses

7. • A basic kanban board
has a three-step
workflow
• One column for the
each different state of
work
➢ To do = list of tasks:
Items to be potentially
worked on, sorted in
priority order
➢ Doing:
Items that have been
selected from the To do
and are worked on
➢ Done:
Items that are ready
Kanban board
and workflow

8. https://leankit.com/learn/kanban/kanban-board/

9. Tasks
• Each card on a kanban board is a work item
• Kanban cards feature critical information about that particular item:
• who is responsible
• a brief description
• how long that piece of work is estimated to take
• etc.
• Bottlenecks = columns accumulating task cards
Shared skillsets means less bottlenecks

11. Agile means ITERATIVE + INCREMENTAL

12. Multitasking kills efficiency
• The team decides on the maximum number of cards each column can
contain, which is called a WIP limit (Work in progress limit)
• A work item can be pulled to the next column only if that column has
spare capacity
• A low limit encourages the team to pay special attention to issues
in a particular state

13. Rituals
• No rituals are specified in kanban, but many teams hold daily
standups and periodic retrospectives to improve team performance
• Daily standups are 15 minute informal gatherings where each team
member answer the following questions:
What did I
complete
yesterday?
What will I
work on today?
Am I blocked
by anything?

14. Tools
• White board & sticky notes
• Virtual shared spaces
• Trello
• Planner
• Jira
• And plenty of more...