How to form a team structure for business needs 1

The latest. 7 I’ve been working at Tinkoff for years and have seen and been responsible for a lot of changes: organizational, product and engineering. I’ve covered many of them in speeches and articles, but there was usually a focus on a specific change. In this post, I would like to talk about the principles of team design and management structure, without which it would be much more difficult for me to understand what needs to be changed and why. To do this, you need to remember a few basic things.

• Working backwards or backcasting approach It is better to start from the end, presenting the goal of change and the final result.
• The Conway Act Melvin Conway’s claim that organizations design systems that replicate the communication structure of the organization
• Conway's reverse maneuver An approach that recommends the evolution of team structure and organizational structure to promote the desired architecture in the organization.
• **Topology of teams (Team topology)**a fruitful approach with a set of patterns for structuring the types of commands and their interactions, which introduces 4 Stream-aligned, platform, enabling, complicated subsystem and three types of interactions: collaboration, facilitating, x-as-a-service.
• Change management (Change management) A set of approaches to implement change at all levels: individual, team and organizational. Now that I have mentioned the concepts themselves, I can describe my approach to forming a management structure.

The algorithm is about this

1. Determine the long-term goal of the part of the company you are responsible for
2. Evaluate which system architecture works best for this purpose
3. Apply Conway's reverse maneuver to understand which team structure will support the desired architecture
4. Use patterns from team topologies to design the structure of teams and how they interact
5. Use change management to plan and execute (We talked about the organizational and team level above, and we will not discuss the individual here.)

In the next part, I will talk about the application of this algorithm to 4 scripts: **- Project (launch of new initiative)

• Product development (simple product development)
• Scaling up development (scaling up)
• Scaling development down (scaling down)** I went through all the stages in practice and even talked about many of them:)

P.S. I'm drawing up sources to study. About backcasting we discussed in series Code of Architecture on Technology Strategy Patterns

• Written about working backwards book You can read about Conway's Law in wikipedia
• Conway's reverse manoeuvre in 2014 year hitch in techradar from ThoughtWorks Teams as means of Delivery, Team Topologies that work for flow, Evolving team interactions for innovation and rapid delivery. About change management is well written in the book "Our iceberg is melting" about which I have already wrote

#Management #Leadership #Processes #ProjectManagement #Project #Software #SoftwareDevelopment