making scrum more powerful with some kanban

Post on 21-Jan-2018

157 Views

Category:

Business

1 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Making Scrum more powerful with some Kanban

Kirill Klimov

Cargo cult

V1 11th State of Agile Report

VERSIONONE.COM 10#StateOfAgile

AGILE METHODS AND PRACTICES

AgileMethodologies UsedScrum and Scrum/XP Hybrid (68%) continue to be the most common agile methodologies used by respondents’ organizations.

58%Scrum

10%Scrum/XP

Hybrid

8%Custom Hybrid

(multiple methodologies)

8%Scrumban

5%Kanban

2% I Don’t Know<1% Agile Unified Process (AgileUP)

<1% XP<1% DSDM/Atern <1% Feature-Driven Development (FDD)

<1% Lean Startup 1% Lean Development

2% Iterative Development 5% Other

Agile Techniques EmployedFrom 2015 to 2016, the use of Kanban grew from 39% to 50%; iteration reviews

increased from 54% to 81% and iteration planning went from 69% to 90%.

TOP 5 AGILETECHNIQUES

88%

81% 71%

83%DAILY

STANDUP

ITERATIONREVIEWS

SHORTITERATIONS

RETROSPECTIVES

} Iteration planning

Daily standup

Retrospectives

Iteration reviews

Short iterations

Release planning

Team-based estimation

Dedicated product owner

Single team (integrated dev & testing)

Frequent releases

Kanban

Open work area

Product roadmapping

Story mapping

Agile portfolio planning

Agile/lean UX

90%

88%

83%

81%

71%

66%

62%

55%

54%

50%

50%

45%

38%

35%

25%

22%

*Respondents were able to make multiple selections.

90%ITERATION PLANNING

Scaling

VERSIONONE.COM 14#StateOfAgile

SCALING AGILE

Scaling Methodsand ApproachesSAFe (28%) has overtaken SCRUM/SCRUM of SCRUMS (27%) to be the most popular scaling method cited by respondents.

Top 5 Tips for Success with Scaling AgileExecutive sponsorship (48%), consistent process and practices (41%), implementation of a common tool across

teams (36%), and agile consultants or trainers (36%) continue to be cited in the top five tips for successfully scaling agile for the past few years and likely points to the long-term importance of self-sufficiency when scaling agility. The

top cited tip this year, internal agile coaches (52%), was a new entry into the top five.

Other important factors included: externally attended classes or workshops, company-provided training program, online training, and webinars.

*Respondents were able to make multiple selections.

NEXUS

RECIPES FOR AGILE GOVERNANCE IN THE ENTERPRISE (RAGE)

DISCIPLINED AGILE DELIVERY (DAD)

LARGE-SCALE SCRUM (LESS)

AGILE PORTFOLIO MANAGEMENT (APM)

LEAN MANAGEMENT

INTERNALLY CREATED METHODS

SCRUM / SCRUM OF SCRUMS

SCALED AGILE FRAMEWORK® (SAFE®) 28%

27%

13%

4%

1%

1%

1%

4%

3%

41%CONSISTENT

PROCESS AND PRACTICES

36%IMPLEMENTATION

OF A COMMON TOOL ACROSS TEAMS

36%AGILE CONSULTANTS

OR TRAINERS

48%EXECUTIVE

SPONSORSHIP

52%INTERNAL AGILE

COACHES

Silver Bullets

Magic Pills

Crossing the Chasm

Innovators

Early Adopters

Early Majority

Late Majority

Laggards

Learning and growth

Exercise

➤ Form groups of 2-3 people

➤ Within your group, one by one share and discuss following:

➤ quickly introduce yourself (name, company, what company is doing, what you are doing within the company) ;-)

➤ what was 1 thing that you either learned today or something that stroke you today? Something that made most of the impact on you today. Discuss within your group.

➤ 2 mins for each of you

How to apply these ideas in your context?

Little’s Law

t

N

. .. .... ..

Th Th= Nt

DeliveryRate= WIPLeadTime

Scaling

Limit WIP: classic

Ready Analysis DevCustomer Acceptance Done

5 3 4 5

Limit WIP: Stories and tasks

UserStories Tasks In Progress Done

4

Limit WIP per lane

5 3 4 5

5

6

Flow

1Fl

ow 2

Ready Analysis DevCustomer Acceptance Done

Min-max WIP for column

To plan In Progress Review3 3-10Backlog Release

UserStories

3-5 5-10

Discovery Kanban

8- 5 3Ideas Concepts Analysis ValidationOptions

5-

http://www.discovery-kanban.comPatrick Steyaert

Limit WIP per person

5 3 4 5

👤 👤 👤

Ready Analysis DevCustomer Acceptance Done

Personal kanban

Ideas ToDo In Progress Done25

Personal kanban with weekly planning

Ideas ToDo In Progress Done25Week

25

Making policies explicit

Ready Analysis DevCustomer Acceptance Done

5 3 4 5

DoD➤ ———— ➤ ———— ➤ ———— ➤ ————

DoD➤ ———— ➤ ———— ➤ ———— ➤ ———— ➤ ————

DoD➤ ———— ➤ ———— ➤ ———— ➤ ———— ➤ ———— ➤ ————

DoD

➤ ———— ➤ ————

Prio

rity

Retrospection process

➤ Tasks on board

➤ Retro board

Personal kanban

Problems & observations Options Possible experiments Committed Ongoing Review Next

… a powerful learning stream that I defined and captured on a parallel “Popcorn board”

Claudio"Perrone"

claudio@agilesensei.com"www.agilesensei.com"

@agilesensei"www.a3thinker.com"

Next is Now

https://popcornflow.comClaudio Perrone

Product Backlog

Explicit Refinement

Using class of service

Class of service for “product backlog”

ProductBacklog

Expedite

Fixed dateRegular

Intangible

Limiting length of backlogs

ProductBacklog

Expiration policy

Eliminating priority from backlog

Product Backlog

Daily stand-ups

5 3 4 5

👤 👤 👤

Ready Analysis DevCustomer Acceptance Done

Future is Uncertain

0 1 2 3 4

“Noonecanpredicttomorrowwithabsoluteconfidence.Butthemistakesomepeoplemakeistryingtoavoidmakinganypredictionsbecausetheirthirstforcertaintyissostrongandtheirfearofdoubttoooverwhelming.”

―CharlesDuhigg,SmarterFasterBetter

Make Uncertancy Explicit

🤦

# ➞

5

8 95%

50%

Future is Uncertain

➤ Not everything is “normal”

➤ Not all normal distributions are the same…

0

0.5

1

1.5

2

2.5

3

3.5

4

4.5

0 3 6 9 12 15 18 21 24 27 30 33 36 39 42 45 48 51 54 57 60 63 66 69 72 75 78 81 84 87 90 93 96 99

NormalDistribution, μ=50,σ=20

0

0.5

1

1.5

2

2.5

0 3 6 9 12 15 18 21 24 27 30 33 36 39 42 45 48 51 54 57 60 63 66 69 72 75 78 81 84 87 90 93 96 99

NormalDistribution, μ=50,σ=2

0

5

10

15

20

25

0 3 6 9 12 15 18 21 24 27 30 33 36 39 42 45 48 51 54 57 60 63 66 69 72 75 78 81 84 87 90 93 96 99

NormalDistribution, μ=50,σ=2 0

ExampleVe

locity

0

5

10

15

20

25

30

35

40

Timeline

Sprint1 Sprint2 Sprint3

201822

20202020 20 20

Velocity

0

5

10

15

20

25

30

35

40

Timeline

Sprint1 Sprint2 Sprint3

20

10

30

20202020 20 20

200storypoints 7sprints 200storypoints 6-9sprints

6⇒10%

7⇒50%

9⇒90%

modemedianmean

Leadtime distribution

probabilistic forecasting

26

57

77

105

125 132150

163181

189

216229

152 152169

189 189199 205 209

225 229

251

272

0

50

100

150

200

250

300

350

400

ReleaseBurn-Up

Burnup

Scope

Nextphase

85%certainty

75%certainty

50%certainty

ScopeTrendline

Frank Vega and Jesper Boeg

Quick Recap of ideas

➤ Limit WIP:

➤ per column

➤ Stories and tasks

➤ Per lane

➤ Min-max WIP for column

➤ Discovery Kanban

➤ Limit WIP per person

➤ Personal Kanban

➤ with weekly planning

➤ Making policies explicit

➤ DoD

➤ Priority

➤ Retrospection process

➤ Popcorn flow

➤ “Product Backlog” hints:

➤ Refinement states

➤ Class of service

➤ Limiting length of backlogs

➤ Eliminating priority from backlog

➤ Daily stand-up

➤ Probabilistic forecasting

“You say you want a revolution Well, you know We all want to change the world You tell me that it's evolution Well, you know We all want to change the world“

Thank you!

Kirill Klimov

+65 8315 9176

kklimov@palo-it.com

f0g

f0g

kirillklimov

QUESTIONS ?

top related