Lknl13 Kanban Dealing with the elephant in the room

552 views
447 views

Published on

My presentation about Kanban as a evolutionary change method and management framework at Modern Management Methods conference #LKNL13.

Basic introduction to Kanban with some practical tips to make it work in your organization

Published in: Business, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
552
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • First lets start off with the difference between Evolutionairy change and Revolutionary change. They are both approaches to change. Even though they can both be used to accomplish the same goal lets call it Organizational Awesomeness for now. Each has its own characteristics, pro’s and cons. So lets match some of the qualities with each approach.Evolutionairy Changewill usually happen in a natural progression as a reaction to changing environments, competitors, new technologies. But it can also be initiated and given direction. Also, evolutionairy change happens in smallincremental steps. This means that it will probably take longer, but that is also a good thing. By going slow and letting people you work with help with the change lowers resistance. Revolutionairy changeUsually has the shape of a complete overhaul of the process or organization. They can have massive impact and are very hard to miss. It is a definite break with the past. Whatever we used to do stops from today. This way of changing works really well when you want to shake up the team or organization. However, it also takes a lot of getting used to new ways and
  • First lets start off with the difference between Evolutionairy change and Revolutionary change. They are both approaches to change. Even though they can both be used to accomplish the same goal lets call it Organizational Awesomeness for now. Each has its own characteristics, pro’s and cons. So lets match some of the qualities with each approach.Evolutionairy Changewill usually happen in a natural progression as a reaction to changing environments, competitors, new technologies. But it can also be initiated and given direction. Also, evolutionairy change happens in smallincremental steps. This means that it will probably take longer, but that is also a good thing. By going slow and letting people you work with help with the change lowers resistance. Revolutionairy changeUsually has the shape of a complete overhaul of the process or organization. They can have massive impact and are very hard to miss. It is a definite break with the past. Whatever we used to do stops from today. This way of changing works really well when you want to shake up the team or organization. However, it also takes a lot of getting used to new ways and
  • First lets start off with the difference between Evolutionairy change and Revolutionary change. They are both approaches to change. Even though they can both be used to accomplish the same goal lets call it Organizational Awesomeness for now. Each has its own characteristics, pro’s and cons. So lets match some of the qualities with each approach.Evolutionairy Changewill usually happen in a natural progression as a reaction to changing environments, competitors, new technologies. But it can also be initiated and given direction. Also, evolutionairy change happens in smallincremental steps. This means that it will probably take longer, but that is also a good thing. By going slow and letting people you work with help with the change lowers resistance. Revolutionairy changeUsually has the shape of a complete overhaul of the process or organization. They can have massive impact and are very hard to miss. It is a definite break with the past. Whatever we used to do stops from today. This way of changing works really well when you want to shake up the team or organization. However, it also takes a lot of getting used to new ways and
  • Before we get into how to make evolutionary change work for your organization i would like to go over some of the basic priciples and practices of Kanban. Kanban is a very nice approach to evolutionary change. I assume that a lot of you are already familiair with the Kanban principles and practices so I will go over them fairly quickly.
  • There are 4 basic Kanban practices. And the first one is very simple: start with what you do now. That is easy. Just take your current situation as a starting point. And all you now have to do is AgreeTo persue incremental, evolutionairy change. We now know that this means small steps towards a goal. The third principle is to Initially, respect current roles, responsibilities and Job titles. So a project manager is still a project manager. And a Scrum Master is still a Scrum Master. The roles that are in the organization are there probably for a reason. They will have worked at some point and might even work nowso why change them? Also, people who work in these roles probably worked hard to get to that point and suddenly telling them that they now have a different title might lead them to resist the change. So initially, lets respect their roles. As a forth we want to encourage acts of leadership. This means that everybody who has a good initiative or idea can take the leadThis is behaviour that we want to encourage
  • There are 4 basic Kanban practices. And the first one is very simple: start with what you do now. That is easy. Just take your current situation as a starting point. And all you now have to do is AgreeTo persue incremental, evolutionairy change. We now know that this means small steps towards a goal. The third principle is to Initially, respect current roles, responsibilities and Job titles. So a project manager is still a project manager. And a Scrum Master is still a Scrum Master. The roles that are in the organization are there probably for a reason. They will have worked at some point and might even work nowso why change them? Also, people who work in these roles probably worked hard to get to that point and suddenly telling them that they now have a different title might lead them to resist the change. So initially, lets respect their roles. As a forth we want to encourage acts of leadership. This means that everybody who has a good initiative or idea can take the leadThis is behaviour that we want to encourage
  • There are 4 basic Kanban practices. And the first one is very simple: start with what you do now. That is easy. Just take your current situation as a starting point. And all you now have to do is AgreeTo persue incremental, evolutionairy change. We now know that this means small steps towards a goal. The third principle is to Initially, respect current roles, responsibilities and Job titles. So a project manager is still a project manager. And a Scrum Master is still a Scrum Master. The roles that are in the organization are there probably for a reason. They will have worked at some point and might even work nowso why change them? Also, people who work in these roles probably worked hard to get to that point and suddenly telling them that they now have a different title might lead them to resist the change. So initially, lets respect their roles. As a forth we want to encourage acts of leadership. This means that everybody who has a good initiative or idea can take the leadThis is behaviour that we want to encourage
  • There are 4 basic Kanban practices. And the first one is very simple: start with what you do now. That is easy. Just take your current situation as a starting point. And all you now have to do is AgreeTo persue incremental, evolutionairy change. We now know that this means small steps towards a goal. The third principle is to Initially, respect current roles, responsibilities and Job titles. So a project manager is still a project manager. And a Scrum Master is still a Scrum Master. The roles that are in the organization are there probably for a reason. They will have worked at some point and might even work nowso why change them? Also, people who work in these roles probably worked hard to get to that point and suddenly telling them that they now have a different title might lead them to resist the change. So initially, lets respect their roles. As a forth we want to encourage acts of leadership. This means that everybody who has a good initiative or idea can take the leadThis is behaviour that we want to encourage
  • By following the Kanban practices a couple of practices started to emerge that were common in succesful Kanban implementations. As you may have noticed they are not numbered. This is because you dont have to do all of them to make Kanban work for you. And the top practice is to Visualize. There is a lot to visualize. We usually visualize our process and differents steps by adding colums, make our current workload visible by putting them on stickies or perhaps a digital variation of those. Some other things that are visualized: metrics, process policies and goalsWe probably all know that multitasking is evil. So that’s one of the reasons why we want to limit work in progress. The less multitasking we have to do and the less workitems we have in our process, the faster it will be finished. Think of it as a highway. The fuller it gets, the slower you are probably able to drive. The third practice is to manage flow. You want to optimize the way tasks move through your process. This means dealing with bottlenecks and adjusting wip limits for optimal flow. When you are doing this you will probably set up policies as a team. It is key to make these explicit so that everyone can get to know them easily. This helps with being transparent. Policies can be about all sorts of things. For instance it can be about when a task may enter the process, when it moves to a different collum (or state), when it is done, how the team likes to work toghether, what is expected from eachother etcetera. And to see how you are doing you need to develop feedback mechanisms. They can be in the form of a regular PDCA cycle, a retrospective or a even a stand-up. And last but not least the sixth practice: improve collaboratively. We already agreed to persue incremental change, but we want to do that in a collaborative way. Involving for instance that business person that keeps asking about why work is taking so long in an experiment to improve communication can really help.
  • This leads to specific design desicions
  • This leads to specific design desicions
  • This leads to specific design desicions
  • Lknl13 Kanban Dealing with the elephant in the room

    1. 1. Kanban Dealing with the elephant in the room, one chunk at a time.
    2. 2. #LKNL13@jaspersonnevelt Jasper Sonnevelt Agile coach | Change agent @jaspersonnevelt.nl mail@jaspersonnevelt.nl
    3. 3. #LKNL13@jaspersonnevelt How do you eat an elephant?
    4. 4. #LKNL13@jaspersonnevelt One bit at a time
    5. 5. #LKNL13@jaspersonnevelt But where do you start???
    6. 6. #LKNL13@jaspersonnevelt
    7. 7. #LKNL13@jaspersonnevelt Kanban is about provoking the right conversations about the best outcome for your organization!
    8. 8. #LKNL13@jaspersonnevelt Evolutionary vs Revolutionairy change - Natural progression - Incremental - Small steps - Strong need for collaboration to work - Transformational - Complete overhaul - Breaking with the past Organizational Awesomeness
    9. 9. #LKNL13@jaspersonnevelt Evolutionary vs Revolutionairy change - Eating the elephant one bite at a time - Taking one big bite and hoping we won’t choke on it!
    10. 10. #LKNL13@jaspersonnevelt Evolutionary vs Revolutionairy change - Eating the elephant one bite at a time - Taking one big bite and hoping we won’t choke on it!
    11. 11. #LKNL13@jaspersonnevelt kanban 看 = Kan = Visual 板 = Ban = Sign
    12. 12. #LKNL13@jaspersonnevelt Visual signs
    13. 13. #LKNL13@jaspersonnevelt Kanban An evolutionary change method and management framework
    14. 14. #LKNL13@jaspersonnevelt Basic Kanban principles
    15. 15. #LKNL13@jaspersonnevelt 1. Start with what you do now Basic Kanban principles
    16. 16. #LKNL13@jaspersonnevelt Kanban combines very well with other frameworks / methods Scrum Prince 2 Many more The “W” word
    17. 17. #LKNL13@jaspersonnevelt 1. Start with what you do now 2. Agree to pursue incremental, evolutionary change Basic Kanban principles
    18. 18. #LKNL13@jaspersonnevelt J-Curve Effect Time Profit
    19. 19. #LKNL13@jaspersonnevelt 1. Start with what you do now 2. Agree to pursue incremental, evolutionary change 3. Initially, respect current roles, responsibilities & job titles Basic Kanban principles
    20. 20. #LKNL13@jaspersonnevelt Be like water
    21. 21. #LKNL13@jaspersonnevelt 1. Start with what you do now 2. Agree to pursue incremental, evolutionary change 3. Initially, respect current roles, responsibilities & job titles 4. Encourage acts of leadership at all levels in your organization – from individual contributor to senior management Basic Kanban principles
    22. 22. #LKNL13@jaspersonnevelt Anyone can be a leader
    23. 23. #LKNL13@jaspersonnevelt 6 Kanban practices • Visualize • Limit Work-in-Progress • Manage Flow • Make Process Policies Explicit • Develop feedback mechanisms at workflow, inter-workflow and organizational levels • Improve Collaboratively using “safe to fail” experiments
    24. 24. #LKNL13@jaspersonnevelt Making Kanban work for your organization
    25. 25. #LKNL13@jaspersonnevelt Why How What “The golden circle” All successful leaders, teams, orga nizations Act, think and communicate in the exact same way Simon Sinek – Start with why
    26. 26. #LKNL13@jaspersonnevelt Why How What “The golden circle” Product / solution Simon Sinek – Start with why
    27. 27. #LKNL13@jaspersonnevelt Why How What “The golden circle” Process / USP Product / solution Simon Sinek – Start with why
    28. 28. #LKNL13@jaspersonnevelt Why How What “The golden circle” Motivation/purpose Process / USP Product / solution Simon Sinek – Start with why
    29. 29. #LKNL13@jaspersonnevelt There are many ways that lead to success
    30. 30. #LKNL13@jaspersonnevelt You have options! WHY HOW WHAT
    31. 31. #LKNL13@jaspersonnevelt Lets imagine a (software) development team…
    32. 32. #LKNL13@jaspersonnevelt …in walks facilitator So what do would you like to accomplish?
    33. 33. #LKNL13@jaspersonnevelt Why How What “The golden circle” Motivation/purpose Process / USP Product / solution Simon Sinek – Start with why Policies Method / Principles
    34. 34. #LKNL13@jaspersonnevelt Simon Sinek – Start with why “We want to: – Reduce stress – Have a happy customer – Be transparent” Why How What Motivation
    35. 35. #LKNL13@jaspersonnevelt Why How What “We think we can do this by: – Getting a grip on ad-hoc work – Involving our customer – Making small changes in our process – (implement Kanban)” Process Simon Sinek – Start with why
    36. 36. #LKNL13@jaspersonnevelt “To do so we will: – Put up a board –Stand-ups and retrospectives – Work at our clients office frequently – Limit our WiP” Why How What Policies Simon Sinek – Start with why
    37. 37. #LKNL13@jaspersonnevelt One of the reasons why copying a workprocess doesn’t work!
    38. 38. #LKNL13@jaspersonnevelt Next Intake Dev Test Done Visualize a status to make sure customer is involved and work is acually ready to start Implications for design decisions
    39. 39. #LKNL13@jaspersonnevelt Add extra swimlanes to manage risk Implications for design decisions Next Intake Dev Test Done
    40. 40. #LKNL13@jaspersonnevelt Implications for much more… Location Process Policies Metrics
    41. 41. #LKNL13@jaspersonnevelt What you measure is what you get!
    42. 42. #LKNL13@jaspersonnevelt So how do you deal with the elephant in the room?
    43. 43. #LKNL13@jaspersonnevelt Further learning LKU Accredited Kanban For IT/OPS – Baarn – 9-10 october, 2013 – by Dragos Dumitriu  THIS IS WEDNESDAY! See me for more info Kanban Coaching Professional Masterclass – Amsterdam – 9-11 October, 2013 – by David Anderson
    44. 44. #LKNL13@jaspersonnevelt @jaspersonnevelt.nl mail@jaspersonnevelt.nl Thank you!

    ×