Tweet
Tweet

Slide 1

Slide 1 text

« Le vieux monde se meurt, le nouveau monde tarde à apparaître et dans ce clair-obscur surgissent les monstres » — Gramsci @lilobase

Slide 2

Slide 2 text

« Apparently, this SCRUM thing is so great, you need a person on every team dedicated to forcing the others to do it » @cgosimon

Slide 3

Slide 3 text

- "Business Agile": Built Upon Sand — R.Jeffries - The State of Agile Software in 2018 — M.Fowler - The Tragedy of Craftsmanship — Robert C. Martin - Developers Should Abandon Agile — R.Jeffries - The Failure of Agile — Andy Hunt - Time to Kill Agile — D.Thomas - The agile hangover — S.Mancuso

Slide 4

Slide 4 text

Agile 101 Let’s become Agile ! @lilobase

Slide 5

Slide 5 text

Before Agile 101 After Project manager

Slide 6

Slide 6 text

Before Agile 101 After Project manager Product Owner (Agile Project Manager)

Slide 7

Slide 7 text

Before Agile 101 After Project manager Product Owner (Agile Project Manager) Estimates in Man/Day

Slide 8

Slide 8 text

Before Agile 101 After Project manager Product Owner (Agile Project Manager) Estimates in Man/Day Estimates in Points

Slide 9

Slide 9 text

Before Agile 101 After Project manager Product Owner (Agile Project Manager) Estimates in Man/Day Estimates in Points Tracking progress

Slide 10

Slide 10 text

Before Agile 101 After Project manager Product Owner (Agile Project Manager) Estimates in Man/Day Estimates in Points Tracking progress Tracking progress (But it is a nice burn-down chart)

Slide 11

Slide 11 text

Before Agile 101 After Project manager Product Owner (Agile Project Manager) Estimates in Man/Day Estimates in Points Tracking progress Tracking progress (But it is a nice burn-down chart) Production releases every 6 months

Slide 12

Slide 12 text

Before Agile 101 After Project manager Product Owner (Agile Project Manager) Estimates in Man/Day Estimates in Points Tracking progress Tracking progress (But it is a nice burn-down chart) Production releases every 6 months Production release every 6 months (But we have 2 weeks sprints)

Slide 13

Slide 13 text

Agile 101 6 months after…

Slide 14

Slide 14 text

Agile 101 6 months after… How do we get better at

Slide 15

Slide 15 text

Agile 101 6 months after… Tracking velocity How do we get better at

Slide 16

Slide 16 text

Agile 101 6 months after… Tracking velocity Estimating our project How do we get better at

Slide 17

Slide 17 text

Agile 101 6 months after… Tracking velocity Estimating our project How do we get better at Refining the backlog

Slide 18

Slide 18 text

Agile 101 6 months after… Tracking velocity Estimating our project How do we get better at Refining the backlog Creating better burn- down charts

Slide 19

Slide 19 text

Agile 101 6 months after… Tracking velocity Estimating our project How do we get better at Refining the backlog Creating better burn- down charts How to sync story in Jira ?

Slide 20

Slide 20 text

More X to solve X

Slide 21

Slide 21 text

More X to solve X « We need to follow the SCRUM guide more strictly »

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

We find the Customer !!

Slide 26

Slide 26 text

Creating our burn- down charts Agile 101 6 months after… Tracking velocity Estimating our project How do we get better at Refining the backlog

Slide 27

Slide 27 text

Creating our burn- down charts Agile 101 6 months after… Tracking velocity Estimating our project How do we get better at Refining the backlog These are sym ptom s, not causes !

Slide 28

Slide 28 text

Product Management Software engineering Management Agile Command & Control

Slide 29

Slide 29 text

Product Management Software engineering Management Agile Command & Control Project Product

Slide 30

Slide 30 text

« Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, just done by brute force and thousands of slaves. » — Alan Kay

Slide 31

Slide 31 text

« Most software today is very much like an Egyptian pyramid with millions of bricks piled on top of each other, with no structural integrity, just done by brute force and thousands of slaves. » — Alan Kay We need to improve their commitment

Slide 32

Slide 32 text

Structural Integrity Stress

Slide 33

Slide 33 text

Structural Integrity Stress

Slide 34

Slide 34 text

Structural Integrity Stress

Slide 35

Slide 35 text

Pace of changes Agile development puts a lot of stresses on the system

Slide 36

Slide 36 text

Until it breaks Pace of changes

Slide 37

Slide 37 text

And the system is not only about the source code Stress

Slide 38

Slide 38 text

And the system is not only about the source code Stress people people

Slide 39

Slide 39 text

And the system is not only about the source code Stress people people And often their last defense has been taken away

Slide 40

Slide 40 text

You need very specific and hard to master software design foundation

Slide 41

Slide 41 text

You need very specific and hard to master software design foundation

Slide 42

Slide 42 text

You need very specific and hard to master software design foundation

Slide 43

Slide 43 text

You need very specific and hard to master software design foundation Refactoring

Slide 44

Slide 44 text

You need very specific and hard to master software design foundation Refactoring You’ll need TDD

Slide 45

Slide 45 text

You need very specific and hard to master software design foundation Refactoring You’ll need TDD

Slide 46

Slide 46 text

You need very specific and hard to master software design foundation Refactoring You’ll need TDD

Slide 47

Slide 47 text

You need very specific and hard to master software design foundation Refactoring You’ll need TDD

Slide 48

Slide 48 text

You need very specific and hard to master software design foundation Refactoring You’ll need TDD

Slide 49

Slide 49 text

You need very specific and hard to master software design foundation Refactoring You’ll need TDD

Slide 50

Slide 50 text

You need very specific and hard to master software design foundation Refactoring You’ll need TDD Decoupling

Slide 51

Slide 51 text

Technical Excellence enable Business Agility Not the other way around

Slide 52

Slide 52 text

« The conventional definition of management is getting work done through people, but real management is developing people through work. » — Agha Hasan Abedi

Slide 53

Slide 53 text

Management 101 Management 101 @lilobase

Slide 54

Slide 54 text

A = What is the cost to create X ? & B = How much did it cost to produce X ? A - B > 0 Management 101

Slide 55

Slide 55 text

A = What is the cost to create X ? & B = How much did it cost to produce X ? A - B > 0 The sacred Provisional budget Management 101

Slide 56

Slide 56 text

A = What is the cost to create X ? & B = How much did it cost to produce X ? A - B > 0 The sacred Provisional budget Management 101 The destroyer of illusions

Slide 57

Slide 57 text

A = What is the cost to create X ? & B = How much did it cost to produce X ? A - B > 0 The sacred Provisional budget Management 101 The destroyer of illusions The feared balance

Slide 58

Slide 58 text

Mesure it and repeat Management 101

Slide 59

Slide 59 text

A = What is the cost to create X ? & B = How much did it cost to produce X ? A - B > 0 Management 101

Slide 60

Slide 60 text

A = What is the cost to create X ? & B = How much did it cost to produce X ? A - B > 0 Management 101 But, does it create value for the company ?

Slide 61

Slide 61 text

A = What is the cost to create X ? & B = How much did it cost to produce X ? A - B > 0 Management 101 It’s a risk hedging strategy But, does it create value for the company ?

Slide 62

Slide 62 text

Management 101 Scope (cost)
 Resources Time The Iron Triangle Scope = Time x Resources

Slide 63

Slide 63 text

Scope (cost)
 Resources Time « Hofstadter's Law: It always takes longer than you expect, even when you take into account Hofstadter's Law » Management 101

Slide 64

Slide 64 text

A development task has only 3 states

Slide 65

Slide 65 text

A development task has only 3 states Not yet started

Slide 66

Slide 66 text

A development task has only 3 states Not yet started Finished

Slide 67

Slide 67 text

A development task has only 3 states Not yet started Finished Almost done

Slide 68

Slide 68 text

Scope (cost)
 Resources Time « Nine women can't make a baby in one month. » Management 101

Slide 69

Slide 69 text

Scope (cost)
 Resources Time « Nine women can't make a baby in one month. » Management 101 Hiring or making, you have to choose

Slide 70

Slide 70 text

Scope (cost)
 Resources Time « This is what has been signed » Management 101

Slide 71

Slide 71 text

Management 101 Scope (cost)
 Resources Time The Iron Triangle Scope = Time x Resources

Slide 72

Slide 72 text

Management 101 Scope (cost)
 Resources Time The Iron Triangle Scope = Time x Resources The Iron Triangle is a lie !

Slide 73

Slide 73 text

Scope (cost)
 Resources Time Quality

Slide 74

Slide 74 text

Scope (cost)
 Resources Time Quality

Slide 75

Slide 75 text

Scope (cost)
 Resources Time Quality Stress

Slide 76

Slide 76 text

Scope (cost)
 Resources Time Quality Stress Anger

Slide 77

Slide 77 text

Scope (cost)
 Resources Time Quality Stress Anger Rotten software

Slide 78

Slide 78 text

Scope (cost)
 Resources Time Quality Stress Defect Anger Rotten software

Slide 79

Slide 79 text

Scope (cost)
 Resources Time Quality

Slide 80

Slide 80 text

Scope (cost)
 Resources Time Quality The only thing you can flex

Slide 81

Slide 81 text

Scope (cost)
 Resources Time Quality You have to choose your next features carefully. The only thing you can flex

Slide 82

Slide 82 text

Scope (cost)
 Resources Time Quality You have to choose your next features carefully. The only thing you can flex Based on what has the most value for the customer

Slide 83

Slide 83 text

« The best way to predict the future is to implement it. » — Alan Kay

Slide 84

Slide 84 text

We need a new hedging strategy

Slide 85

Slide 85 text

We need a new hedging strategy Making the right product

Slide 86

Slide 86 text

We need a new hedging strategy Making the right product And delivering it

Slide 87

Slide 87 text

We need a new hedging strategy Making the right product And delivering it A non delivered product has a no value !

Slide 88

Slide 88 text

Validation over guess & illusions

Slide 89

Slide 89 text

Validation over guess & illusions Stop tracking progress, start to experience it

Slide 90

Slide 90 text

Validation over guess & illusions Smaller batch Stop tracking progress, start to experience it

Slide 91

Slide 91 text

Validation over guess & illusions Smaller batch Tell smaller lies Stop tracking progress, start to experience it

Slide 92

Slide 92 text

Validation over guess & illusions Smaller batch Tell smaller lies Stop tracking progress, start to experience it What about 1 day sprint ?

Slide 93

Slide 93 text

Reduce your feedback loop

Slide 94

Slide 94 text

Reduce your feedback loop Continuous Delivery

Slide 95

Slide 95 text

Reduce your feedback loop Continuous Delivery A delivered feature is no longer a risk !

Slide 96

Slide 96 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution Feedback loops

Slide 97

Slide 97 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Feedback loops

Slide 98

Slide 98 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Type system Feedback loops

Slide 99

Slide 99 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Pair programming Type system Feedback loops

Slide 100

Slide 100 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Pair programming Unit tests Type system Feedback loops

Slide 101

Slide 101 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Pair programming Unit tests System metaphor Type system Feedback loops

Slide 102

Slide 102 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Pair programming Unit tests System metaphor Continuous Integration Type system Feedback loops

Slide 103

Slide 103 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Pair programming Unit tests System metaphor Continuous Integration On site customer Type system Feedback loops

Slide 104

Slide 104 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Pair programming Unit tests System metaphor Continuous Integration On site customer Collective ownership Type system Feedback loops

Slide 105

Slide 105 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Pair programming Unit tests System metaphor Continuous Integration On site customer Collective ownership Acceptance testing Type system Feedback loops

Slide 106

Slide 106 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Pair programming Unit tests System metaphor Continuous Integration On site customer Collective ownership Acceptance testing Type system Planning game Feedback loops

Slide 107

Slide 107 text

Time Seconds Minutes Hours Days Weeks Statements & methods Classes & Interface Design Architecture Features Priorities Solution IDE Pair programming Unit tests System metaphor Continuous Integration On site customer Collective ownership Acceptance testing Type system Planning game Short releases Feedback loops

Slide 108

Slide 108 text

Predictability comes from technical excellence

Slide 109

Slide 109 text

Predictability comes from technical excellence « The quality of today is the productivity of tomorrow » — JB. Dusseaut

Slide 110

Slide 110 text

A = What is the cost to create X ? & B = How much did it cost to produce X ?

Slide 111

Slide 111 text

A = What is the cost to create X ? & B = How much did it cost to produce X ? What our customers need next ? & How do we put it as quickly as possible in front of them ?

Slide 112

Slide 112 text

A = What is the cost to create X ? & B = How much did it cost to produce X ? What our customers need next ? & How do we put it as quickly as possible in front of them ? From Planification to Prioritization

Slide 113

Slide 113 text

Product Management Software engineering Management Agile Command & Control Project Product

Slide 114

Slide 114 text

« We're All In This Together » — Virgin America

Slide 115

Slide 115 text

Stop the project manager posture

Slide 116

Slide 116 text

Stop the project manager posture There is not such thing as an Agile Project Manager

Slide 117

Slide 117 text

— @johncutlefish

Slide 118

Slide 118 text

what goes into production is what the developers have understood

Slide 119

Slide 119 text

Stop producing specifications without your dev team what goes into production is what the developers have understood

Slide 120

Slide 120 text

If you are not involved in the production process, please don’t get involved…

Slide 121

Slide 121 text

If you are not involved in the production process, please don’t get involved… TDD, Pair Programming, …

Slide 122

Slide 122 text

Product Manager Dev Team

Slide 123

Slide 123 text

Give Trust, not Toys

Slide 124

Slide 124 text

Give Trust, not Toys Andon

Slide 125

Slide 125 text

Give Trust, not Toys Andon Developers should have the right to stop the production pipeline

Slide 126

Slide 126 text

Hoshin Kanri « How to scale Agile »

Slide 127

Slide 127 text

Thanks! @lilobase lgo.group NewCrafts Bordeaux 3 & 4 octobre 2019 bordeaux.ncrafts.io