2013 04 10 (2008) Scrum Australia Keynote -...

Preview:

Citation preview

1 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Economically Sensible Scrum Scrum Australia Keynote

April 10, 2013 by Kenny Rubin

2 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Background of Kenny Rubin

Author Trainer/Coach Trained more than 19,000 people in Agile/Scrum, SW dev and PM Provide Agile/Scrum coaching to developers and executives

Experience

My first Scrum project was in 2000 for bioinformatics

Former Managing Director

Executive

3 Copyright © 2013, Innolution, LLC. All Rights Reserved.

4

Scrum Framework

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Art available at: http://www.innolution.com/resources

5 Copyright © 2013, Innolution, LLC. All Rights Reserved.

6

Approaches

Copyright © 2013, Innolution, LLC. All Rights Reserved.

7

ScrumBut(t) – Violations of the Scrum Framework

Copyright © 2013, Innolution, LLC. All Rights Reserved.

We do Scrum, but…

Sprints are 8 weeks

No product owner

Daily scrums on M-W-F

Sprint planning is 2 days

Etc…

8

What If We Had No Scrum Violations?

Copyright © 2013, Innolution, LLC. All Rights Reserved.

VIOLATION YOUR USE OF SCRUM VIOLATES A CORE PRACTICE AND IS HEREBY

DEEMED TO BE A SCRUMBUT

YOUR TEAM PHOTO HAS BEEN RECORDED

Do no violations = success with Scrum?

9

Current Industry Results – From Comparative Agility®

Copyright © 2013, Innolution, LLC. All Rights Reserved.

>7,000 Surveys at www.comparativeagility.com

10

VersionOne 7th Annual Survey

Copyright © 2013, Innolution, LLC. All Rights Reserved.

0%

20%

40%

60%

1% 1% 1% 2% 2% 2% 2% 4% 4% 7% 9% 11%

54%

Of 4,048 respondents, most are using Scrum or Scrum variants (72%)

11

Inhibitors to Success Using Scrum

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Ignorance or misapplication of core agile principles during development

Failure to apply agile principles throughout the value chain

Failure to structure teams in an economically sensible way

Overall, they don’t apply core agile principles in an economically sensible way

12

Principles

Copyright © 2013, Innolution, LLC. All Rights Reserved.

13

So What is Economically Sensible Scrum?

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Economic Framework Variability

& uncertainty

Prediction &

adaptation

Validated learning

Work in process (WIP)

Progress Performance

14

Economics – The Universal Language of Product Development

Copyright © 2013, Innolution, LLC. All Rights Reserved.

15

We Need a Economic Framework

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Waste

Lead time

Variability

Batch size

Customer sat

Lifecycle profits

Based on Reinertsen The Principles of Product Development Flow: Second Generation Lean Product Development

Compare effects of different product / process /organizational attributes by converting them all into the same unit of measure

16

Example: Waste

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Waste 1 Waste 2 Waste 3 Waste 4 Multiple forms

of waste

Waste 1 Waste 2 Waste 3 Waste 4 Can t eliminate

them all

Waste 1 Waste 2 Waste 3 Waste 4

$ $$$$ $$ $$$

Determine which cause most

economic damage

17

Example: Cost of Delay

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Lead time Variability

Money Lead time

If you have to wait 3 weeks for the UX team to design your UIs, and that delay could be eliminated by having a UX designer on your team, what would be the cost of the UX-team delay (in lifecycle profits)?

18 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Ignorance or Misapplication of

Core Agile Principles During

Development

19

Misunderstanding of When Change Occurs

Copyright © 2013, Innolution, LLC. All Rights Reserved.

We like Scrum, because we can make changes anytime we want!

Holly *?&! they can’t just change things whenever they want!

20

Economically Sensible Change

Copyright © 2013, Innolution, LLC. All Rights Reserved.

21

Misunderstanding of Just-in-Time

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Holly *?&! This sounds like total chaos!!!

With Scrum we do everything just-in-time!

22

Balance Up Front Predictive with Adaptive Just in Time

Copyright © 2013, Innolution, LLC. All Rights Reserved.

23

Recognize Inventory (WIP) Waste

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Manufacturing inventory is both physically and

financially visible

Product-development inventory are knowledge assets that

aren’t visible in the same way as physical parts

24

Focus on Idle Work Not Idle Workers

Watch the Baton Not the Runners

Copyright © 2013, Innolution, LLC. All Rights Reserved.

25

Economically Sensible Planning

Copyright © 2013, Innolution, LLC. All Rights Reserved.

26 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Failure to Apply Scrum Principles Throughout the

Value Chain

27

Example Value Chain

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Management

Finance HR Legal

Sales

Marketing

Develop Ops

Cust

Dev Partners Dev

Partners Dev

Partners

Cust

28

Do Agile Here

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Internal Management Misaligned

Develop in an Agile way, but still provide all of the same plan-driven artifacts (e.g., extensive up-front requirements, full budget, and precise schedule) like before to get the project approved

29

Sales Misaligned

Copyright © 2013, Innolution, LLC. All Rights Reserved.

30

Portfolio Planning Misaligned

Copyright © 2013, Innolution, LLC. All Rights Reserved.

31

Downstream Misaligned

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Develop Ops Backlog of potentially

shippable product increments

Cust

Ops

32

Partners Misaligned

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Fixed

Fixed Fixed

Contract

33

Protection of the Fiefdoms

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Sure, we can do Scrum, as long as I don’t have to change anything in my group!

George s Group

Me too! Me too! Me too! Me too!

34

Failure to See the Whole

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Optimizing locally frequently sub-optimizes the system

35 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Failure to Structure Teams

in an Economically Sensible Way

36

Economically Sensible Teaming

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Reduce multitasking

Scaling teams based on economics, not dogma

Embrace T-shaped Skills

Create and maintain long-lived teams

37

Reduce the Amount of Multi-tasking

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Not about keeping people busy

38 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Multitasking

Clark and Wheelwright (1992) studied multi-tasking and determined that when working on more than two projects, a person’s time spent on value-adding work drops rapidly

39

Teams with T-Shaped Skills

Copyright © 2013, Innolution, LLC. All Rights Reserved.

40

Team Longevity

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Product 1 PB 1 Feature Team A

Product 2 PB 2 Feature Team A

?

41

Economics Favor Long-lived Teams

Copyright © 2013, Innolution, LLC. All Rights Reserved.

More productive than newly formed groups

Team familiarity can positively impact efficiency and quality of team output

Has a shared velocity and estimating history that can be used during planning

Have established trust and team identity and integrity

42 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Projects with at least 100 people (320 surveys)

43

Scaling With Multiple Teams

Copyright © 2013, Innolution, LLC. All Rights Reserved.

As the scope of work gets larger and one team is no longer sufficient, what is your scaling strategy?

44

Discipline Teams

Copyright © 2013, Innolution, LLC. All Rights Reserved.

45

Location Teams

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Sydney New York

Sydney New York Deliberately Distributed

Teams Team 2

Team 1

Team 1 Team 2 Coordinating Collocated

Teams

46

Architectural Layer Teams

Copyright © 2013, Innolution, LLC. All Rights Reserved.

DB

Middle Tier

GUI

47

Component Teams

Copyright © 2013, Innolution, LLC. All Rights Reserved.

48

Feature Teams

Copyright © 2013, Innolution, LLC. All Rights Reserved.

49

Don t Scale Based on Dogma!

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Do you honestly think there is a single answer to scaling that universally applies to all situations (sizes and types of organizations)?

Everyone knows feature teams are better!

Nuts! Component teams promote

conceptual integrity & reuse!

50 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Component Teams (Single Source)

51 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Component Teams (Multiple Sources)

52 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Combined Feature & Component Teams

53

Summary

Copyright © 2013, Innolution, LLC. All Rights Reserved.

Performing all Scrum practices and using generally accepted Scrum approaches is necessary, but not sufficient

If you want to see the real benefits of applying Scrum you need to apply Scrum within an economic framework that allows you to make sensible tradeoffs

54 Copyright © 2013, Innolution, LLC. All Rights Reserved.

Contact Info for Kenny Rubin

Email: krubin@innolution.com Website: www.innolution.com Phone: (303) 827-3333 LinkedIn: www.linkedin.com/in/kennethrubin Twitter: www.twitter.com/krubinagile Essential Scrum: A Practical Guide to the Most Popular Agile Process

www.essentialscrum.com

Comparative Agility Website www.comparativeagility.com

Recommended