Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Kanban Basics

91 914 vues

Publié le

Kanban is the simplest approach which is currently used in software development. Since Kanban prescribes close to nothing there are often a lot of basic questions about the method.

The presentation depicts what Kanban is generally using Scrum as a reference point. Then it presents a series of situations to answer basic questions about working with Kanban

Publié dans : Technologie, Business
  • Your opinions matter! get paid for them! click here for more info...●●● http://ishbv.com/surveys6/pdf
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici
  • You can now be your own boss and get yourself a very generous daily income. START FREE...●●● https://tinyurl.com/realmoneystreams2019
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici
  • Secrets to making $$$ with paid surveys... ●●● http://ishbv.com/surveys6/pdf
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici
  • Nice !! Download 100 % Free Ebooks, PPts, Study Notes, Novels, etc @ https://www.ThesisScientist.com
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici
  • Kanban emphasises on measuring flow rather that setting targets for team members. In this approach every phase in the process is important. Efficiency can be achieved only by keeping the process under control, reducing constraints and bottlenecks and optimizing the flow. This is what is important to the end users. They want the order to be delivered. Source: www.scrumstudy.com
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici

Kanban Basics

  1. 1. Kanban Basics Pawel Brodzinski pawel.brodzinski@gmail.com http://blog.brodzinski.com
  2. 2. What is Kanban? Kanban is an approach to change management. It isn’t a software development or project management lifecycle or process. David Anderson
  3. 3. Kanban in a nutshell 3rules 1tool simple mechanics Visualize workflow Limit WIP Measure flow
  4. 4. Scrum in a nutshell Small, cross-functional teams Product split into small, roughly estimated, stories Iterations Continuous improvement
  5. 5. Scrum versus Kanban Team KANBANSCRUM
  6. 6. Scrum versus Kanban Iterations Iteration length [weeks] 0 2 4 8 16 32 64 . . . KANBAN SCRUM
  7. 7. Scrum versus Kanban Product management Product Backlog Sprint Backlog Shippable Product 2-4 weeks 1 day KANBANSCRUM
  8. 8. Scrum versus Kanban Continuous improvement KANBANSCRUM Retrospectives
  9. 9. Scrum versus Kanban Board KANBANSCRUM
  10. 10. Why Kanban? Sometimes time-boxing doesn’t work Easy integration with other processes Organizational constraints Minimal entry barrier
  11. 11. How to start with Kanban? 1. 2.
  12. 12. Kanban kick start The most basic board
  13. 13. Kanban kick start Limits
  14. 14. Kanban kick start Backlog
  15. 15. Kanban kick start SDLC
  16. 16. Kanban kick start Transition criteria
  17. 17. Kanban kick start Board summary Map current process Start simple Improve over time
  18. 18. Kanban kick start Tasks: MMF MMF = Minimal Marketable Feature *- if possible… *
  19. 19. Kanban kick start The board – day 0
  20. 20. Kanban kick start The board – day n
  21. 21. Kanban kick start Dealing with backlog
  22. 22. Kanban kick start Todo queue
  23. 23. Kanban kick start Responsibility for tasks
  24. 24. Kanban kick start Testing
  25. 25. Kanban kick start Blockers
  26. 26. Kanban kick start Blockers
  27. 27. Kanban kick start Priority lane
  28. 28. Kanban kick start Multiple projects
  29. 29. Kanban kick start Multiple projects
  30. 30. Kanban kick start Deployment
  31. 31. Kanban kick start Deployment
  32. 32. Kanban kick start Continuous improvement
  33. 33. Kanban kick start Estimation WIP Cycle time
  34. 34. Kanban is (only) a tool
  35. 35. Kanban Many of results of Kanban are counterintuitive. What appears to be very mechanical approach – limit WIP and pull work – actually has profound effects on people and how they interact with one another. David Anderson
  36. 36. Thank you Questions? Pawel Brodzinski pawel.brodzinski@gmail.com http://blog.brodzinski.com http://vsoft.pl @pawelbrodzinski