Et si on redémarrait l’agile ? — Agile Grenoble 2019

Slide 1

Slide 1 text

No content

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.Jeﬀries - The State of Agile Software in 2018 — M.Fowler - The Tragedy of Craftsmanship — Robert C. Martin - Developers Should Abandon Agile — R.Jeﬀries - The Failure of Agile — Andy Hunt - Time to Kill Agile — D.Thomas - The agile hangover — S.Mancuso

Slide 4

Slide 4 text

Before Agile 101 After Project manager Product Owner (Agile Project Manager) Estimates in Man/Day Tracking progress Tracking progress (But it is a nice burn-down chart) Production releases every six months. Production releases every 6 months (But we have 2 weeks sprints) Estimates in points (and convert them in man/day)

Slide 5

Slide 5 text

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

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

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

Slide 8

Slide 8 text

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

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

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

Slide 12

Slide 12 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 13

Slide 13 text

Structural Integrity Stress

Slide 14

Slide 14 text

Structural Integrity Stress

Slide 15

Slide 15 text

Structural Integrity Stress

Slide 16

Slide 16 text

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

Slide 17

Slide 17 text

Until it breaks Pace of changes

Slide 18

Slide 18 text

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

Slide 19

Slide 19 text

Technical Excellence enable Business Agility Not the other way around Clean code is not enough

Slide 20

Slide 20 text

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

Slide 21

Slide 21 text

« So much of what we call management consists of making it diﬃcult for people to work. » — Peter Drucker

Slide 22

Slide 22 text

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

Slide 23

Slide 23 text

Measure it and repeat Management 101

Slide 24

Slide 24 text

Management 101 The Iron Triangle Scope = Time x Resources

Slide 25

Slide 25 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 26

Slide 26 text

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

Slide 27

Slide 27 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 28

Slide 28 text

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

Slide 29

Slide 29 text

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

Slide 30

Slide 30 text

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

Slide 31

Slide 31 text

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

Slide 32

Slide 32 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 33

Slide 33 text

Creating our burn- down charts Agile 101 6 months after… Tracking velocity Estimating our project How do we get better at Reﬁning the backlog How m uch will it cost to m ake X ? & How m uch did it cost ?

Slide 34

Slide 34 text

Product Management Software engineering Management Agile Command & Control Project Product

Slide 35

Slide 35 text

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

Slide 36

Slide 36 text

We need a new hedging strategy Making the right product And delivering it A non-delivered product is a risk !

Slide 37

Slide 37 text

Validation over guess & illusions Tell smaller lies What about 1 day sprint ?

Slide 38

Slide 38 text

Reduce your feedback loop Continuous Delivery Stop tracking progress, start to experience it

Slide 39

Slide 39 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 40

Slide 40 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 Planiﬁcation to Prioritisation

Slide 41

Slide 41 text

Product Management Software engineering Management Agile Command & Control Project Product

Slide 42

Slide 42 text

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

Slide 43

Slide 43 text

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

Slide 44

Slide 44 text

Stop producing speciﬁcations without your dev team what goes into production is what the developers have understood

Slide 45

Slide 45 text

— @johncutleﬁsh

Slide 46

Slide 46 text

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

Slide 47

Slide 47 text

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

Slide 48

Slide 48 text

Product Manager Dev Team

Slide 49

Slide 49 text

« Economies of scale are true in milk, not in software development » — @allankellynet

Slide 50

Slide 50 text

No content

Slide 51

Slide 51 text

No content

Slide 52

Slide 52 text

« Two-Pizza Teams work like semi-independent entrepreneurial hothouses. Insulated from the greater organisation’s bureaucracy » — John Rossman

Slide 53

Slide 53 text

« Learn to ship software at will without any risk of defects, and you will discover you no longer need your framework. » — Arlo Belshee

Slide 54

Slide 54 text

Thanks! @lilobase lgo.group