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.


198 visualizaciones

Publicado el

This presentation provides a brief about kanban and the difference between it and scrum.

Publicado en: Tecnología
  • Sé el primero en comentar

  • Sé el primero en recomendar esto


  1. 1. Kanban Method Created By : Hala Mehana – Business Analyst
  2. 2. Agenda  What is Kanban  Kanban in a nutshell  Continuously improve  Kanban Vs. Scrum  How to get started with Kanban
  3. 3. What is Kanban  Kanban is a new technique for managing a software development process in a highly efficient way  Kanban is a method for managing knowledge work with an emphasis on just-in-time delivery while not overloading the team members  It uses a work-in-progress limited pull system as the core mechanism to expose system operation (or process) problems and stimulate collaboration to continuously improve the system  Visualisation is an important aspect of Kanban as it allows understanding of the work and the workflow
  4. 4. Kanban in a nutshell  3 Rules  Visualize the workflow  Split the work into pieces (small task), write each item on a card and put on the wall  Use named columns to illustrate where each item is in the workflow (To do, Dev., Test, etc.)  Limit WIP (work in progress)  assign explicit limits to how many items may be in progress at each workflow state “Column”  Measure the lead time  average time to complete one item, sometimes called “cycle time”  optimize the process to make lead time as small and predictable as possible ”sprint length in scrum”
  5. 5. Continuously improve  Its Important Principle in Kanban  Once the Kanban system is in place, it becomes the cornerstone for a culture of continuous improvement. Teams measure their effectiveness by tracking flow, quality, throughput and lead times.
  6. 6. Kanban Vs. Scrum  Scrum is more prescriptive “has more rules to follow” than Kanban  Scrum prescribes 3 roles: Product Owner, and Scrum. While Kanban doesn’t prescribe any roles at all  Scrum is based on time boxed iterations  In Kanban, You can choose when to do planning, process improvement, and release. You can choose to do these activities on a regular basis or on-demand  Scrum board is reset between each iteration while Kanban board is normally a persistent thing – you don’t need to reset it and start over  Scrum board is owned by exactly one Scrum team “Cross functional”  Kanban, cross-functional teams are optional, and a board doesn’t need to be owned by one specific team. A board is related to one workflow, not necessarily one team.
  7. 7. Kanban Vs. Scrum – Part 2  A Scrum team will only commit to items that they think they can complete within one iteration.  Kanban teams set the lead time and level the flow to help them to discover bottlenecks early, there is no explicit rule stating that items must be small to fit into a specific time box  In Scrum there is daily meeting “Standup” and there is no rule in Kanban stating this but we can use this roles from scrum   In Scrum, burn down charts are prescribed, While In Kanban, no particular type of chart is prescribed. But Team are allowed to use any type of chart  In Scrum, Estimation prescribed. In Kanban, Estimation optional  In Scrum, Prescribes a prioritized product backlog . In Kanban, Prioritization is optional.
  8. 8. So, How to get started with Kanban  Backlog source > Documentation  Shall we need to prioritize the backlog ? The prioritization process  Yes, we will prioritize the user stories and show it in board based on cards colors  When we can say that product is ready for end user “Team agreement”  Tested and bug free  How we will break down the tasks  Development Team will provide the tasks  Who will be responsible to assign Tasks  Development Team  Design our workflow board “Board columns”  Backlog, BDD, Development, Testing, Done  Initial WIP and when user can move task from column to another  Lead time “Week”
  9. 9. How to get started with Kanban – 2  Decide the roles  Do We need any rules to be stated ? “No”  Decide the meetings  Planning meeting ? Every Sunday  Daily Stand up ? Every day  Retrospective ? Every Thursday
  10. 10. Thank You