👩‍💻 You, **SRE** or **dev**, did you ever wondered how to get your PM to prioritize a ***pipeline CI/CD*** over a feature?

👀 You, **QA** or quality manager, how many times have you campaigned for **automated testing** of your application's critical requirements?

👨‍💼 You, **DSI**, how many SteerCO meetings have you taken part in as a mediator between production and business players to find a cost/quality/impact compromise without having any factual arguments?

After accompanying **more than 50 teams** in their **DevOps transformations**, I share with you how I go about helping them save from **30% to 500%** in average *delivery* time, respectively from 15d-->10d and 4months -->3 weeks!

One thing's for sure: you were all right: **good business financial performance = good software engineering practices**: testing, CI/CD, agility, observability ... The authors of the book *__Accelerate__* confirm this statistically and even tell us what makes leaders successful. The key ... is acceleration!

[Accelerate [2018 Forsgren, Humble, Kim] (ISBN 1942788339)](https://www.goodreads.com/book/show/40313863-accelerate)

Hello,

There are basically two topics I'm covering in this talk:
- The Accelerate book and the *"State of DevOps "* studies conducted by Google Cloud / DORA.
- How **in practice** I start or reinforce the implementation of a DevOps transformation, from tools to corporate culture.

Both are obviously linked, since the principle of my coaching is to highlight **a tangible impact** to the implementation of tools and practices, and this is what the authors *of Accelerate* prove.

# Background
## In theory: Accelerate

Like Team Topologies or Domain Driven Design, Accelerate has become a reference in the IT market since its publication in 2018. DORA's research model and statistical results are edifying!
So I'd like to share, not to say evangelize, on this subject, which is coming up in every company I come across: CDiscount, Décathlon, PayFit, Engie, La Banque Postale, ...

This year, I'm bringing you an update on the *State of DevOps* studies.

## In practice: my REX

I then explain how to get started effectively, whether with the sponsorship of management or just the will of the teams, based on my feedback.
I propose a progression path:
- which engineering practices: pipeline, automated testing, infra cloud
- which methodological approaches: **Lean IT and *Value Stream Mapping***, KPIs

I've already addressed this subject on several occasions at private and public conferences.