Kanban: Fly Different - An Introduction v1.3

3,691 views

Published on

A gentle, fun introduction to the Agile Kanban nethodology. It uses a metaphor from aviation to make it more fun.

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,691
On SlideShare
0
From Embeds
0
Number of Embeds
1,986
Actions
Shares
0
Downloads
68
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide
  • Image Credits: Blue Angels Navy Acrobatic team and Flickr.\n
  • \n\n
  • \n\n
  • Image Credit: Movie Apollo 13\n
  • \n\n
  • \n\n
  • Image Credits: Flickr.\n
  • \n\n
  • \n\n
  • \n\n
  • Image Credits: Flickr and the US Air Force Acrobatic Team\n
  • \n\n
  • Image Credits: Crisp AB Stockolm, and Henrik Kniberg\nhttp://www.crisp.se/kontakt\n\n\n
  • \n\n
  • \n\n
  • Image Credits: Kanban book by David Anderson.\nhttp://www.amazon.com/Kanban-David-J-Anderson/dp/0984521402\n
  • Image Credits: Kanban book by David Anderson.\nhttp://www.amazon.com/Kanban-David-J-Anderson/dp/0984521402\n
  • Image Credits: Kanban book by David Anderson.\nhttp://www.amazon.com/Kanban-David-J-Anderson/dp/0984521402\n
  • Image Credits: Flickr.\nStory taken from David Anderson’s Kanban book page 11, explanation provided by myself.\n\nBook by David Anderson.\nhttp://www.amazon.com/Kanban-David-J-Anderson/dp/0984521402\n\n\n
  • Image Credit: US Navy, image from Flickr. \n
  • \n\n
  • \n\n
  • Image Credit: Italian Air Force, Tricolori Acrobatic Team. \nSource found via Google Images. \n
  • Kanban: Fly Different - An Introduction v1.3

    1. 1. Agile Kanban: Fly Different v1.3by Joseph Hurtadojoseph@agilelion.comTwitter: @josephhurtado | Web:AgileLion.com1
    2. 2. What will I learn?Why we need Agile Kanban?What is Kanban anyway?How can I use it for Software Development?How can I “Fly Kanban” using Agile Zen?2
    3. 3. Credits - People and PhotosKanban boards and inspiring content from DavidAndersons Kanban Book.Henrik Kniberg slides, and solid content on his blog.Photos: Blue Angels, and Thunderbirds - US Navy and AirForce Teams. The last photo is from Italys Aerobatic Team:Frecce Tricolori.Several Photos and Illustrations via Flickr and Google, thatdeal with flight, crews and Apollo 13.3
    4. 4. I.“Houston we have aProblem”4
    5. 5. SW Planning ProblemsChanging RequirementsWrong Assumptions: WaterfallEstimation ChallengesBlack box DevelopmentExternal Change Agents5
    6. 6. Early SolutionsIterative DevelopmentWaterfall planning but divided in phasesHeavy use of Engineering Concepts and toolsLocked DeadlinesThe de-facto standard todayHouston, We still have a problem! :-)6
    7. 7. II. There must be aBetter Way!7
    8. 8. Agile Manifesto - Feb 200117 developers introduced the world into the "Agile Way":Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a plan8
    9. 9. Key Agile MethodologiesXP - Extreme Programming (Kent Beck)Pair Programming, thorough testing, emphasis on littleor no documentation, very “fanatical approach”Scrum (Ken Schwaber, Jeff Sutherland)Daily Stand-ups, Scrums, Reflections, Integrated QA/User/Teams, Velocity, Poker Estimation, etc.Very detailed "Agile recipe" --> All or nothing9
    10. 10. Agile or Fragile?Going too Agile:Zero documentationBlindly following the recipeWild ExpectationsToo much too soonKanban addresses those areas through two principles:Kaizen (Continuos Improvement, in gradual steps)Simplicity (simple principles that easily scale)10
    11. 11. III. Fly Different: Kanban11
    12. 12. What is Kanban?Kanban in Japanese means “Visual Board.”It relates to a system, where one Kanban sign signalsanother member of the team that we can “Pull” workfrom one phase to another.Early Kanban was adopted in Japan by Toyota forLean Manufacturing (TPS - late 1940s to 1970s)Agile Kanban for Software Development however isquite recent: from 2004 to 2010.Agile Kanban was born in the software industry atMicrosoft and Corbis. The first systems were related toQA and Development inside Waterfall Organizations!12
    13. 13. Kanban is very Light13
    14. 14. Kanban’s 3 Principles1. Visualize the WorkflowBy using Kanban Boards2. Limit Work in Progress - LWIPBy imposing limits on the size of some stages you force the teams andindividuals to focus.Also when WIP is less, work travels faster. (batch size)3. Keep Improving Flow or KaizenBy thinking and discovering ways to improve on what we doBy using any tool or technique that helps you do it.14
    15. 15. Kanban’s Minimal Flow1. Ready or Queue EntryThink of it as the relevant backlog2. WorkingTasks or stories you are working on now3. DoneCompleted stories or tasks15
    16. 16. Kanban’s Flow Expanded16
    17. 17. Kanban’s Sticky Boards17
    18. 18. Kanban’s Sticky Boards18
    19. 19. Optional Slide: A Pull SystemImperial Palace in Tokyo is actually a reallife Kanban Pull System.Each visitor receives a “token” the visitorhas to keep the token until he leaves, thenhe returns the token into the pool: Asimple Kanban System!Token = Story. The system has LWIP fornumber of tokens, and three phases:Queue into the palace, LWIP inside thePalace, and Exit of the Palace (wheretokens are returned and LWIP isreplenished, to “pull” visitors!)19
    20. 20. IV. "We dont need roadsany more"20
    21. 21. No More Boards!Agile Zen is a web 2.0 board that replaces and enhances anything a StickyBoard can do. Advantages over other solutions:Right balance of featuresDesktop app. experience on a browserElegant UIRequirements:Firefox 3.x or later (avoid Chrome or Safari for now)Internet ConnectionMac or PC21
    22. 22. Learning Session LabMinimal Kanban Process: Ready - Working - DoneHow Process Flow WorksStory CreationStory Movement and common SituationsStory Features22
    23. 23. The End! Now Fly Solo.23

    ×