Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Kanban. Dealing with the elephant in the room. One chunk at a time

1,567 views

Published on

Evolutionairy change is a great method in DevOps environments

Published in: Business, Technology
  • Be the first to comment

Kanban. Dealing with the elephant in the room. One chunk at a time

  1. 1. KanbanDealing with the elephant inthe room, one chunk ata time.
  2. 2. How do you eat an elephant?
  3. 3. One bit at a time
  4. 4. But where do you start???
  5. 5. #DevOpsDaysAgile coach & consultantJasper Sonnevelt
  6. 6. “Who uses some form ofagile (method)?”
  7. 7. “Do you still know whyyou started using „X?”
  8. 8. Kanban is about provokingthe right conversationsabout the best outcomefor your organization!
  9. 9. Evolutionary vs Revolutionairychange- Natural progression- Incremental- Small steps- Strong need forcollaboration towork- Transformational- Complete overhaul- Breaking with the pastOrganizationalAwesomeness
  10. 10. Evolutionary vs Revolutionairychange- Eating the elephantone bite at a time- Taking one big bite andhoping we won‟t choke onit!
  11. 11. Evolutionary vs Revolutionairychange- Eating the elephantone bite at a time- Taking one big bite andhoping we won‟t choke onit!
  12. 12. Basic Kanban principles
  13. 13. 1. Start with what you do now2. Agree to pursue incremental, evolutionary change3. Initially, respect current roles, responsibilities & jobtitles4. Encourage acts of leadership at all levels in yourorganization– from individual contributor to senior managementBasic Kanban principles
  14. 14. 6 Kanban practices• Visualize• Limit Work-in-Progress• Manage Flow• Make Process Policies Explicit• Develop feedback mechanismsat workflow, inter-workflow and organizational levels• Improve Collaborativelyusing “safe to fail” experiments
  15. 15. Making Kanban work foryour organization
  16. 16. WhyHowWhat“The golden circle”All successfulleaders, teams, organizationsAct, think andcommunicate in theexact same waySimon Sinek – Start with why
  17. 17. WhyHowWhat“The golden circle”Product / solutionSimon Sinek – Start with why
  18. 18. WhyHowWhat“The golden circle”Process / USPProduct / solutionSimon Sinek – Start with why
  19. 19. WhyHowWhat“The golden circle”Motivation/purposeProcess / USPProduct / solutionSimon Sinek – Start with why
  20. 20. You have options!WHY HOW WHAT
  21. 21. We use Kanban because…“We want to improveScrum because we have alot of ad-hoc work”“Kanban helps us toreduce multitasking”“To see how we arespending our time ”“Focus on flow”
  22. 22. Lets imagine a team…
  23. 23. Simon Sinek – Start with why“We want to:– Reduce stress– Have a happy customer– Be transparent”WhyHowWhatMotivation/purpose
  24. 24. WhyHowWhat“We think we can do this by:– Getting a grip on ad-hocwork– Involving our customer– Making small changes inour process”Process / USPSimon Sinek – Start with why
  25. 25. “To do so we will:– Put up a board–Stand-ups and retrospectives– Work at our clients officefrequently– Limit our WiP”WhyHowWhatProductSimon Sinek – Start with why
  26. 26. One of the reasons whycopying a workprocess onlygets you so far!
  27. 27. Next Intake Dev Test DeployedVisualize a status to makesure customer is involvedand work is acually readyto startImplications fordesign decisions
  28. 28. Next Intake Dev Test DeployedAdd extra swimlanes tomanage riskImplications fordesign decisions
  29. 29. Implications formuch more…LocationProcess PoliciesMetrics
  30. 30. 1. Start with what you do now2. Agree to pursue incremental, evolutionary change3. Initially, respect current roles, responsibilities & jobtitles4. Encourage acts of leadership at all levels in yourorganization– from individual contributor to senior managementBasic Kanban principles
  31. 31. What you measure is what you get!
  32. 32. Thank you!

×