lean meets it: how kata can helpkatasummit.com/wp-content/uploads/2017/02/kata... · 4.a tale of...

Post on 17-May-2020

2 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

2/6/2017

1

Lean Meets IT:

How Kata Can Help

February 22, 2017

Adam Light

Consultant & Principal, SocioTech

The world runs on software…

…YOU can use KATA to make software better!

2/6/2017

2

Challenge Vision Next

Target Condition

Current Condition Obstacles

1. Why Lean for software is different

2. How you can translate

3. What to look for

4. A tale of three Katas

5. Igniting the fire in IT

2/6/2017

3

5

Software development is a design activity.

Work items are intangible.

Scope and scale are highly variable.

2/6/2017

4

Value = fitness for use.

Software development has come a long way!

2/6/2017

5

Scrum / Agile

Speak The Same Language

Lean Agile Batches User Stories, Releases, Sprints

WIP control Sprint length

Value Working software

Work Cells Stable, cross-functional teams

Just in Time Continuous delivery (customer pull)

Respect for People Respect for People

2/6/2017

6

Know What to Expect

• Agile “by the book”

• Managing people, not processes

• Measuring feature velocity

• “Water-scrum-fall”

Kata #1 Team C

Team A

Team B

Features

Features

SupportIssues

2/6/2017

7

Kata #1

Current Condition

Target Condition

?

?

? ?

?

Process?

2/6/2017

8

Water

Scrum

Fall

Kata #2

Kata #2

Conduct Experiments to get there Grasp the

Current Condition

Establish your Next

Target Condition

Get the Direction or Challenge

1

2

3

4

2/6/2017

9

Cycle Time

Seeing the Value Stream

Starbucks 1: Cash Registers

Kata #3

2/6/2017

10

Novice

Basic

Intermediate

Learning Spiral

© 2015 Iberle Consu lting Group, Inc.

Organization

Learner

Value-

Stream

Learner

Process-

Level

Learner

Success Cards for

Each Process

Learner: Coach:

Target Condition: Size of Zebra

System Test Queue is 50% of

current size.

Results: We learned that

some stories can be tested

concurrently on the same

test bed without interfering

with each other,

so we changed our process

for letting stories into

System Test to allow stories

to enter concurrently with

prior approval from Dev.

Elapsed time for the PDCA

cycles: ~10 days

Benefit: Some stories move

into System Test without

waiting as long, reducing

average cycle time for an

update. Average # stories in

System Test Queue dropped

by 25%.

Make Success Visible!

2/6/2017

11

Challenge Vision Next

Target Condition

Current Condition Obstacles

• Recognize the Lean inside Agile

• Tap data using (Lean) tools you know

• Help the value stream emerge

• Spiral up

• Make success visible!

Lean + Agile Lean startup… Scrum… Kanban… Continuous delivery… Design thinking… DevOps… Lean Product Development…

2/6/2017

12

23

Recognize the Lean in Agile

Make processes visible

Celebrate simple successes

Prepare to learn from your pupils!

Lean Meets IT: How Kata Can Help

24

Adam Light Consultant & Principal

SocioTech

adam@sociotechadvisors.com

503.522.1499

top related