Saint TeamLead Conf · St. Petersburg · Sep 24–25, 2018
Scaling a Team Tenfold
How to stay sane as a frontend team lead on the ↗tinkoff.ru acquisition team
/ Scaling a Team Tenfold · Saint TeamLead Conf 2018
How to stay sane as a frontend team lead on the ↗tinkoff.ru acquisition team
How to stay sane as a frontend team lead on the tinkoff.ru acquisition team
Alexander Polomodov, Frontend team lead, customer acquisition, Tinkoff.ru
What this talk is about
Five steps that reshaped the frontend architecture, the team structure, and the team lead's duties.
Focus — Frontend of the tinkoff.ru unauthenticated zone
Scale — Team 4 → 40, team leads 1 → ~10
Frontend of the tinkoff.ru unauthenticated zone
Team 4 → 40, team leads 1 → ~10
What we owned and what the business wanted
Unauthenticated zone and internet bank
Stakeholders — all business units
Path from click to application
Growing stream of requests
At scale, cheaply — Clients in volume, at a price
Usable UI/UX — A modern path from click to application
Scalable processes — Campaigns and tests without releases
Build product pages
A/B tests and personalization
Launch campaigns fast
Measure the effect
A monolith with shared releases — one team for everything
A buffer in front of stakeholders, and our own releases
Stakeholder communication
Code and deploys
Too many contexts
Split the app and the team by product
More developers and QA
Growing task volume
One lead as the bottleneck
Inside the company
performance review of developers
potential tech and team leads
Outside the company
candidate requirements
a dedicated hiring track
Shared parts into packages, org work to release managers
More teams now
Each builds its own
Same forms rebuilt again
What we started measuring so quality wouldn't slip as we grew
Volume — Functionality per release
Speed — Average time to release
Quality — Escaped defects
Separate repositories and clear ownership boundaries
Side effects from others' edits
Hard to try new things
Nobody owns the shared code
How it should work
shared understanding of goals
agreed architecture vision
right decomposition
The risks
work detached from business
funded with leftovers
botched decomposition
Teams keep growing — the architecture has to catch up again
Clearly understand business goals
Know the team's lifecycle stage
Know your duties at that stage
Honestly decide: do you want it
…or keep writing code
Tinkoff.ru
Thank you! Questions — scan the QR, or email [email protected]
Alexander Polomodov, Frontend team lead, customer acquisition, Tinkoff.ru
Ask a question