Launching Kanban Teams GOTO Cph. 2012 Jesper Boeg, Agile/Lean - - PowerPoint PPT Presentation

▶
launching kanban teams goto cph 2012
SMART_READER_LITE
LIVE PREVIEW

Launching Kanban Teams GOTO Cph. 2012 Jesper Boeg, Agile/Lean - - PowerPoint PPT Presentation

Aug 31, 2023 225 likes •1.02k views

Launching Kanban Teams GOTO Cph. 2012 Jesper Boeg, Agile/Lean Coach, VP Trifork Agile Excellence jbo@trifork.com Twitter: J_Boeg WHO AM I? 2 Agenda Introduction The Challenge What Worked What Failed What Failed Things

slide-1
SLIDE 1

Launching Kanban Teams GOTO Cph. 2012

Jesper Boeg, Agile/Lean Coach, VP Trifork Agile Excellence jbo@trifork.com Twitter: J_Boeg

slide-2
SLIDE 2

WHO AM I?

2

slide-3
SLIDE 3

Agenda

Introduction The Challenge What Worked What Failed What Failed Things to Consider Common Problems (Board Designs) Q&A

3

slide-4
SLIDE 4

What I Won’t Cover

Kanban’s Origins Kanban principles Scrum vs. Kanban

4

slide-5
SLIDE 5

Trifork A/S

Agile Coaching and Training

– Scrum, Kanban, XP….

Software development:

– Public, Mobile, Security and Finance – Public, Mobile, Security and Finance

Conferences

– GOTO and QCon

5

slide-6
SLIDE 6

Accredited Kanban Training

6

slide-7
SLIDE 7

Agile Training

Kanban Kickstart

– 1-2 day Kanban Training, Kickstart, Follow Up, Review

Scrum Kickstart Scrum Kickstart

– 1-2 day Scrum Training, Kickstart, Follow Up, Review

Organizational Health Checks

– Govenance, Portfolio, Program, Project, Team, Technical

7

slide-8
SLIDE 8

ONE MINUTE KANBAN REMINDER

8

slide-9
SLIDE 9

Core Values

Start with what you do now Agree to pursue incremental,

evolutionary change

Initially, respect current processes, roles, Initially, respect current processes, roles,

responsibilities and job titles

9

slide-10
SLIDE 10

Kanban Principles

Visualize the Work Limit Work-in-Progress Manage Flow Make Process Policies Explicit Make Process Policies Explicit Improve Collaboratively (using models)

10

slide-11
SLIDE 11

THE CHALLENGE

11

slide-12
SLIDE 12

17 Teams, 3 Organizations

12

slide-13
SLIDE 13

WITH VERY DIFFERENT REASONS FOR IMPLEMENTING KANBAN

13

slide-14
SLIDE 14

Context Based Agile

Also outside the development context

14

slide-15
SLIDE 15

Flexible Scheduling

15

slide-16
SLIDE 16

Predictability

16

slide-17
SLIDE 17

Suboptimization

– http://blog.crisp.se/2008/09/08/mattiasskarin/1220882915232

17

slide-18
SLIDE 18

Truck Factor

18

slide-19
SLIDE 19

Organizational Resistance

19

slide-20
SLIDE 20

Continuous Improvement

20

slide-21
SLIDE 21

Structure/Maturity

21

slide-22
SLIDE 22

Next Step - Agile

22

slide-23
SLIDE 23

A Mix

23

slide-24
SLIDE 24

Usual Strategy

Training Coaching More Coaching Even More Coaching Even More Coaching Review and Assesment Future Directions

24

slide-25
SLIDE 25

Budget and Time Constraints

1 ½ - 2 days per team (Roughly)

25

slide-26
SLIDE 26

Strategy Used

Training Kick Start Off-site Coaching (Email, Skype etc.) Review and Future Directions Review and Future Directions

26

slide-27
SLIDE 27

Training

2 day Accredited Kanban Training for

“Drivers/Champions/Change Agents”

1 day Introduction for “participants”

27

slide-28
SLIDE 28

Kickstart Content

Why? Boards and States WIP Limits Metrics Cadences Cadences Policies Roles and Responsibilities Card Content (Classes of Service) Commitments!

28

slide-29
SLIDE 29

Off-Site Coaching

Problems, Successes, Clarification,

Inspiration/Experiments

29

slide-30
SLIDE 30

Before the Review

Perceived Benefit of Kanban (Positive,

Neutral, Negative)

Metrics Questions/Problems Questions/Problems

30

slide-31
SLIDE 31

At the Review (1/2 – 1 day)

Comparing the why’s? System Design Retrospective Time Machine Time Machine Topics of the Day

31

slide-32
SLIDE 32

WHAT WORKED?

32

slide-33
SLIDE 33

Cut the Cord

33

slide-34
SLIDE 34

A ”Driver” Really Helps

34

slide-35
SLIDE 35

Collaborative System Design

35

slide-36
SLIDE 36

Revolutionary and Evolutionary

36

slide-37
SLIDE 37

Owning the Process

37

slide-38
SLIDE 38

Value Perspective

38

slide-39
SLIDE 39

Changing the Team Perspective

39

slide-40
SLIDE 40

Physical Boards

40

slide-41
SLIDE 41

Distributed Projects

41

slide-42
SLIDE 42

Deeper Understanding of Agile

42

slide-43
SLIDE 43

Perceived Effect

43

slide-44
SLIDE 44

WHAT FAILED?

44

slide-45
SLIDE 45

Ideas vs. Rules

Why are we not allowed to estimate?

45

slide-46
SLIDE 46

Management Focus

Last Minute Cancellations

46

slide-47
SLIDE 47

USING AND UPDATING METRICS

47

slide-48
SLIDE 48

Status?

48

slide-49
SLIDE 49

Status?

49

slide-50
SLIDE 50

Status?

50

slide-51
SLIDE 51

Evolutionary?

You are now a Team! But we have nothing in common Don’t worry. Start with Kanban and improve one step at a time

51

step at a time

slide-52
SLIDE 52

Off-Site Coaching

52

slide-53
SLIDE 53

No Perceived Need

“A crisis is a terrible thing to waste. It

should give people, institutions and politicians the necessary courage to implement change” implement change”

– Patrick Anderson

53

slide-54
SLIDE 54

THINGS TO CONSIDER

54

slide-55
SLIDE 55

Predictability

55

slide-56
SLIDE 56

Start Gathering Data

But don’t expect people to use them right

away

56

slide-57
SLIDE 57

Copy Cats

57

slide-58
SLIDE 58

People Need Help

To stop focusing on mechanics

58

slide-59
SLIDE 59

Change Management is Hard

59

slide-60
SLIDE 60

COMMON PROBLEMS

60

slide-61
SLIDE 61

Management Wants It

  • But does not live it

61

slide-62
SLIDE 62

Partly Visualized System

62

slide-63
SLIDE 63

Standup Duration

63

slide-64
SLIDE 64

Difference in Item Type/Size

64

slide-65
SLIDE 65

BOARD DESIGNS

65

slide-66
SLIDE 66

66

slide-67
SLIDE 67

67

slide-68
SLIDE 68

68

slide-69
SLIDE 69

69

slide-70
SLIDE 70

70

slide-71
SLIDE 71

71

slide-72
SLIDE 72

72

slide-73
SLIDE 73

73

slide-74
SLIDE 74

74

slide-75
SLIDE 75

75

slide-76
SLIDE 76

QUESTIONS

76

slide-77
SLIDE 77

How To Reach Me

Jesper Boeg

– Mail: jbo@trifork.com – Mobile: +45 51 54 28 20 – Twitter: J_Boeg – Twitter: J_Boeg

77