Under Pressure - Speaker Deck

Slide 1

Slide 1 text

Under Pressure Resisting the urge to GO FASTER

Slide 2

Slide 2 text

My name is Todd Kaufman Tweet away @toddkaufman Say [email protected]

Slide 3

Slide 3 text

Disclaimer: The stories you are about to hear are strictly HYPOTHETICAL

Slide 4

Slide 4 text

The Team

Slide 5

Slide 5 text

The Team

Slide 6

Slide 6 text

The Team

Slide 7

Slide 7 text

Iterations Points Remaining

Slide 8

Slide 8 text

Iterations Points Remaining

Slide 9

Slide 9 text

Iterations Points Remaining

Slide 10

Slide 10 text

Iterations Points Remaining

Slide 11

Slide 11 text

“We need to add more people!”

Slide 12

Slide 12 text

“Let’s work weekends until we’re back on track!”

Slide 13

Slide 13 text

“I’ll just skip tests for this feature and come back to do them later”

Slide 14

Slide 14 text

Will we SPEED UP?

Slide 15

Slide 15 text

Faster 10% Slower 90% Results

Slide 16

Slide 16 text

and the cycle continues…

Slide 17

Slide 17 text

How do we react to PRESSURE

Slide 18

Slide 18 text

How can we avoid PRESSURE

Slide 19

Slide 19 text

More People

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

Does adding developers resources to a project, that is already late, speed it up?

Slide 22

Slide 22 text

Nope

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

Why is this?

Slide 25

Slide 25 text

1. Ramp up 2. Communication 3. Separation of work 4. Integration 5. Dysfunction

Slide 26

Slide 26 text

“Adding manpower to a late software project makes it later.” Brook’s Law

Slide 27

Slide 27 text

“Adding people to a dysfunctional software environment makes it even more inept.” Todd’s Law

Slide 28

Slide 28 text

Instead

Slide 29

Slide 29 text

Fix existing issues

Slide 30

Slide 30 text

No content

Slide 31

Slide 31 text

No content

Slide 32

Slide 32 text

No content

Slide 33

Slide 33 text

Remove negativity and waste

Slide 34

Slide 34 text

More Commitment

Slide 35

Slide 35 text

PMs like per sprint estimation

Slide 36

Slide 36 text

Predictable outcomes

Slide 37

Slide 37 text

Time 1x .25x 4x Cone of uncertainty

Slide 38

Slide 38 text

Realistic cone of uncertainty

Slide 39

Slide 39 text

Time 1x .25x 8x

Slide 40

Slide 40 text

“When will we be done?”

Slide 41

Slide 41 text

“We don’t know”

Slide 42

Slide 42 text

One cannot simply change an estimate to a commitment

Slide 43

Slide 43 text

#noestimates

Slide 44

Slide 44 text

3 possible outcomes

Slide 45

Slide 45 text

1. Nailed it!

Slide 46

Slide 46 text

2. Early

Slide 47

Slide 47 text

3. Late

Slide 48

Slide 48 text

How does that affect the next estimation session?

Slide 49

Slide 49 text

No content

Slide 50

Slide 50 text

Instead

Slide 51

Slide 51 text

#noestimates

Slide 52

Slide 52 text

Cycle Time

Slide 53

Slide 53 text

Quick Sizing

Slide 54

Slide 54 text

More Stress

Slide 55

Slide 55 text

Does applying pressure work?

Slide 56

Slide 56 text

Stress Performance Fatigue Exhaustion ILL - Health Breakdown Comfort Zone

Slide 57

Slide 57 text

What about creativity?

Slide 58

Slide 58 text

Creativity Under the Gun

Slide 59

Slide 59 text

Mon Tues Wed Thur Fri Creativity

Slide 60

Slide 60 text

Mon Tues Wed Thur Fri Creativity

Slide 61

Slide 61 text

Mon Tues Wed Thur Fri Creativity Planning Meeting

Slide 62

Slide 62 text

Mon Tues Wed Thur Fri Creativity Planning Meeting

Slide 63

Slide 63 text

Mon Tues Wed Thur Fri Creativity Planning Meeting

Slide 64

Slide 64 text

Are developers lazy?

Slide 65

Slide 65 text

not when properly motivated

Slide 66

Slide 66 text

No content

Slide 67

Slide 67 text

But we aren’t saving lives…

Slide 68

Slide 68 text

Focus less on stress

Slide 69

Slide 69 text

Instead

Slide 70

Slide 70 text

Focus more on Why

Slide 71

Slide 71 text

Cut Corners

Slide 72

Slide 72 text

Do we reduce QUALITY in order to speed up?

Slide 73

Slide 73 text

What is quality?

Slide 74

Slide 74 text

“low Cyclomatic Complexity”

Slide 75

Slide 75 text

“SOLID”

Slide 76

Slide 76 text

“High Test Coverage!”

Slide 77

Slide 77 text

Quality How easily and safely we can change a codebase

Slide 78

Slide 78 text

Do we reduce QUALITY in order to speed up?

Slide 79

Slide 79 text

Less Tests

Slide 80

Slide 80 text

Less Refactoring

Slide 81

Slide 81 text

More Complexity

Slide 82

Slide 82 text

Less Comprehension

Slide 83

Slide 83 text

More Defects

Slide 84

Slide 84 text

More Rework

Slide 85

Slide 85 text

Less Quality

Slide 86

Slide 86 text

Less Speed

Slide 87

Slide 87 text

Instead

Slide 88

Slide 88 text

Resist!

Slide 89

Slide 89 text

Make Debt Visible

Slide 90

Slide 90 text

Pair More

Slide 91

Slide 91 text

Estimation

Slide 92

Slide 92 text

#noestimates

Slide 93

Slide 93 text

Are there cases where we should estimate?

Slide 94

Slide 94 text

“Is there a ROI?”

Slide 95

Slide 95 text

$150k

Slide 96

Slide 96 text

$150k $780k

Slide 97

Slide 97 text

Left with only this data…

Slide 98

Slide 98 text

We need estimation

Slide 99

Slide 99 text

We need to get better at estimation

Slide 100

Slide 100 text

Why is ESTIMATION so difficult?

Slide 101

Slide 101 text

1. Optimism Bias

Slide 102

Slide 102 text

Other 5% Programming 95% Workday as we estimate it

Slide 103

Slide 103 text

Other 10% Cukes 15% Meetings 25% Work 50% Workday as we live it

Slide 104

Slide 104 text

2. No two things are alike

Slide 105

Slide 105 text

3. Requirements suck

Slide 106

Slide 106 text

“The ability to report on data”

Slide 107

Slide 107 text

Instead

Slide 108

Slide 108 text

Team Level Cycle Time

Slide 109

Slide 109 text

Resist Change

Slide 110

Slide 110 text

Leverage Spikes

Slide 111

Slide 111 text

Adjust Fidelity

Slide 112

Slide 112 text

Is it just a Lack of trust?

Slide 113

Slide 113 text

Yes

Slide 114

Slide 114 text

Have we earned it?

Slide 115

Slide 115 text

Slide 116

Slide 116 text

Discipline and Accountability

Slide 117

Slide 117 text

Objectives Constraints Fidelity

Slide 118

Slide 118 text

Communication Impediments Organization

Slide 119

Slide 119 text

Estimation Quality Resistance

Slide 120

Slide 120 text

Predictable over Quick

Slide 121

Slide 121 text

Thank you!

Slide 122

Slide 122 text

References: https://www.amazon.com/Exit-Voice-Loyalty-Responses-Organizations/dp/0674276604 https://www.amazon.com/Mythical-Man-Month-Software-Engineering-Anniversary/dp/ 0201835959 http://dilbert.com/strip/2010-04-29 https://hbr.org/2015/04/why-some-men-pretend-to-work-80-hour-weeks https://hbr.org/2002/08/creativity-under-the-gun http://www.construx.com/Resources/White_Papers/Managing_Technical_Debt/ Icons: Dice by Hopkins from the Noun Project Clamp by Tomas Knopp from the Noun Project Quality badge by Gregor Cresnar from the Noun Project Communication by Oksana Latysheva from the Noun Project options by Bernar Novalyi from the Noun Project Unicorn by Lele Saa from the Noun Project Tshirt by Edward Boatman from the Noun Project Lock by Aleksandr Vector from the Noun Project

Slide 123

Slide 123 text

No content