scale quality with kaizen - tech.rocks conference
TRANSCRIPT
![Page 1: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/1.jpg)
How to Scale Quality
With Kaizen
![Page 2: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/2.jpg)
From building MVPs to addressing scale● Theodo
○ agile tech-team-for-hire, Paris & London, 200 people ○ x10 growth from 2012 to 2016
● Our strength: build & deploy MVPs in less than 10 weeks○ Small teams of excellent engineers + super strong agile discipline
● Until 2016, when the project scaled...
○ ↘ velocity and enthusiasm
○ ↗testing time, complexity and cost of integrating new devs
![Page 3: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/3.jpg)
Today, I will share with you 3 counter-examples from 2017
![Page 4: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/4.jpg)
A dev team produced 220 perfect user stories in a row...
...and tripled the velocity!
![Page 5: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/5.jpg)
A dev team scaled from 4 to 12 devs over the year...
… while continuously decreasing the build time
![Page 6: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/6.jpg)
A dev team trying to integrate 3 new developers efficiently...
was so efficient that the average velocity increased by 2x!
![Page 7: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/7.jpg)
It all started with two things
1. Benoît went to Japan with Michael Ballé
![Page 8: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/8.jpg)
2. Theodo UK forced us to rethink our added value
![Page 9: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/9.jpg)
...to go fast?
Why would you need excellent engineers?
For that we have quick&dirty off-shoring
...to make a good product?
For that we have excellent design agencies
...
French CTO
UK CEO
![Page 10: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/10.jpg)
Brits are pragmatic, they buy business results
What is the business impact of excellent engineers?=> Products that scale
So:● we had to focus on becoming expert at code that scales● and for that we looked at Toyota...
![Page 11: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/11.jpg)
![Page 12: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/12.jpg)
改善
![Page 13: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/13.jpg)
My definition of Kaizen:
The cultural effort of trying to improve continuously, as a team, on an identified problem.
What is 改善?
![Page 14: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/14.jpg)
![Page 15: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/15.jpg)
Our current recipe (continuously improving)
● A clear target addressing a problem “0 bugs deployed by 31/10/2017”
● A team, a team leader, a coach and a sponsor
● A whiteboard
● Make sure time is spent on Kaizen
![Page 16: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/16.jpg)
A clear indicator, updated every day / every week
A schema of the situation
The last identified defects to analyse
them
Ideas for experiment, expected results and
checks
![Page 17: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/17.jpg)
#1: “0 bugs Kaizen” on a large project in productionWhat?● Look at every bug in production to find team improvements
Improvement examples:● Create a standard way of coding an API call cache● Make sure everyone is using a well-configured IDE with a debugger
BUT● Bugs not clearly defined: some UX issues were not considered important● Analysis was very hard: not reproducible or too old to understand● Temptation to solve and move on was too strong
![Page 18: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/18.jpg)
Kaizen topic chosen by CTO without proper go&see...
![Page 19: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/19.jpg)
… is not the right way to do kaizen!
![Page 20: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/20.jpg)
#2: “0 defects Kaizen” on a long redevelopmentWhy?● Client voice: “I wish I could validate all user stories at first try”
What?● Look at every issue during the development flow to find improvements
Improvement examples● Agree to define validation steps beforehand● Improve the definition of a “perfect” user story ready for development● Refactor emails to not have duplicate code for text and html versions
![Page 21: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/21.jpg)
Results:● 220 User Stories in a row validated at first try by the Product Owner!● x3.5 velocity over 15 weeks
![Page 22: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/22.jpg)
#3: “Divide build by 2 Kaizen” on a 3 teams projectWhy?● Devs were fed up of wasting so much time on failed and/or long builds
What?● Inspect build failure rate & build time and experiment ideas every week
Improvement examples● Refactor tests, update testing libraries, migrate to ES6● Pre-hook to run tests locally before build, stop tests at first fail● Switch to Circle-CI 2.0● Only run tests linked to modified code
![Page 23: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/23.jpg)
Results:● Build failure rate divided by 3● Build time divided by 2 and maintained low
![Page 24: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/24.jpg)
#4: “Succeed 100% of sprints” (while integrating 3 new devs)
Why?● There were many late sprints already and the team was concerned of how
worse it would become with the dev team growing from 3 to 6
What?● For every ticket, plan the “how” before coding (steps of 2 to 20 minutes),
get it challenged and ask for help as soon as the plan goes wrong
Improvement examples● Script ticket start to reduce that step from 10 to 3 minutes ● Change DB creation step to reduce testing from 18 to 7 minutes ● Competency matrix of every dev to know whom to train on what
![Page 25: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/25.jpg)
Results:● Less than 5% User Story longer than planned!● 7/7 sprint success!● Average velocity x2!
![Page 26: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/26.jpg)
The
Future
![Page 27: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/27.jpg)
● Not only is kaizen helping us scale quality● It is also empowering every developer to act as a tech leader...● … growing Theodoers at much faster speed than ever before
![Page 28: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/28.jpg)
“J’ai autant appris cet après-midi qu’en deux ans chez Theodo”
Nicolas
![Page 29: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/29.jpg)
Seeing the spectacular progress made me think of the 10x developer myth
![Page 30: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/30.jpg)
At current speed of progress, 10x is just a few years away…… and unlike the car industry, software is not limited by the law of mechanics. What is the limit of progression?
![Page 31: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/31.jpg)
Are we creating an army of 100x developers?
![Page 33: Scale quality with kaizen - Tech.Rocks conference](https://reader031.vdocuments.mx/reader031/viewer/2022030318/5a656c287f8b9af13a8b493b/html5/thumbnails/33.jpg)
Rendez-vous in 2025