1 / 27

Kanban

Kanban. “like playing F risbee … with your dog!”. MissedMemo@GMail.com. m e. You?. Agenda:. History: Agile pragmatism/fundamentalism seesaw Misconceptions: What Kanban is – and is NOT! Mechanics: How & why it works Questions, discussion, sample Kanban boards….

rhys
Download Presentation

Kanban

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Kanban “like playing Frisbee … with your dog!” MissedMemo@GMail.com Andrew Lloyd 6/20/2011

  2. me

  3. You?

  4. Agenda: • History: Agile pragmatism/fundamentalism seesaw • Misconceptions: What Kanban is – and is NOT! • Mechanics: How & why it works • Questions, discussion, sample Kanban boards…

  5. Incompetence is no barrier to success ! Dev. Process V ^ Commercial

  6. Agile Fundamentalism: "Critics of the first edition have complained that it tries to force them to program in a certain way... I'm embarrassed to say that was my intention... in this edition, I have tried to rephrase my message in a positive, inclusive way“ -- Kent Beck, “Extreme Programming Explained”2nd ed.

  7. “Agile” defined by Principles (not specific practices) • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. • Business people and developers must work together daily throughout the project. • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. • Working software is the primary measure of progress. Agile processes promote sustainable development. • The sponsors, developers, and users should be able to maintain a constant pace indefinitely. • Continuous attention to technical excellence and good design enhances agility. • Simplicity--the art of maximizing the amount of work not done--is essential. • The best architectures, requirements, and designs emerge from self-organizing teams. • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

  8. Scrum...

  9. Harsh Realities…

  10. Kanban “Kanban is not a software development cycle methodology or an approach to project management. It requires that some process is already in place so that Kanban can be applied to incrementally change the underlying process“ -- David Anderson (originator of Kanban)

  11. Kanban is Simple! • Visual representation of your ACTUAL process (3 Requirements)

  12. Scrum board (over-simplified): To Do In Progress… Done ! A B C D E

  13. Scrum board vs. Kanban board: To Do In Progress… Done ! 2 A B C D D E

  14. Kanban is Simple! • Visual representation of your ACTUAL process • Limit “Work in Progress” (WIP) (3 Requirements)

  15. Demo… On Deck Dev. Test Backlog Done ! (2) (2) (1) A C B F E Done D G K J H M N

  16. Demo… On Deck Dev. Test Backlog Done ! (2) (2) (1) A C E B K F J Done D G H M N

  17. Demo… On Deck Dev. Test Backlog Done ! 2 (2) (2) (1) A K B G F J E Done D C H M N

  18. Demo… On Deck Dev. Test Backlog Done ! (2) (2) (2) A B G F J K E Done D C H M N

  19. Kanban is Simple! • Visual representation of your ACTUAL process • Limit “Work in Progress” (WIP) • Track and optimize “flow” (3 Requirements)

  20. Cumulative Flow Diagram: On Deck Development By tweaking WIP ! Test Lead Time = 6 days Done! # Featuresin Each Column WIP on day #4 = 9 ( seek to MINIMIZE ) # Days

  21. Kanban “like playing Frisbee … with your dog!”

  22. So, why all the hate? “The surprising thing for me is that many smart Agile people - people I know to be intelligent insightful people - seem bugged by Kanban... I'm seeing Agile people behave as strangely about Kanban as traditional process folks behaved about Agile. They seem threatened." -- Jeff Patton, (Agile speaker and author)

  23. The Pirate’s Code: “The (Pirate's Code) is more what you'd call 'guidelines' than actual rules." -- Captain Barbossa, Agile pragmatist, “Pirates of the Carribean”, 2003

  24. Kanban Board Examples:

  25. Definitive Resources: Kanban and Scrum: Making the Most of Both by Henrik Kniberg & Mathias Skarin (http://www.infoq.com/minibooks/kanban-scrum-minibook) * Kniberg also authored Scrum and XP From The Trenches Kanban: Successful Evolutionary Change for Your Technology Business by David J. Anderson

  26. a Confession…

  27. Questions / Discussion…

More Related