Kanban vs. Scrum. a comparison

Transcription

1 Kanban vs. Scrum a comparison

2 Which method is best, Kanban or Scrum? 2

3 Kanban vs. Scrum Kanban A change management method, start from today and evolve stepwise Create flow and optimize lead-time Scrum A framework in which you should employ and develop good practices Time-boxed: Plan and define scope Develop and Deliver within the time-box 3

4 Kanban and Scrum, a comparison Both embrace the Agile principles Kanban: also embrace Lean Both are empirical and adaptive processes Adapt by providing transparency and inspections Management and decisions are based on visualization and feedback Both are incremental development processes Build a product stepwise, by incremental development Kanban: Main focus is to create flow, but cadences can be added if it serves the process Scrum: Prescribes time-boxed iterations (Sprints) 4

5 Kanban and Scrum, a comparison Both are based on pull mechanisms Kanban: On demand when WIP limits and policies allow Scrum: Per Sprint to create a Sprint Backlog Both balance workload and capacity Kanban: By pull (above) and by WIP limits on the number of work items in activities and buffers Scrum: The amount of work is limited per Sprint by team capacity Both address process improvements Kanban: Reflect, gather data, analyze and improve the workflow, step by step Scrum: Retrospectives where different aspects of the process and/or team work can be addressed 5

6 Kanban and Scrum, a comparison Kanban is more open Kanban: Does not prescribe any particular sessions or roles Start with today s process, stimulate improvements and evolve (can be seen as a change management process) Scrum: Pre-defines sessions, artifacts and roles Visualization, the board Kanban: A Kanban board can belong to a team or be shared between many teams and resources. The board lives and evolves as long there is work in the process. Scrum: Each Development Team has their own Scrum Board. The board is cleared and re-arranged every Sprint. 6

7 Kanban and Scrum, a comparison The workflow Kanban: Map out Activities and Buffers that reflect how your process work today, and evolve! Can make use of Swim-lanes, Shared Services, etc. Can state various types of process policies Scrum: Typically, Planned Ongoing Done Backlog Items (Stories) are usually broken down into s Definition of Done (DoD) and Definition of Ready (DoR) 7

8 Kanban and Scrum, a comparison Preparing Work Items Kanban: Organize work items into stereotypes (Work Item Types), Classes of Services May state policies for preparing Work Items Scrum: Refine (groom) the Product Backlog: Set estimates on Backlog Items, and if needed break down bigger items to smaller, if needed re-arrange the Backlog Items, check that items are Ready to be pulled into a Sprint. Main metrics Kanban: WIP and lead-time/cycle-time Scrum: Team estimates on Backlog Items and Team Velocity/Capacity 8

9 Time-boxing vs. WIP limits Pull a batch of Work Items from the Product Backlog Sprint Backlog pull Scrum increase Amount of work (improve Velocity) Sprint length (fixed) Pull Work Items on demand when WIP limits and polices allow pull Kanban Amount of work is fixed (WIP Limits) shorten Lead-time (and improve Throughput) 9

10 Adopt Scrum roles into Kanban Development Team Cross-functional and self-organizing team Kanban coach/facilitator Product Owner Complement the board with a business view Upstream workflow for Backlog Management State business policies (e.g. how to prioritize and prepare work) 10

11 Adopt Scrum events into Kanban Refining (grooming) upcoming Work Items (next to pull) Upstream Business perspective Can be triggered by WIP Limits or by a Cadence Coordination meetings (Stand-ups) Manage flow, coordinate work and deal with impediments Triggered by a Cadence (each day, twice a week, ) Review/Demo Feedback, validation and acceptance from Customer/User Can be triggered by WIP Limits or by a Cadence Retrospectives to improve the workflow Triggered by a Cadence 11

12 Scaling Agile Can use Kanban to map out and visualize an enterprise workflow, end-to-end perspective Compare to a Agile Release Train in SAFe A subset of the enterprise Kanban workflow can be mapped to, and managed by a Scrum Team 12

13 Plannable vs. Unplannable work A Development Team in Scrum can add a Kanban workflow for unplanned work as a part of their capacity Capacity for Unplannable work (flow) Next Ongoing Done Defects (high prio) Defect Defect Defect Capacity for Plannable work, pulled from the Product Backlog (Sprints) Other stuff 13

14 Plannable vs. Unplannable work X = % unplannable work (prediction) Buffer for plannable Items (from Product Backlog) a Burn-down Buffer for unplannable Items (bug-fixes, maintenance, support, etc.) b Burn-up? 14

15 Stagger planning over a Sprint to create flow Prio A [8 sp] start B [13 sp]? next, plan more soon C [8 sp]? wait, plan later 15

16 Adopt WIP Limits into Scrum Proto Kanban thinking Set WIP limit on how many s a person can work on, <n> s per person Can make use tokens/avatars Kanban and WIP Limits within a Sprint Set WIP limits on the number of Sprint Items In Progress Only work with <n> Sprint Items/Stories at the time 16

17 Kanban within a Sprint, example Fill up at Sprint planning (cadence) Sprint Backlog Planned In Progress [2] Development Waiting for UAT UAT Released (Done) Development policy UAT policy Released policy 17

18 Up-stream Kanban for Backlog Management New Next to Refine [~6] Refine [~4] Ready for Development [~4] In Progress (~ 2-4) Done Prioritization policy Ready for Dev. policy Done (DoD) policy 18

19