How Amazon and Spotify Used Scrum to Change How They Work | ALC Training News
- No comments
Amazon and Spotify are two market leaders known for their dynamism and technological know-how. In this Scrum case study, we’ll analyse how their approach to agile working improved the way they work and how this can be instructive for other organisations seeking to adopt agile practices.
How Amazon use Scrum in the workplace
Amazon, which hasÂ opened several warehouses in Australia, has long been using Scrum in its work practices. Since 1999, the company has been using agile practices for managing its employees.
In the years ranging between 2004 and 2009,Â Scrum became widely adopted in its development organisations. Amazonâ€™s adoption strategy has been described as an unplanned and decentralised transformation thatâ€™s different from the way Scrum adoption usually takes place.
6 Key characteristics of Amazonâ€™s use of Scrum include the following:
Amazonâ€™s teams were given broad discretion to solve their own problems without detailed prescriptive practices from a central authority. The decentralised decision-making discretion is designed to let teams create, deliver, and operate high-quality software in a streamlined and red-tape-free way.
Stable and long-lived teams support agile practices. Development teams have one manager to whom they report to directly. These standard Amazon team policies make the culture and work arrangement consistent with Scrum practices.
The spark was lit through team members who were happy to help educate others about Scrum on an ad hoc and voluntary basis. Once they were educated in the practices, individual teams were able to make ground-level decisions about how to implement it. The results these teams achieved drove other teams to become interested.
- Scale capacity
Amazon switched from dedicated servers to AWS and removed the siloed approach from their operations and development teams. This means their developers can deploy individual codes to any of their servers at their disposal, allowing the business to move and innovate faster. Engineers can scale up or down their capacity without restrictions.
- Better software
Adopting Agile has allowed Amazon to deliver better software and save considerably on costs. An average of their 40% of dedicated-servers capacity ended up going to waste. Shifting to Agile practices have seen their engineers deploy a code every 12 seconds, accompanied by a drop in the volume and duration of outages.
With ad hoc, voluntary Scrum education; an email-based Scrum community; and occasional Scrum master training sessions, a critical mass of teams had adopted the winning practice. Following this, a Scrum trainer/coach position was created, and having a full-time trainer on board meant easier adoption and high-quality agile working implementations.
Scrum implementation happened from the ground-level up at Amazon. No timelines or mandates were used. It didnâ€™t start with management-level decisions and prescriptive plans for adoption.
By encouraging Scrum through fostering a culture of innovation and ensuring information about it is available, organisations can drive adoption by responding to demand and removing impediments as theyâ€™re discovered. Allowing stable, long-term teams to exist and giving teams plenty of discretion about how they would adopt went a long way to make this approach to agile working successful.
How Spotify use Scrum in the workplace
For a contrasting approach, Spotify provides a suitable case study. Unlike Googleâ€™s â€śgrassrootsâ€ť strategy, the digital music service had aÂ systematic approach to adopting Scrum. Spotifyâ€™s approach has some similarities with Googleâ€™s, but its key tenet is living and breathing Scrum as a development methodology. The Scrum masters at Spotify are required to be experienced agile coaches, and many of the companyâ€™s Scrum masters are leading agile trainers.
In addition to complete management buy-in, Spotify uses small teams that, like Googleâ€™s Scrum teams, are totally independent. These â€śsquadsâ€ť are treated like individual startups. Theyâ€™re allowed to be fully autonomous and work independently to focus on assigned, specific functions within Spotifyâ€™s product.
These autonomous teams are organised into larger units of tribes and loosely structured into chapters and guilds to drive stronger knowledge sharing between teams. Spotify’s team approach seems to balance team independence with knowledge-sharing between specialist groups that don’t engage in daily collaboration. At the same time, Spotify is avoiding scaling issues by decoupling where possible.
This approach allows the business to quickly develop and deliver software updates. An additional benefit of these small, autonomous teams is they can make changes and deliver upgrades without interfering the other teamsâ€™ work.Â These squads or teams completely own their pieces of product, so they can deploy, change, and upgrade that piece without interrupting anything else.Â
Rapid removal of roadblocks is also key to Spotifyâ€™s successful adoption of Scrum. Spotify makes it a priority to deal with roadblocks and issues as soon as they arise, and does so by constantly monitoring possible impediments and eliminating them before they turn into issues. This allows their teams to move rapidly to achieve goals and scale up.
What you can learn from Amazon and Spotify’s agile project management
Amazon and Spotify have very different approaches as far as the adoption of Scrum is concerned. In the case of Amazon, the organisation allowed adoption to happen incrementally and at the ground level, as demand drove it. In the case of Spotify, it was a deliberate, management-sanctioned plan that led to Scrum implementation.
However, the two businesses are similar in how theyÂ use the process. Scrum is used in order to allow teams to be autonomous and self-directing. Spotifyâ€™s approach allows them to emphasise autonomous and discrete teams that work separately from others. Amazonâ€™s use of Scrum is focused on long-term, stable teams.
In addition, Amazonâ€™s practice focuses on sharing knowledge and driving better understanding through resources like training, email-based communities, and expert coaches. For Spotify, the removal of roadblocks is vital for rapid responses, product iterations, and scaling up.
How Scrum innovates the way you work
Scrum rethinks the traditional hierarchical management ideology by suggesting a flatter, more empowering working structure is better. This type of organisation can be superior because it can enable you to leverage the skills of individuals and teams while responding more dynamically and being more innovative.
Scrum teams can include a product owner, a development team, and a Scrum master. Instead of the team taking instructions from a senior manager, the Scrum team is usually self-organising and cross-functional.
This means the team chooses how they will do their work. Since theyâ€™re cross-functional, Scrum teams donâ€™t need to work with other teams and can act dynamically to achieve goals without waiting for others.
Since products are designed in an iterative and incremental way, teams have a lot of opportunities to test, take feedback into account, and engage in continuous improvement. The development team are by design small enough to stay dynamic but sizeable enough to deal with the workloads required for sprints.
Sprints are another core element of Scrum, and theyâ€™re a time-box of four weeks or less during when a useable and possibly releasable version of a product is produced. Sprints can result in a final product or be used to produce product increments rapidly.
Why the role of Scrum master is pivotal for agile working
Scrum masters play a pivotal role in any Scrum environment. They are responsible for ensuring teammates understand the goals of the agile method. The Scrum master helps team members achieve this by sharing their knowledge of Scrum theory, practices, and rules.
A secondary role of the Scrum Master is to help others outside of the team understand the usefulness of their interactions of with teamÂ members. This allows outsiders, who are within the organisation, adapt their interactions to best support the Scrum team members.
The Scrum Master is also responsible for removing impediments to the teamâ€™s progress, and they may play a significant role in the organisation by coaching and leading the organisation in Scrum adoption.
Ready to become a Scrum master and enhance the way you work?Â
If you’re keen to take the next step to improve how your team works, sign up to our Professional Scrum Master course. Presented byÂ Erwin van der Koogh,Â one of the most experienced Scrum Master trainers in the Asia-Pacific region, this course is the world premium certification for anyone wanting to master Scrum.Â