Summary of Death Of The "Spotify Model" • Gijs Meijer & Marcin Pakulnicki • GOTO 2022

00:00:00 - 00:45:00

The video discusses the "death of the Spotify model" of having small, autonomous teams that work on their own projects. The team at which the video was filmed switched to a model where all work is done in code, with each developer having responsibility for their own part of the project. This makes it easier to monitor and improve the quality of the code, and ensures that all the necessary pieces of the project are in place.

• 00:00:00 In this talk, Gijs Meijer and Marcin Pakulnicki discuss the concepts of an agile organizational model and how it applies to daily banking at ING. They note that, in order to implement these concepts, developers must be given Macs to work on, and that it is important to have a remote blast radius for high performing teams. Finally, they discuss the book "The DevOps Handbook" and how it has helped them in their work.
• 00:05:00 The video discusses the journey that the team at ING took in order to transition to a more effective way of working. The team moved away from projects and towards fixed-capacity squads, which helped to simplify business interactions and cut down on communication overhead. While there were some good aspects to this change, it also introduced someissues, such as increased communication overhead and the growth of teams to larger sizes.
• 00:10:00 The video discusses the challenges Spotify faced in scaling their engineering team and how they solved them by transitioning to a microservice architecture and Java programming language.
• 00:15:00 The speaker discusses the death of the "Spotify model", in which large teams work on long-term projects with no purpose. He argues that the concept of micro teams, in which each team has four or fewer developers and focuses on the most important thing at that moment, is a better solution.
• 00:20:00 The video discusses how the "Spotify model" of having small, autonomous teams that work on their own projects is no longer effective in the modern software development world. The team at which the video was filmed switched to a model where all work is done in code, with each developer having responsibility for their own part of the project. This makes it easier to monitor and improve the quality of the code, and ensures that all the necessary pieces of the project are in place.
• 00:25:00 In 2021, the daily banking tribe implemented a model where each engineer refines codes tests, deploys the whole bunch, and manages their dependencies with the whole I.T stack and the whole it landscape. This led to the team behaving as if they were a small startup within a larger scale, and eliminated the need for Ops.
• 00:30:00 The video discusses how the Spotify model, in which individual team members work on features without coordination, is no longer sustainable in the future. The Cloud Engineer role will be important in this transition, as they will standardize and coordinate work across teams, create pipelines and virtual machines, and audit stacks.
• 00:35:00 The speaker discusses the "Death of the Spotify Model" and how it means that teams will have to allocate more time to code features and manage access to the platform. He also notes that this is a time to reallocate people to more important tasks.
• 00:40:00 The video discusses the death of the "Spotify model" where micro teams are implemented in place of traditional teams. It goes on to discuss how change management is needed to implement this change and how patience is key to making it successful. Finally, the presenter shares how a vision and strategy were created together with other leaders in the company, and how communication and talent management are essential to success.
• 00:45:00 The speaker discusses the various changes they have seen in the tech industry over the past few years, including the evolution of the "Spotify model" where developers are given the choice to work with or not work with the company. They discuss the importance of making teams small, of having simple work, and of being patient in order to make changes. They also mention the importance of a cloud-based development environment, and encourage developers to give away Macs to new hires.