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 in your daily work - Sebastian Sussmann


Published on

What is Kanban and what does the belt production has to do with software development?
How can we improve our daily work (personally and in my team) and get things done?
How can we reduce pressure and increase the productivity and quality?

Published in: Leadership & Management
  • Be the first to comment

Kanban in your daily work - Sebastian Sussmann

  1. 1. Kanban in your daily work V150623
  2. 2. Who we are? Dipl.-Ing. Sebastian Sussmann easy, just call me: Sebi Born in Germany Living and working since 2003 in Switzerland and since 2008 also in Vietnam Studied at Brandenburg University of Technology Cottbus (BTU), Germany Swiss Federal Institute of Technology Zürich (ETH), Switzerland IT developing experience started at university in 1995 Institute for Automation Engineering - IFAT, network and WEB-Application, Otto-von-Guericke-University Magdeburg, Germany Multimedia Centre Cottbus (BTU), Germany 3D Print @ Swiss Federal Institute of Technology Zürich (ETH), Switzerland Mappuls AG, Lucerne, Switzerland Axon Active AG, Luzern, Switzerland Axon Active Vietnam Co. Ltd., Ho Chi Minh City, Vietnam Trainer at ECCInternational Email
  3. 3. Axon Active Vietnam We care about the community
  4. 4. ?Kanban ?What does it mean
  5. 5. ?Is this Kanban Do you use it ?
  6. 6. Kanban board
  7. 7. Team board
  8. 8. ?What is ?the idea of Kanban ? ? ?What is Kanban
  9. 9. Kan + ban “Visual” + “card / board”
  10. 10. Produce “Just in time” business
  11. 11. Belt production
  12. 12. Push?
  13. 13. Push? How can we solve this?
  14. 14. Parallel work?
  15. 15. Parallel work? How can we handle it?
  16. 16. Bottleneck?
  17. 17. Bottleneck? Who will fix this?
  18. 18. Kanban [Method] ( Lucy's Famous Chocolate Scene
  19. 19. WIP Observe, Visibility ! ! !Pull
  20. 20. Don’t Hide your work … Don’t produce Technical dept Don’t get “undone work”
  21. 21. The team is OWNER of the Item / Story Not a single member …. Individuals and Interaction - Teamwork
  22. 22. First IN First OUT Get Things DONE
  23. 23. Frequently delivery reduce coordination and planning & increase trust Increase trust and plan
  24. 24. Plan-Do-Check-Act (PDCA) cycle Plan DoCheck Act © W. Edwards Deming (1900 –1993) or Deming Cycle
  25. 25. appreciate that things are done, deliver motivation
  26. 26. Happiness is not something ready made. It comes from your own actions. Dalai Lama
  27. 27. Avoid story card hell Keep your backlog SLIM
  28. 28. Set the GOAL for your Project Get the Vision
  29. 29. Why PULL We don’t want to write more spec than code... We don’t want write more code than tests… We don’t want test more then deploy… We don’t want to have “undone work” ?
  30. 30. Why WIP Reduce multi tasking prevent context switching performing tasks on-at-a-time yields results sooner Maximize throughput and output Enhance teamwork working together to make things done increase cross functionality ?
  31. 31. Visibility Provide visibility status of work how is it progressing Provide a method for continuous improvement Provide a direction to invest into most valuable work Reduce risk Increase flexibility more stable DEV cycle (feedback loop kata)
  32. 32. Get things DONE Incremental Iterative Impact Mapping: Making a big impact with software products and projects / Gojko Adzic fail outcome
  33. 33. Kaizen “change for better“ The Idea of “Continuously improvement”
  34. 34. Get support from other people Slack
  35. 35. ?How does it work In Software development
  36. 36. Kanban [Method] • Continuously prioritized queue (limited work item > PULL system) • Continuously deployment • Development and maintenance, combined • Visibly and easy to use Source: getkanban
  37. 37. Kanban in action (
  38. 38. Kanban stop starting, start finishing Keep the flow running &
  39. 39. Bug’s Where are the BUG’s
  40. 40. Where are the BUG’s
  41. 41. Where are the BUG’s If a serious BUG appear…
  42. 42. Where are the BUG’s
  43. 43. Where are the BUG’s 60% New Development 10% Maintenance 30% Production Problems
  44. 44. Compare Agile Lean Kanban Scrum XP Type The way to THINK Production PRACTICE METHOD FRAMEWORK Technical PRACTICE Goal Responsiveness to changes Reducing waste Maximize the Flow Increase the Speed and Feedback loop Improve software quality Implementation Agile manifesto 12 Agile Principles With principles and practices Whiteboard Sprint TDD Paring Swarming You can use them separated or combine them … stop starting, start finishing
  45. 45. Lets get some support, Where can we use it? ©
  46. 46. With your Team
  47. 47. Daily meeting what can we do to finish this item? Daily meeting
  48. 48. Daily meeting what can we do to finish this item? Daily meeting Scrum: What have you done since last meeting for my team? What will you do now for my team? What is in your way? The Team share this, one by one … Kanban: What can we do to finish this item? And we go trough ITEM by ITEM From right to left
  49. 49. Find out WHAT to DO any meeting
  50. 50. Scrumban Scrum (Scrumban)
  51. 51. Personal
  52. 52. Personal KANBAN BacklogofTODAY DoneTODAY In progress NOW Visualize
  53. 53. Personal KANBAN Visualize
  54. 54. Visualize mockup
  55. 55. Personal KANBAN 2 RULES Visualize your work + limit your WIP!
  56. 56. Source: Book Title from: Erlend Hamberg; GTD in 15 Minutes This can help to manage your personal backlog For more Projects at the same time GTD Get Things Done GTD introduced by David Allen
  57. 57. GTD Get Things Done Do it immediately if it takes less than 2 min, If not put it to your folder (area backlog)
  58. 58. Pomodoro Technique Source: staying focused
  59. 59. Pomodoro Technique Work with Time Not against Time Manage Distractions Only one thing at one-time Source: staying focused
  60. 60. staying focused Multitasking brain rules by John Medina: multitasking needs 50% more time + 50% more mistakes !
  61. 61. Pomodoro Technique If you are in Pomodoro, switch of everything that will interrupt you! - Skype - Yahoo - Email - Facebook - Phone - … > you can answer in your 5 min break … staying focused
  62. 62. Online Tools Online tools can not replace physical boards
  63. 63. Use your hands … Handmade
  64. 64. © Just start! Trust! It’s your TIME! if you don’t know your WIP, start with 1,5 and adapt
  65. 65. Books Kanban David J. Anderson Real-World-Kanban Mattias Skarin Personal Kanban Jim Benson & Tonianne DeMaria Barry Pomodoro Technique Staffan Nöteberg Help work to flow… Samantha Laing & Karen Greaves
  66. 66. Keep in touch: Email Trung Nguyen Café 264A Nam Ky Khoi Nghia Str. Dist. 3, HCM City 27. June 2015 – 9:00 am Pattern language for Team Productivity
  67. 67. Disclaimer This presentation is an ongoing work and will be updated and improved frequently. 1. Use This presentation is produced for Axon Active Vietnam and may be used: By Sebastian Sussmann for Axon Active Vietnam. 2. Content The author reserves the right not to be responsible for the whole correctness, completeness or quality of the information which is provided at this document. If some body will get problems because of using some information out from this presentation, the author will reject all claims. Because the author can not guarantee the correct use of all provided information. The author done it with the best of one's knowledge and belief This presentation / document is not complete. The author can add, remove and change it completely or partly at any time. 3. Copyright The author intended not to use any copyrighted material for the presentation. For the case it was clearly indicated he provide the copyright and source information at this page to indicate the copyright and the way of use. The copyright for any material created by the author and the company Axon Active Vietnam is reserved. Any duplication or use of objects such as images, diagrams, sounds or texts in other electronic or printed publications is not permitted without the author's agreement. 4. References: Bas Vodde ( from CSM) Sudipta Lahiri (from Kanban) Simon Roberts (from CSPO) Rena Striegel (Leadship) Henrik Kniberg (Agile Product Ownership in a Nutshell) Mike Cohn (Effort)