Implementing Scrum with Kanban
•
2 likes•159 views
The document provides an overview of implementing Scrum with Kanban. It begins with definitions of Scrum and Kanban principles and practices. It then compares Scrum and Kanban approaches and outlines how Scrum events, roles and artifacts can be combined with Kanban practices like limiting work in progress, visualizing workflow and metrics. The remainder discusses the experience of one team that adopted Scrum with Kanban, including defining their workflow, setting work in progress limits and evolving their approach over time based on metrics.
Report
Share
Implementing Scrum with Kanban
- 1. INFRASTRUCTURE & OPERATIONS Implementing Scrum with Kanban Tiffany Scott Scrum Master and Agile Coach scott17@nationwide.com
- 2. INFRASTRUCTURE & OPERATIONS About Me Tiffany Scott Scrum Master and Agile Coach at Nationwide Insurance www.linkedin.com/in/tiffanyjscott TiffanyJScott@gmail.com @gr8scottfr33
- 3. INFRASTRUCTURE & OPERATIONS • Brief overview of Scrum • Overview of Kanban principles and practices • Comparison of Scrum and Kanban • Overview of Scrum with Kanban • Basic Metrics of Flow • Visualizing Metrics of Flow • Experience Report Agenda
- 4. INFRASTRUCTURE & OPERATIONS 4 Daily Scrum Sprint Review Sprint Retro Sprint Planning Scrum Sprint 1 month or less Scrum Master Product Owner Development Team Process Improvement Item Sprint Backlog Sprint Goal Definition of “Done” Stakeholders Increment Scrum Team Roles Artifacts Events Product Backlog Adapted from JodranJob based on the 2017 Scrum Guide
- 5. INFRASTRUCTURE & OPERATIONS 5 Foundational Principles of Kanban Change Management: 1. Start with what you are doing now 2. Agree to pursue incremental, evolutionary change 3. Encourage acts of leadership at all levels Service Delivery: 1. Understand and focus on customer needs and expectations 2. Manage the work; let people self-organize around it 3. Evolve policies to improve customer and business outcomes
- 6. INFRASTRUCTURE & OPERATIONS 6 Core Practices of Kanban 1. Visualize the workflow 2. Limit work in progress (WIP) 3. Manage flow 4. Make policies explicit 5. Implement feedback loops 6. Improve collaboratively, evolve experimentally using data and models
- 7. INFRASTRUCTURE & OPERATIONS Comparison of Scrum and Kanban Scrum Kanban • Definition of Done = Make policies explicit • Scrum events = Implementing feedback loops • Retrospectives = Improve collaboratively • Selecting PBIs for Sprint = Limiting WIP • Visualize the workflow • Manage flow Mandatory • roles • events • artifacts • timeboxes
- 8. INFRASTRUCTURE & OPERATIONS This Is Not A Workflow
- 9. INFRASTRUCTURE & OPERATIONS Typical Dev Team Board Day 1 – 3
- 10. INFRASTRUCTURE & OPERATIONS Typical Dev Team Board Day 8 – 10
- 11. INFRASTRUCTURE & OPERATIONS Work in Progress Limits in Kanban • Read from right to left • Forces existing work to be finished before starting new work, which creates a Work in Progress limited pull system
- 12. INFRASTRUCTURE & OPERATIONS Work in Progress Limits in Kanban • What should we do?
- 13. INFRASTRUCTURE & OPERATIONS Basic Metrics of Flow • Work in Progress (WIP) – number of work items started but not finished • Work Item Age – amount of time between when a work item started and the current time • Cycle Time – Amount of time between when a work item starts and when a work item finishes • Throughput – number of work items finished per unit of time • Flow metrics require the team to track the start date and finished date of each work item
- 14. INFRASTRUCTURE & OPERATIONS Visualizing Cycle Time with Scatterplots How do we interpret a bunch of random dots? Use percentile lines • Count up all the dots and multiply by a percentage • Draw the line such that the percentage of the dots chart fall below that line
- 15. INFRASTRUCTURE & OPERATIONS Cycle Time Scatterplots with Percentile Lines
- 16. INFRASTRUCTURE & OPERATIONS Visualizing Throughput – Line Chart
- 17. INFRASTRUCTURE & OPERATIONS Visualizing Work Item Age
- 18. INFRASTRUCTURE & OPERATIONS 18 Daily Scrum Sprint Review Sprint Retro Sprint Planning Sprint 1 month or less Scrum Master Product Owner Development Team Process Improvement Item Sprint Backlog Definition of “Done” Stakeholders Increment Scrum Team Roles Artifacts Events Sprint Goal Product Backlog Work Item Age WIP TH CT Service Level Expectation Definition of Workflow Scrum with Kanban Adapted from JodranJob based on the 2017 Scrum Guide and 2018 Scrum with Kanban Guide
- 19. INFRASTRUCTURE & OPERATIONS History of The Team • Formed in May 2018 with a mandate to become full stack engineers –1 new Scrum Master, 3 Solution Engineers, 1 Provisioner, 1 Firewall Engineer • Supports the enterprise by delivering environments • Became an end-to-end team with the addition of a Middleware Engineer in September 2018
- 20. INFRASTRUCTURE & OPERATIONS Why Kanban? The Team • Disillusioned with Scrum and estimating • Electronic visual management system was insufficient • Dissatisfied with current throughput • No time for polyskilling Tiffany • Couldn’t tell our customers when anything would be done • Metrics were visualized in unusual ways or suboptimal
- 21. INFRASTRUCTURE & OPERATIONS How Did We Start? • The game is played in teams of four to six people • Each team has a playing board representing a Kanban task board, and a collection of story cards representing work to be done • Teams compete to maximize profit by optimizing the flow of work
- 22. INFRASTRUCTURE & OPERATIONS 1. Defined the workflow 2. Determined a global Work in Progress limit 3. Allocated Work in Progress limits per step in the workflow 4. Visualized the current work on the board Defining Workflow & Setting WIP Limits
- 23. INFRASTRUCTURE & OPERATIONS • Team set a goal of 30 days to deliver an environment –07 days to design a solution –14 days to build Setting Internal SLEs
- 24. INFRASTRUCTURE & OPERATIONS Evolution of Scrum Events & Artifacts • Daily Scrum • Sprint Planning • Sprint Review • Sprint Retrospective • Definition of Done
- 25. INFRASTRUCTURE & OPERATIONS Cycle Time and Throughput Over Time
- 26. INFRASTRUCTURE & OPERATIONS Where Do We Go Next? • Work in Progress limits upstream • Continue persuading our sister teams to implement WIP limited pull systems • Analyzing flow efficiency • Rebuild the team • Forecasting using Monte Carlo simulations
- 27. INFRASTRUCTURE & OPERATIONS Things You Can Do Now • Analyze your cycle time and throughput • Review or define your workflow –Make sure your workflow reflects what you do now • Review your visual management system (VMS) –Make sure your VMS reflects your workflow • Try out work in progress limits • Continuously improve by inspecting and adapting
- 28. INFRASTRUCTURE & OPERATIONS Additional Resources • The Scrum Guide – Ken Schwaber and Jeff Sutherland • Essential Kanban Condensed – David J. Anderson and Andy Carmichael • The Kanban Guide for Scrum Teams – Scrum.org and Daniel S. Vacanti • Actionable Agile Metrics for Predictability: An Introduction – Daniel S. Vacanti • Focused Objective – Free forecasting tools • Practical Kanban: From Team Focus to Creating Value Kindle Edition – Klaus Leopold
- 31. INFRASTRUCTURE & OPERATIONS Throughput July 2018 – May 22, 2019
- 32. INFRASTRUCTURE & OPERATIONS Cycle Time June 2018 – May 22, 2019
- 33. INFRASTRUCTURE & OPERATIONS Cycle Time June 2018 • Didn’t get anything done :o( • Team member out a lot due to memory issues from a car accident
- 34. INFRASTRUCTURE & OPERATIONS Cycle Time July 2018 • Team member with memory issues returns with limited capacity
- 35. INFRASTRUCTURE & OPERATIONS Cycle Time August 2018 • Played GetKanban game • Built first version of the Kanban board • Discovered there were 17 work items in Design
- 36. INFRASTRUCTURE & OPERATIONS • Still working through the work items in Design • Team member still having memory issues • Different team member not coping well with life issues • New team member joins • Changed definition of done to include new team members work • Acknowledging cycle time will extend Cycle Time September 2018
- 37. INFRASTRUCTURE & OPERATIONS Cycle Time October 2018
- 38. INFRASTRUCTURE & OPERATIONS Cycle Time November 2018 • Changed the workflow to add a step to verify the customer was ready to start • Resulted in redirecting customers to self- service options • Demand started to slow due to holidays
- 39. INFRASTRUCTURE & OPERATIONS Cycle Time December 2018
- 40. INFRASTRUCTURE & OPERATIONS Cycle Time January 2019 • Team is a whole functional team for the first time!
- 41. INFRASTRUCTURE & OPERATIONS Cycle Time February 2019 • Team started to gel
- 42. INFRASTRUCTURE & OPERATIONS Cycle Time March 2019 • Cycle time takes a hit due to unclear requirements resulting in rebuilding two environments • Two team members to deployed application teams for an experiment • Team of 3 decides not to adjust WIP limits
- 43. INFRASTRUCTURE & OPERATIONS Cycle Time April 2019 • Another members to deployed for an experiment • Team of 2 decides to keep current WIP limits
- 44. INFRASTRUCTURE & OPERATIONS Cycle Time April 2019 • Another members to deployed for an experiment • Team decides to keep current WIP limits with a two person team
- 45. INFRASTRUCTURE & OPERATIONS Cycle Time May 2019 • Team of 2 feels overwhelmed but keeps current WIP limits • Team member is hospitalized and will be out for 3 months • Time to form a new team :o