Launching Kanban Teams GOTO Cph 2012 - GOTO Conference · PDF file 2012-05-21 ·...

Click here to load reader

  • date post

    25-May-2020
  • Category

    Documents

  • view

    4
  • download

    0

Embed Size (px)

Transcript of Launching Kanban Teams GOTO Cph 2012 - GOTO Conference · PDF file 2012-05-21 ·...

  • 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 to Consider � Common Problems � (Board Designs) � Q&A

    3

  • What I Won’t Cover

    � Kanban’s Origins � Kanban principles � Scrum vs. Kanban

    4

  • 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

  • Accredited Kanban Training

    6

  • 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

  • ONE MINUTE KANBAN REMINDER

    8

  • 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

  • Kanban Principles

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

    10

  • THE CHALLENGE

    11

  • 17 Teams, 3 Organizations

    12

  • WITH VERY DIFFERENT REASONS FOR IMPLEMENTING KANBAN

    13

  • Context Based Agile

    � Also outside the development context

    14

  • Flexible Scheduling

    15

  • Predictability

    16

  • Suboptimization

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

    17

  • Truck Factor

    18

  • Organizational Resistance

    19

  • Continuous Improvement

    20

  • Structure/Maturity

    21

  • Next Step - Agile

    22

  • A Mix

    23

  • Usual Strategy

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

    24

  • Budget and Time Constraints

    � 1 ½ - 2 days per team (Roughly)

    25

  • Strategy Used

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

    26

  • Training

    � 2 day Accredited Kanban Training for “Drivers/Champions/Change Agents”

    � 1 day Introduction for “participants”

    27

  • Kickstart Content

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

    28

  • Off-Site Coaching

    � Problems, Successes, Clarification, Inspiration/Experiments

    29

  • Before the Review

    � Perceived Benefit of Kanban (Positive, Neutral, Negative)

    � Metrics � Questions/Problems� Questions/Problems

    30

  • At the Review (1/2 – 1 day)

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

    31

  • WHAT WORKED?

    32

  • Cut the Cord

    33

  • A ”Driver ” Really Helps

    34

  • Collaborative System Design

    35

  • Revolutionary and Evolutionary

    36

  • Owning the Process

    37

  • Value Perspective

    38

  • Changing the Team Perspective

    39

  • Physical Boards

    40

  • Distributed Projects

    41

  • Deeper Understanding of Agile

    42

  • Perceived Effect

    43

  • WHAT FAILED?

    44

  • Ideas vs. Rules

    Why are we not allowed to estimate?

    45

  • Management Focus

    � Last Minute Cancellations

    46

  • USING AND UPDATING METRICS

    47

  • Status?

    48

  • Status?

    49

  • Status?

    50

  • 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

  • Off-Site Coaching

    52

  • 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

  • THINGS TO CONSIDER

    54

  • Predictability

    55

  • Start Gathering Data

    � But don’t expect people to use them right away

    56

  • Copy Cats

    57

  • People Need Help

    � To stop focusing on mechanics

    58

  • Change Management is Hard

    59

  • COMMON PROBLEMS

    60

  • Management Wants It

    � - But does not live it

    61

  • Partly Visualized System

    62

  • Standup Duration

    63

  • Difference in Item Type/Size

    64

  • BOARD DESIGNS

    65

  • 66

  • 67

  • 68

  • 69

  • 70

  • 71

  • 72

  • 73

  • 74

  • 75

  • QUESTIONS

    76

  • How To Reach Me

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

    77