Skip to content

YaTalks · December 6, 2023

YaTalksYandex for Developers

How to Form Team Structure for Business Demands

Five transformations from a project to end-to-end teams

From the business goal to team boundariesBusiness goalUIAPIDataTeam 1Team 2
Five transformations01Project02Product03Scale04Superapp05Value stream
/ How to form team structure · YaTalks 2023

Slide contents

  1. 1. How to Form Team Structure for Business Demands

    Five transformations from a project to end-to-end teams

  2. 2. The Goal Shapes Architecture and Team Boundaries

    Start from the desired future

    Make the target architecture explicit

    Shape team boundaries around it

    Treat the transition as work of its own

    Stabilize what is burning before redesigning the system

  3. 3. 00. Tools and Algorithm

    From the desired future to a managed transition

  4. 4. The Desired Future Shapes Today’s Plan

  5. 5. Different Challenges Need Different Tools

  6. 6. Stability First, Then a New Structure

  7. 7. 01. Project: Migrating Tinkoff.ru

    Three months to fix critical acquisition problems

  8. 8. Four Problems Before the Migration

  9. 9. Project Team: Two Releases a Week

  10. 10. Forms Moved with Little Efficiency Loss

    Core forms and pages moved on time

    Acquisition efficiency was largely preserved

    The team learned to resolve acute problems

    The resulting product was ready to scale

    After migration, the team could plan product development

  11. 11. 02. Product: Deliberate Development

    Explicit ownership, APIs, and Kanban

  12. 12. Architecture Defines Team Responsibilities

  13. 13. APIs and Pull Connect the Teams

  14. 14. Visible Work and Predictable Throughput

    Teams understand their areas of ownership

    Work is visible to teams and customers

    Throughput became predictable

    The process gained a path for improvement

    The product teams were ready to scale

  15. 15. 03. Scale: Product and Platform

    Feature-team autonomy without duplicating shared solutions

  16. 16. Team Types Combine with Interaction Modes

  17. 17. A Shared Platform for Autonomous Teams

  18. 18. Products Own Features, Platforms Own Shared Tools

    Product teams ship features

    The platform team develops shared tools

    Shared React components connect through DI

    Teams moved to microfrontends

    The teams develop the unauthenticated part of Tinkoff.ru

  19. 19. 04. Mobile Bank as a Platform

    Autonomous business domains and platform teams in one application

  20. 20. The Mobile Bank Becomes a Platform

  21. 21. One App Connects Different Businesses

  22. 22. Product and Platform Teams Split Responsibilities

  23. 23. Shared Architecture Supports Autonomous Domains

  24. 24. Autonomous Teams, Scheduled Releases

  25. 25. Each Business Has Its Own Mobile Team

    Business verticals gained teams and backlogs

    Platforms strengthened modularity, SRE, performance, and CI/CD

    Release frequency increased several times

    Teams own process improvement themselves

    Autonomy works when shared qualities have owners

  26. 26. 05. Teams Across the Value Stream

    Reduce time to market and cognitive load, improve end-to-end architecture

  27. 27. One Team Spans All Technology Layers

  28. 28. One Team Owns the Entire Stack

  29. 29. Team Boundaries Reshape End-to-End Work

  30. 30. Shared Rules Are Checked Automatically

  31. 31. Metrics Show Platform Impact on Teams

  32. 32. Different Challenges Require Different Team Structures

  33. 33. Teams Follow the Target Architecture

    Start from the long-term business goal

    Derive boundaries from the target architecture

    Choose team types and interaction modes

    Automate shared rules and measure outcomes

    Changing structure takes deliberate work with people

  34. 34. What the Model Builds On

    Author PDF for YaTalks 2023 · 172 pages

    Backcasting, Kanban and the inverse Conway maneuver

    Team Topologies and change management

    Five cases from Tinkoff.ru and the Superapp

  35. 35. Thank you!

    Knizhny kub

    Continue the discussion: t.me/book_cube

    Alexander Polomodov, Technical Director, Tinkoff

    @book_cube