Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Maintenance fun using Kanban

4.545 visualizaciones

Publicado el

Maintenance is a mandatory part of any successful software product. This stage significantly differs from development phase. And standard project management approaches (e.g. Scrum) do not work properly here. And here comes Kanban – method that works just great for support teams.

Publicado en: Tecnología, Empresariales
  • Inicia sesión para ver los comentarios

Maintenance fun using Kanban

  1. 1. <ul><li>Maintenance fun using Kanban </li></ul><ul><li>Sergii Maliarov </li></ul><ul><li>Lohika Systems </li></ul>
  2. 2. <ul><li>How maintenance takes away fun </li></ul><ul><li>How Kanban brings back fun on a real-life example </li></ul><ul><li>Some tips from my experience </li></ul><ul><li>And of course some nice cats pictures </li></ul>What we’re going to see?
  3. 3. <ul><li>8 years in software development, 6 years in Java development </li></ul><ul><li>Worked on different projects with different processes used (Scrum, RUP, different mixes) </li></ul><ul><li>For the last year working as a Lead Engineer in Lohika Systems on a project that first was managed using Scrum and after that moved to Kanban </li></ul><ul><li>[email_address] , [email_address] </li></ul>About me
  4. 4. <ul><li>New task may arrive any time </li></ul><ul><li>Some bugs may need to be fixed immediately </li></ul><ul><li>There is no release date </li></ul><ul><li>Big tasks can arrive </li></ul><ul><li>You may need several teams (e.g. development team, release team, etc) </li></ul><ul><li>So Scrum or RUP are not really great for maintenance </li></ul><ul><li>And what does it bring us? </li></ul>Support stage specifics
  5. 5. <ul><li>A lot of time is wasted on meetings, planning, etc </li></ul><ul><li>You may stuck for days with some problem </li></ul><ul><li>Customer is not satisfied </li></ul><ul><li>Developer is bothered with things other than development </li></ul>Fun goes away
  6. 6. <ul><li>Only three principles: </li></ul><ul><li>Visualize the workflow </li></ul><ul><li>Limit Work In Progress </li></ul><ul><li>Measure the lead time </li></ul><ul><li>Let’s see how it works on a real example </li></ul>Here comes Kanban
  7. 7. <ul><li>Use any tool you want. We tried Google Docs and GreenHopper (JIRA plugin) </li></ul><ul><li>Use as many columns as you need </li></ul><ul><li>If some column is constantly empty or contains 1 item – you don’t need that column. Or you may descrease its WiP. </li></ul>Visualize the workflow
  8. 8. <ul><li>Probably the most important principle </li></ul><ul><li>Classic WiP is n where n is number of developers </li></ul><ul><li>We are using n+1 </li></ul><ul><li>Item should go through cycle as fast as it’s possible </li></ul>Limit Work In Progress
  9. 9. <ul><li>Don’t forget to add or remove columns to optimize the lead time </li></ul><ul><li>Add releases and cycle time if you want. Like we did </li></ul>Measure the lead time
  10. 10. <ul><li>Just-in-time </li></ul><ul><li>Few teams may work on one board </li></ul><ul><li>Big tasks can be taken </li></ul><ul><li>Very transparent process </li></ul><ul><li>Customer is happy </li></ul>Here comes the fun
  11. 11. <ul><li>Experiment </li></ul><ul><li>Take what works for you from another processes </li></ul><ul><li>Don’t forget about the fun for all </li></ul>What else can be done
  12. 12. Resources Henrik Kniberg Lean from the Trenches Henrik Kniberg, Mattias Skarin Kanban and Scrum. Making the most of both
  13. 13. Question and Answers