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

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

Beb422437c1dfb5366f197919e41ac50?s=128

Arnaud LEMAIRE

October 10, 2019
Tweet

Transcript

  1. None
  2. Agile 101 Let’s become Agile ! @lilobase

  3. 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)
  4. 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 ?
  5. More X to solve X « We need to follow

    the SCRUM guide more strictly »
  6. None
  7. None
  8. We find the Customer !!

  9. 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 !
  10. « Apparently, this SCRUM thing is so great, you need

    a person on every team dedicated to forcing the others to do it » @cgosimon
  11. - "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
  12. Product Management Software engineering Management Agile Command & Control Project

    Product
  13. « 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
  14. Structural Integrity Stress

  15. Structural Integrity Stress

  16. Structural Integrity Stress

  17. Pace of changes Agile development puts a lot of stresses

    on the system
  18. Until it breaks Pace of changes

  19. And the system is not only about the source code

    Stress people people And often their last defense has been taken away
  20. You need very specific and hard to master software design

    foundation Refactoring You’ll need TDD Decoupling
  21. Technical Excellence enable Business Agility Not the other way around

  22. « So much of what we call management consists in

    making it difficult for people to work. » — Peter Drucker
  23. Management 101 Management 101 @lilobase

  24. 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
  25. Mesure it and repeat Management 101

  26. 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 ?
  27. Management 101 Scope (cost)
 Resources Time The Iron Triangle Scope

    = Time x Resources
  28. 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
  29. A development task has only 3 states Not yet started

    Finished Almost done
  30. Scope (cost)
 Resources Time « Nine women can't make a

    baby in one month. » Management 101 Hiring or making, you have to choose
  31. Scope (cost)
 Resources Time « This is what has been

    signed » Management 101
  32. Management 101 Scope (cost)
 Resources Time The Iron Triangle Scope

    = Time x Resources The Iron Triangle is a lie !
  33. Scope (cost)
 Resources Time Quality Stress Defect Anger Rotten software

  34. 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
  35. « The best way to predict the future is to

    implement it. » — Alan Kay
  36. We need a new hedging strategy Making the right product

    And delivering it A non delivered product has a no value !
  37. Validation over guess & illusions Smaller batch Tell smaller lies

    Stop tracking progress, start to experience it What about 1 day sprint ?
  38. Reduce your feedback loop Continuous Delivery A delivered feature is

    no longer a risk !
  39. 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
  40. Predictability comes from technical excellence « The quality of today

    is the productivity of tomorrow » — JB. Dusseaut
  41. 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
  42. Product Management Software engineering Management Agile Command & Control Project

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

  44. Stop the project manager posture There is not such thing

    as an Agile Project Manager
  45. — @johncutlefish

  46. Stop producing specifications without your dev team what goes into

    production is what the developers have understood
  47. If you are not involved in the production process, please

    don’t get involved… TDD, Pair Programming, …
  48. Product Manager Dev Team

  49. Give Trust, not Toys Andon Developers should have the right

    to stop the production pipeline
  50. « Scaling is only hard if you talk about Agile

    without actually doing it. » — Arlo Belshee
  51. We are not getting better

  52. None
  53. None
  54. « Anyone building a process or framework for scaling Agile

    doesn’t know Agile. Period. Learn to ship software at will without any risk of defect, and you will discover you no longer need your framework. » — Arlo Belshee
  55. Hoshin Kanri « How to scale Agile »

  56. Thanks! @lilobase lgo.group