Fantastic Platform Teams and Where to Find Them

Why the Platform Team must shift to a product-driven mentality


The world of application development has changed dramatically in recent years. Monolithic applications have been replaced by services interconnected through APIs. Applications distributed across multiple services are often developed on multi-cloud infrastructures and developers and DevOps have the ability to choose the best tools to implement within their technology stack. In many companies, C-Level figures are realizing that IT teams dealing with application development use a myriad of different tools and solutions for data processing and analysis, observability and monitoring. , security and networking, particularly at the application level. The PlatformOps approach allows you to give order to this situation, bringing a real cultural change within the organization.
PlatformOps has spread with the increasing popularity and increasing use by companies of the DevOps methodology. This approach aims to simplify the processes involved as the DevOps practices in use by the company increase, allowing developers to focus on application development, rather than internal processes and tools, in order to always offer a better service to its customers.
But how can you do this? In order to scale the use of the DevOps methodology and retain the related knowledge, it is essential to rethink the structure of the DevOps teams: DevOps practices must be thought of as products and services of which the application development teams are users.
As Gartner states, by 2025 95% of enterprises will fail to scale DevOps initiatives if shared self-service platform approaches are not adopted.
In this talk I want to bring attention to the foundation of Platform Teams and how they should be organized in order to achieve the transition to a product-driven mentality