Scrum & Kanban Better Together? Some Scrum/Kanban Myths & What Professional Scrum+Kanban can look like

Size: px

Start display at page:

Download "Scrum & Kanban Better Together? Some Scrum/Kanban Myths & What Professional Scrum+Kanban can look like"

Randolf Andrews
6 years ago
Views:

1 Scrum & Kanban Better Together? Some Scrum/Kanban Myths & What Professional Scrum+Kanban can look like Dave West Product Owner & CEO Yuval Yeret Enterprise Lean/Agile Consultant/Trainer

2 2

3 We re privileged We can mix colors! 3

4 Survey 4

5 Scrum Strength: Optimized for value delivery; well defined Weakness: mini-waterfall 5

6 Kanban Strength: Optimized for flow Weakness: No rules; deferred value delivery 6

7 It s about being Professional Scrum Professional 7

8 So what is Professional Scrum? 8

9 9

10 So Why Kanban? We set out to help practitioners figure out how to do *Professional* Kanban within a *Professional* Scrum context 10

11 Kanban Core Practices This is what *Professional* Kanban looks like 1. Visualize 2. Limit Work-in-Progress 3. Actively Manage Items in Progress 4. Make Policies Explicit 5. Improve Collaboratively 11

12 1. Visualize + 2. Limit Work in Progress work items workflow how Work In Progress is limited Visualization of a Service Level Expectation (SLE) Visualization of process policies 12

Cycle Time: The elapsed time between when works starts and when work finishes.

13 3. Actively Manage Items in Progress - Required Metrics To actively manage work in progress you must track when work begins and when work begins and when work is done. Cycle Time: The elapsed time between when works starts and when work finishes. Work item age: The time between when works starts and the current time. Throughput: The total number of items of items finished per unit of time. 13

14 4. Make Policies Explicit Explicit policies ensure process transparency and enable inspection and adaptation 14

15 5. Improve Collaboratively 15

16 Myth / Truth? Where are the PEOPLE in Kanban? 16

17 kanban doesn't encourage creating effective teams 17

18 kanban is all about manufacturing, software isn't manufacturing 18

19 Isn t Scrum just Kanban with a bigger batch size? 19

20 Scrum is for Kanban is for kanban is all about manufacturing, software isn't manufacturing 20

21 Our Scrum team has evolved to become a Kanban team. 21

22 We do Kanban because we can't plan out for an entire Sprint. 22

23 Scrum is revolutionary; Kanban is evolutionary. Kanban always starts with what you got 23

24 kanban always starts with what you got 24

25 Kanban accepts and reinforces command and control / waterfall mindset 25

26 Where are the PEOPLE in Kanban? 26

27 Myth / Truth? Where are the PEOPLE in Kanban? 27

28 Changes you can try in your Scrum teams 28

29 Use a Kanban Board as your Sprint Backlog 29

30 Make more of your process Transparent by making more policies explicit Asdcasdc Asdcasdca sdcasdca Asdcasdc Asdcasdca sdcasdca Asdca sdc Asdca sdca sdcasd ca THE Definition of Done: Asdcasdc Asdcasdca sdcasdca 30

31 Work Item Age / Fighting Zombies 31

32 The Banana Peel Technique 32

33 Flow-based Sprint Planning Leverage the Sprint Goal You don t need to plan out the entire Sprint You can begin unplanned work part way through the Sprint Work can flow across Sprint boundaries 33

34 Flow-based Sprint Planning Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less. The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint. The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal. The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives. As the Development Team works, it keeps the Sprint Goal in mind. In order to satisfy the Sprint Goal, it implements the functionality and technology. If the work turns out to be different than the Development Team expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint. 34

35 Flow-based Sprint Planning 35

36 Flow-based Daily Scrums Flow/Pull/Hebrew-mode Work the Kanban board right to left Focus on stories rather than going person by person What work is blocked? What work is about to violate our SLE? What work are we not visualizing? Where s the bottleneck? 36

37 Flow-based Sprint Reviews What is our current throughput? How does this impact items in our Product Backlog? Has our SLE changed? What is our lead time? 37

38 Flow-based Retrospectives Stop Is our cycle time decreasing? Did we meet our SLAs? Keep Start Ad Hoc (SLA violation) Less More 38

39 Helping more Scrum teams be Professional using Kanban, Helping Kanban teams be more Professional Scrum scrum.org/resources/blog/kanban-primer-scrum-teams scrum.org/resources/blog/scrum-and-kanban-strongertogether scrum.org/resources/blog/scrum-primer-kanban-teams agilesparks.com/solutions/kanban/ Professional Professional Kanban Professional Kanban Guide WIP Scrum.Org Professional Kanban for Scrum Teams - TBA 39

40 Thank You 40

41 Connect with the Scrum.org & AgileSparks community Forums Scrum.org /Community LinkedIn LinkedIn.com /company/scrum.org Facebook Facebook.com /Scrum.org RSS Scrum.org/RSS Blog Insights from AgileSparks s team of Agile Coaches/Consultants 41

This Thing Called Kanban

This Thing Called Kanban A presentation for Agile Richmond Slide 1 Announcing Innovate Virginia! Accelerate Delivery with Lean and Agile! Friday Sept 16, 2011 Lewis Ginter Botanical Gardens Leading experts