Et si on redémarrait l'agile ? — Agile Tour Bordeaux 2018

Vidéo disponible sur la page de l'Agile Tour Bordeaux : https://www.facebook.com/Agiletourbordeaux/videos/263415924530627

Transcript

2. Let’s Reset Agile @lilobase lgo.group
3. I’m no longer an “Agilist”
4. « Apparently this SCRUM thing is so great, you need a person on every team dedicated to forcing the others to do it » @cgosimon
5. - "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
6. Product Management Production Management Agile Command & Control « Making the right thing right »
7. Cost Time Scope Quality The Iron Triangle
8. What is the cost to create X ? How much did it cost to produce X ?
9. Tracking velocity Estimating our project How do we get better at Refining the backlog
10. More X to solve X
16. Tracking velocity Estimate our project These are the symptoms, not the causes Refining the backlog
17. It’s time to focus on what creates value Making the right product And delivering it
18. Companies are driven by fear (of loss) This is what they consider « risks »
19. Product Management Production Management Agile Command & Control « Making the right thing right »
20. What is the cost to create X ? How do we reduce the risk ?
21. How do we reduce the risk ? Reduce your feedback loop Continuous Delivery
22. 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
23. Validation over assumption Smaller batch Tell smaller lies
24. Predictability comes from technical excellence Refactoring capabilities TDD / Pair Programming / …
25. Destroy the run vs project model
26. Product Management Production Management Agile Command & Control « Making the right thing right »
27. Give Trust, not Toys Jidoka
29. If you are not involved in the production process, please don’t get involved… Enterprise architect, Scrum Master, Product Owner…
30. @johncutlefish
31. You need product management Stop the project manager posture
32. Product Management Production Management Agile Command & Control « Making the right thing right »
33. Coach, PO, Management Break the us vs them Business Units
34. Dev, QA, Ops Fully featured & autonomous team UX, UI, Legal, PO
35. A PO is not a foreman for the dev team (neither is the ScrumMaster) But a member of it
36. They have nothing to say on how the team works A PO is not a supervisor for the dev team (neither is the ScrumMaster) He does not dictate the planning
37. Stop producing specifications without your dev team what goes into production is what the developers understood
38. Let’s Reset Agile @lilobase lgo.group
39. It is not sufficient to simply be aware of the problem Causes vs Symptoms
40. Agile is first about Software Engineering ! You need evolutionary architecture And it puts a lot of stress on the design
42. BTW, Clean Code is not a software architecture You need to know how to build application !
43. Let’s Reset Agile @lilobase lgo.group
44. Stop trying to improve your ceremonies ! Start improving your delivery mechanism
45. Most dev team are constipated
46. AGILE
47. Can you Install a local dev env in less than 20 min and 2 actions ? If you can’t, don’t expect to have a good delivery !
48. Do 1 day Sprint And it should be deployed in production « Tell smaller lies »
49. Stick to your practices Choose interconnected ones
51. Pair programming Instead of « better » code review
52. Stop being afraid of modifying the existing source code You’ll need TDD
53. Stop Ruinous Empathy Embrace radical candor
55. The certification business is the scientology of agile…
57. How to scale ? DONT! DON’T FUCKING DO IT PLZ STOP TRYING TO SCALE AGILE! YOU DON’T NEED SCALED AGILE FOR FUCKS SAKE! MATURE AGILE TEAM CAN SCALE WITHOUT NEEDING A MANAGEMENT BULLSHIT TRYING TO SCALE THEM! MAKE YOUR MANAGER BUSY BY DOING SOMETHING ELSE! BUT PLZ STOPIT, REALLY, IT IS QUITE SCARY AT THIS POINT! DON4T1!!11!1
58. - R. Jeffries « But they’re large companies. So, naturally, they think they need to scale. […] they’re wrong. They don’t need to scale. They need to do plain old simple Agile software development. »
59. - R. Jeffries « That’s not to say that large-scale Agile won’t be successful; very likely it will be. It will be successful in the sense that large companies will buy scaling products and ideas, and consultants and training companies will enrich themselves selling what these large companies want. »
60. - R. Jeffries « If your individual teams cannot work in an Agile fashion, then clearly you’re not ready to “transition” your company or to “scale” Agile. You don’t want to transition to something you can’t do, and you don’t want to scale something that doesn’t work. »
61. - R. Jeffries « First, start creating teams that are very capable of doing Agile. Then, give them the most important, most valuable work to do that your organization can come up with. And stand back. Keep creating Agile teams, organized by features where possible. You may find that you have little need to scale Agile. »
62. When a team has a good delivery mechanism Agile became easy !
63. Thanks! @lilobase lgo.group