Tweet
Tweet

Slide 1

Slide 1 text

1 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 2

Slide 2 text

Waste in Software Development 2 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 3

Slide 3 text

What is Waste? Waste is any material or activity that does not create value for the customer. 3 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 4

Slide 4 text

The Lean Model of Software Development 4 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 5

Slide 5 text

5 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 6

Slide 6 text

6 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 7

Slide 7 text

Activities · Build · Learn · Measure 7 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 8

Slide 8 text

Assets · Code · Ideas · Data 8 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 9

Slide 9 text

Code Waste · Code that is deleted before it creates value for the customer · Code for features the customer does not value · Code for features the customer cannot use 9 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 10

Slide 10 text

Ideas Waste · Ideas that are discarded before being turned into potential features · Potential features we do not turn into code · Ideas we cannot turn into code 10 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 11

Slide 11 text

Data Waste · Data that is insufficient for creating ideas · Data we do not turn into ideas · Data we cannot turn into ideas 11 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 12

Slide 12 text

Our simplified model of waste That which is: · Incomplete, or; · Unvalued, or; · Unused. 12 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 13

Slide 13 text

13 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 14

Slide 14 text

Code Waste 14 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 15

Slide 15 text

Code that is Incomplete, Unvalued, or Unused by the customer. 15 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 16

Slide 16 text

Incomplete Code · Dead-ends · Epics · Work-in-Progress 16 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 17

Slide 17 text

Unvalued Code · Architecture · Tests 17 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 18

Slide 18 text

Unused Code · Misfeatures · Over-optimizations 18 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 19

Slide 19 text

19 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 20

Slide 20 text

Unfulfilled Potential 20 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 21

Slide 21 text

Unfulfilled Code Unfulfilled code is code that would have created customer value, had it been in the customer's hands earlier. But it wasn't. 21 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 22

Slide 22 text

Unfulfilled Ideas Unfulfilled ideas are ideas that would have become features creating customer value, had we employed it to create features sooner. But we didn't. 22 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 23

Slide 23 text

Unfulfilled Data Unfulfilled data is data that would have pointed us towards valuable ideas for creating customer value, had we considered it earlier than we did. But we didn't. 23 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 24

Slide 24 text

24 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 25

Slide 25 text

Unfulfillment is Waste 25 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 26

Slide 26 text

Almost There… 26 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 27

Slide 27 text

27 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 28

Slide 28 text

Waste (again) Waste is: · Incomplete, or; · Unvalued, or; · Unused. 28 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 29

Slide 29 text

Code Waste (again) Incomplete code, such as dead-ends, epics, and work-in-progress. Unvalued code, such as architecture and tests. Unused code, such as misfeatures and over- optimizations. Unfulfilled code, such as features that are ready, 29 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 30

Slide 30 text

Five Easy Pieces 30 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 31

Slide 31 text

Question One Is technical debt waste? 31 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 32

Slide 32 text

Question Two Do big releases create waste? 32 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 33

Slide 33 text

Question Three Is tooling actually waste? 33 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 34

Slide 34 text

Question Four What does this model tell us about continuous integration and deployment? 34 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 35

Slide 35 text

Question Five What does this model tell us about big design up- front? 35 — © 2017 Reginald Braithwaite and PagerDuty, Inc.

Slide 36

Slide 36 text

Bonus Question Are technical talks waste? 36 — © 2017 Reginald Braithwaite and PagerDuty, Inc.