Scrum@Scale Case Study

Spotify: A Scrum@Scale Case Study

Scrum@Scale Trainer Henrik Kniberg discusses how key patterns of the Scrum At Scale Framework helped transform the engineering culture at Spotify, achieve continuous delivery and disrupt the music-streaming industry.
“We wanted to enable teams to move fast, to ship software as quickly as possible, with minimum pain and overhead.” – Henrik Kniberg

CASE STUDY SNAPSHOT

Trainer Name: Henrik Kniberg
Organization: Spotify
Organization Size:Large
Industry:
Arts, Entertainment, and Recreation
Topics: Organizational Culture, When to Scale
Date: 2014
Website: Henrik’s website

Summary

Scrum@Scale Trainer Henrik Kniberg discusses how he leveraged the Scrum at Scale Framework to transform the engineering culture at Spotify, achieve continuous delivery and disrupt the music-streaming industry.

Spotify Engineering Culture

In 2014, Henrik posted his “Spotify Engineering Culture” video (often referred to as the “Spotify Model”) for the community to take a look inside the Agile Engineering culture. In its early stages, Spotify was “pretty much a Scrum company”; Agile principles allowed teams to enhance and maintain a positive culture and eventually disrupt the music streaming industry. However, as Spotify continued to grow, the teams discovered the need for a better way to coordinate. Henrik co-trained with Dr. Jeff Sutherland to develop and introduce scaling patterns which utilize small, cross-functional, self-organizing teams, and to continue encouraging constant improvement, innovation, and continuous deployment.

Spotify’s Scaling Approach

Spotify’s approach to scaling Scrum was focused on constant improvement, innovation, and continuous deployment. Utilizing an early-adopters version of Dr. Jeff Sutherland’s lightweight Scrum@Scale framework allowed the “Spotify Model” to organically emerge. It included:

  1. Utilizing recurring strategy days, where leaders and stakeholders got together to align around a set of strategic principles, referred to in the Scrum@Scale Guide as Executive MetaScrum
  2. Encouraging Agile coaches to train, support and coach each other, which enabled their team to enhance and maintain a positive culture
  3. Introducing an Executive Action Team (EAT) of Product Owners, Chapter Leads, and Agile Coaches got together on a daily basis to solve high-level, high-impact problems

Success for Minecraft’s Development Team

Now that Henrik is with the Minecraft development team, he credits continuous improvement for keeping 90 million active users satisfied. The team rolls out new snapshot releases every week to its user base, resulting in incredibly fast product improvement.

Who is Henrik Kniberg

Henrik Kniberg is a Scrum@Scale Trainer who has worked with Scrum@Scale Founder, Dr. Jeff Sutherland, for over a decade. He has dedicated the last 12+ years to coaching and mentoring organizations based on Agile and Lean principles. He is currently with the Minecraft Development Team at Mojang, and has previously worked with Spotify and Lego.

 

 

More Case Studies

Achieve 5-10x Faster Market Delivery with Scrum at Scale

Achieve 5-10x Faster Market Delivery with Scrum at Scale

One of the Netherlands' largest DIY retail franchises had a siloed management structure and projects that took 3-12 months or even longer to get to market. They had a waterfall delivery style, with the entirety of the delivery at the end and no early value delivery for customers. Registered Scrum@Scale Trainer Serge Beaumont's approach started with the creation of cross-functional, autonomous teams, each solely responsible for a different part of the process. This allowed for work to proceed very quickly with each team simultaneously able to complete their part of a project without first waiting on another team. The results were immediate and impressive. The team achieved 5-10x faster market delivery to customers, there was now alignment between what was expected and what was delivered, delivery was made in smaller chunks allowing for early value delivery to customers, and e-Commerce sales soared.
Creating Customer-Centric Social Media Teams Using Agile

Creating Customer-Centric Social Media Teams Using Agile

In this case study, Christoph Dibbern tackles a myriad of challenges that were plaguing a social media-based organization – lack of prioritization, no organizational refactoring, and a lack of shared values. These challenges created an unproductive and unhealthy environment, where mistrust and misalignment were common and innovation was stifled. Utilizing Scrum@Scale, the organization was able to align around a customer-centric focus, work as a cohesive unit, and deliver high quality results to customers faster.
Preserve Culture While Scaling: The Road Back to Cohesiveness

Preserve Culture While Scaling: The Road Back to Cohesiveness

Gereon Hermkes explores the complexities of maintaining a cohesive corporate culture amidst the explosive expansion of a technology firm. To address this challenge, Gereon initiated a simple Scrum@Scale strategy focused on rejuvenating the core values of shared language, trust and cooperation. These principles had defined the company's early days but began to deteriorate with rapid scaling.