Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Introduction to kanban calgary .net user group - feb 6

February 6, 2013 Calgary .NET User Group Lunch Seminar series - An introduction to Kanban presented by Dave White of Imaginet ( and board member at Lean Kanban University (

  • Login to see the comments

  • Be the first to like this

Introduction to kanban calgary .net user group - feb 6

  1. 1. Introduction to KanbanDiscover How The Kanban Method Can Help Supercharge Your Organization(and dispelling a few myths along the way)
  2. 2. Your SpeakerDave WhiteTechnical Program DirectorImaginet Resources Corp. - Microsoft Partner• Management Board - Lean-Kanban University• Advisory Board - LKU’s Accredited Kanban Training program – Accredited Kanban Trainer (AKT) – Kanban Coaching Professional (KCP)• numerous Microsoft certifications – Microsoft Certified Trainer• 15 years of experience• specializes in helping organizations mature their software development and information technology practices• passionate about Application Lifecycle Management tooling, techniques, and mindsets and regularly talks and teaches on a wide range of ALM topics
  3. 3. Why I Went Looking
  4. 4. Symptom Lead time for Feature: 12 months “The business unit built that?” “That isn’t what we wanted.” Release Date: in 9-12 months“We’ve got 100s of bugs waiting.” “We’re waiting on other teams.” “We have to get this out right away!” ETA of Bug Fix: ??? “That feature doesn’t matter anymore.”“We don’t have staff for that project/work” “We’re really late.”
  5. 5. ProblemLots of work, not enoughcapacity• Quality suffers• Features delayed• Technical debt• How much… • Work?? • Capacity??Disengaged people!
  6. 6. Another Problem Why isthis still aproblem?
  7. 7. My Journey
  8. 8. What We’ve Tried So FarWhat’s Prevalent • Chaos • Waterfall • ScrumStill Looking… • Chaos is … chaotic • Waterfall not well suited • Large batch, single pass, long duration workflow • If we just do it better…  • Scrum is better suited • prescriptive without understanding context
  9. 9. And…Adoption is hard! (People are weird!)
  10. 10. Something different…KanbanMethod
  11. 11. WAIT!! kanban?kanban system?Kanban Method?
  12. 12. The Kanban Method is……an approach to incremental, evolutionary process change for organizations.
  13. 13. Kanban MethodSo Why The Kanban Method • Designed to… • Be context sensitive kaizen • Foster organizational learning • Be evolutionary • Simple rules to govern complex systems • Teams of people are systems • Agile methods can emerge • Fully embraces Agile Manifesto • Lean methods can emerge • Fully embraces Lean Software Development Principles • Tactic-agnostic • Catalyst for organizational improvement To make better
  14. 14. Kanban Method agileKanban Method • 4 principles lean • 6 practices… and it’s easy to get started
  15. 15. Kanban Method Principlesstart with what you do now agree to pursue incremental, evolutionary changeinitially, respect current roles,responsibilities & job titles encourage acts of leadership
  16. 16. 6 CORE PRACTICESvisualizelimit WIPmanage flowmake process policies explicitdevelop feedback mechanismsimprove collaboratively
  17. 17. Visualize
  18. 18. Limit WIP
  19. 19. Manage Flow
  20. 20. Make Process Policies Explicit Explicit PoliciesExplicitPolicies
  21. 21. Develop Feedback Mechanisms
  22. 22. Improve Collaboratively with Science!
  23. 23. WARNING!“Kanban is an unapologetic, realistic,representation of the law of physics.“ – Daniel Vacanti @danvacanti
  24. 24. WHY ARE WE DOING ALL THIS?To create a LEARNING capability in our organizationthat enables CONTINUOUS IMPROVEMENT!We must…• Have time to discover and implement kaizen opportunities• Create theories and experiment• Give ourselves opportunities to fail• Learn from your mistakes
  25. 25. The Benefits I’ve SeenBenefits of Agile plus…• Deeper understanding of demand and capacity• Constantly improving teams• Exposed Constraints at multiple levelsHappy People
  26. 26. Better Teams = Better Business • Predictability • Agility • Risk Management • Governance • Change Management
  27. 27. Solutions Are Just Waiting to be Discovered• Work is understood! • Designed to understand demand • Discover capacity • People improve the system• People are engaged! • Empowered • Own the improvements • Pull work• Solving Our Problem • Our processes are important • Learning-focused approach
  28. 28. Myths About Kanban
  29. 29. Myth #1Kanban Method is an Agile Methodology
  30. 30. Myth #2Kanban Method competes directly with Scrum
  31. 31. Myth #3Kanban doesn’t have iterations
  32. 32. Myth #4Kanban works for Dev Ops, not for projects
  33. 33. Myth #4Kanban is a mini-waterfall methodology
  34. 34. How You Can Get Here
  35. 35. Where to Start1. Find a Leader2. Get Foundational Knowledge3. Visualize Your Work4. Limit your WIP5. Focus on HIGH Quality
  36. 36. Call to Action• Engage• Attend our Accredited Core Kanban class with or without our Visual Studio day• Reach out to Dave • @agileramblings or• Join the Community! • Lean-Kanban University • Lean Kanban North America 2013 in Chicago! • kanbandev group (Yahoo) • Limited WIP Society or your local Kanban User Group
  37. 37. Imaginet’s New Visual Studio 2012 Website!Visit Imaginet’s new Visual Studio 2012 website, your one-stophub for all your Visual Studio 2012 needs!
  38. 38. Thank you twitter: @justimaginet