Insights on How Team Topologies Drive Organizational Success - Manuel Pais - GOTO 2024 - Part II (Category Management)

With this post, I’m going to end with a talk by Manuel Pais, co-author of Team Topologies. In past post I started reviewing this insight story from the practical application of team topology.

7. The author touches on the inconsistent user experience. The BBC story is cited as a case study (It's not on the site either.). The bottom line here was that the BBC had a lot of products, each of which had its own distinct interface, and users didn't like it very much:) As a result, the BBC simply isolated the standard front-line components, but also made a big reorg that they were not the only ones. described on his Medium. As a result, the author highlights the following Optimize for innovation and speed when those are needed, allow “eventual consistency” and standartization to emerge later

• Practice: Collaborate, facilitate, x-as-a-service. Platform teams need to choose the right type of interaction 8. The author moves to a slow time-to-market. An example of SAP, which has difficulties with speed due to compliance with legal requirements and security, is considered. (And probably not just because of that.). As a result, the guys took up an internal platform to simplify the work of development teams. The platform was seen as a product targeted at teams suffering from complex compliance and safety processes. Turn blocking dependencies into unblocking ("dependency inversion" for teams)
• Practice: Product management in platform. You can read more about this in my CNCF Platform White Paper: 1, 2 and 3 9. The thesis is “we can’t do that in my organization.” This is a GfK/NIQ case. The guys ala SAFE and all the teams are engaged in product development. They figured out that one in five sprints will work on platform tasks. The principle is “behaviors over structures”. Don't wait for the ideal org / process / scale
• Practice: Thinnest viable platform. You can start with as thin a platform as possible, which already benefits the organization. 10. Team topology is seen as a socio-technical approach to increase flow and increase satisfaction. Organizations can apply the ideas of team topology in different areas of business, adapting them to their needs. It is important to have a vision and understand the principles of team topology. The examples above show how ideas and principles can be adapted to the current situation. The community around the topology of teams is active and engaged, and there are plenty of resources to explore and apply these ideas.

#Management #Leadership #PlatformEngineering #Software #SoftwareDevelopment #Architecture #Processes