4. Openminds
• Hosting (support, installations, ...)
•Development
•Sales/marketing
•Administration
• 8 people (5 sysadmin, 2 development, 1
sales, but overlap)
Tuesday 14 June 2011
5. Before
• Planning was hard
•Tickets got “lost”
•Hard to delegate a task to a colleague
•No overview
Tuesday 14 June 2011
6. Overview
•Each had his own todo method
• Support: “master in-pile” & “todo”
•Sales: Kristofs book
•Development: All over the place
•Other: when (if) it came to mind
Tuesday 14 June 2011
10. Standard IT kanban
•Backlog, Ready, Work In Progress, Done
Tuesday 14 June 2011
11. Standard IT kanban
• Backlog, Ready, Work In Progress, Done
•Task goes from left to right
Tuesday 14 June 2011
12. Standard IT kanban
• Backlog, Ready, Work In Progress, Done
•Task goes from left to right
•WIP is limited
Tuesday 14 June 2011
13. Standard IT kanban
• Backlog, Ready, Work In Progress, Done
•Task goes from left to right
•WIP is limited
•Refill of the backlog through meetings
Tuesday 14 June 2011
22. Meetings
•Monday: “planning”
•Tuesday till Friday: “standup”
Tuesday 14 June 2011
23. Planning
• First working day of the week
•Overview of last week
•Selection of workload for this week
•Discussion about each todo-item
• Rating the item
Tuesday 14 June 2011
24. Planning
poker
• Fibonacci-series
• ? en coffee
• Complexity, not time
• Discussion when the
difference is big
Tuesday 14 June 2011
25. Each morning
Standup
5 minutes
Tuesday 14 June 2011
27. Extra
• Priority is from top to bottom (todo)
•“Pair” for training / difficulties
•Ping-pong: stick the tickets together
•Three magnets per person
Tuesday 14 June 2011
28. Introduction
•No major issues...
•Team wanted some change
•We will evaluate after 2 months
Tuesday 14 June 2011
30. Result
•Planning: major improvement
Tuesday 14 June 2011
31. Result
• Planning: major improvement
•Monitoring: nothing gets forgotten
Tuesday 14 June 2011
32. Result
• Planning: major improvement
•Monitoring: nothing gets forgotten
•Overview: very clear
Tuesday 14 June 2011
33. Result
• Planning: major improvement
•Monitoring: nothing gets forgotten
•Overview: very clear
•Workflow gets optimized
Tuesday 14 June 2011
34. Result
•Planning: major improvement
•Monitoring: nothing gets forgotten
•Overview: very clear
•Workflow gets optimized
• Open communication between teams
Tuesday 14 June 2011
35. More result
•Measurement: velocity
•feedback for the planning-meeting
Tuesday 14 June 2011
37. Issues
•Our board is too small
Tuesday 14 June 2011
38. Issues
• Our board is too small
•Planning: only one week
Tuesday 14 June 2011
39. Issues
• Our board is too small
•Planning: only one week
•Existing ticketting system
Tuesday 14 June 2011
40. Issues
•Our board is too small
•Planning: only one week
•Existing ticketting system
•Flexible working hours & morning-meeting
Tuesday 14 June 2011
41. Issues
•Our board is too small
•Planning: only one week
•Existing ticketting system
•Flexible working hours & morning-meeting
• Person still decides what to work on
Tuesday 14 June 2011
42. Post-its
They don’t stick as they
advertise!
Tuesday 14 June 2011
43. ISO 9001
•We have ISO certification
•Kanban is a perfect fit
•Auditor loved the idea
Tuesday 14 June 2011
44. Bottom line
•It works
•No problem making your own version
•Routine
•Digital board?
• Bigger teams?
Tuesday 14 June 2011
