Introduction to Kanban
•
6 likes•4,538 views
Introduction to the Kanban as applied to software development. Delivered in Kirkland, WA in Nov 2011 by Dynacron Group. Dynacron Group is an Agile software technology consulting firm. We provide training, consulting, and hands-on implementation for software projects in the Pacific Northwest.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (17)
Similar to Introduction to Kanban
Similar to Introduction to Kanban (20)
More from Will Iverson
More from Will Iverson (12)
Recently uploaded
Recently uploaded (20)
Introduction to Kanban
- 2. Presenters • Will Iverson • Special Guest: • CTO, Dynacron Group • Peter Turner • Author, Architect Scrum Master • Elise Shapiro • Sr. Technical Project Manager • Scrum Master, former SysAdmin
- 3. Audience & Schedule • Intended Audience: Software Technology Management Professionals • 3:00 PM - Doors Open! Social Mixer with Appetizers and Beverages • 3:30 PM - Presentation • 4:30 PM - Open Discussion, Coffee & Appetizers
- 4. Agenda • Assumptions (Scrum & Waterfall) • Kanban Overview • Key Kanban Concepts • Mapping Kanban • Existing Process, Tools, Roles • Real World Examples • Q&A
- 5. Assumptions: Project • Waterfall • Series of phased gates • Highly structured roles & responsibilities • Scrum • 2-4 week incremental work • Focus on “get it done” over roles & responsibilities • Discuss: • Pros & Cons with both models?
- 6. Assumptions: Org Structures • Cross-functional matrix • Dev, QA, PM, Ops “own” resources • Virtual teams created from matrix • Team-based structure • PM owns project • Discuss: • Pros & cons of both models? • Fit with process choice? • Change management?
- 7. Kanban Overview • Workflow Visualization • WIP Limits • Flow Management • Explicit Process Policies • Incremental Collaborative Improvement
- 8. Workflow Visualization • Project Report • Standard Scrum Board • Kanban Board[s]
- 10. WIP Limits • Problem: To Do Mushball • Problem: Not Enough Work @ Right Place To Do In Progress Done Epic Story Design Test Dev Validate
- 12. Flow Management • How long are things stuck? • How do you know what to fix? • How do you know if changes actually improved things? • What metrics are you tracking? Epic Story Design Test Dev Validate
- 14. Explicit Process Policies Story As a [user] I want to [perform action] Prioritied Example: Clear definition so that I can [do something] of done for each lane Design Workflow Mockups Matched to Style Guide Test Acceptance Criteria Negative Test Criteria Tests associated with Clear Clear proper tier Development Tests Pass Build Works Release Produced
- 15. Incremental Collaborative Improvement • Review bottlenecks • E.g. Scrum Retrospectives • Suggest improvements • Perform experiments & track results with metrics • Scientific method, not opinion
- 16. Mapping Kanban To Existing Process, Tools, Roles • First board: From Scrum to ScrumBan
- 17. Scrumban: Scrum + Kanban • Less emphasis on (lengthy) sprint planning meetings • Keep sprint planning, daily standups, retrospectives • Make them higher level • Move from burndown charts to Kanban style-reports • Tends to be better for both line staff & management
- 19. Real World Kanban Examples • Software Development Team (Elise) • Blending Scrum with cross-functional matrix team • Software Development Team (Pete) • More pure Lean/Kanban • Intake Kanban • Feature definition & Lean UX paper prototyping - get rapid feedback on potential products / product features • Operational/Maintenance Team (Pete) • Personal Kanban –Workplace (Elise)
- 20. Kanban with Scrum Artifacts
- 21. Star Wars Team - Before
- 22. Star Wars Team - After
- 23. Star Wars Team - Detail
- 24. Ops Team – Back of Board
- 25. Ops Team – Front Before
- 26. Ops Team – Front After
- 27. Ops Team – Front Detail
- 28. Ops Team – Front Detail
- 29. Personal Kanban at Desk
- 30. Personal Kanban in Office
- 31. Tools • http://agilescout.com/best-kanban-tools/ • 25+ Tools Listed • http://www.toolsjournal.com/tools-world/item/142- kanban-tools • 15+ Tools Listed • Many existing tools adding support • E.g. Atlassian Greenhopper, Rally, VersionOne, etc.
- 32. Tool: AgileZen
- 33. Challenges & Observations • Make the board work for you & your team! • No such thing as one true board • Keeping the value stream filled • You need to get stuff to the ready to work column somehow! • Scrum + Kanban = tactics, still need strategy • Agile & Agile Manifesto = human values declaration • Discuss: “Soulless Agile”
- 34. Q&A