Spotify Engineering Culture - Part 2

Quick recap from part one our culture is based on agile principles all engineering happens in squads and we try to keep them loosely coupled and tightly aligned we like cross-pollination and have an internal open source model for code squads do small and frequent releases which is enabled by decoupling our self-service model minimizes the need for handoffs and we use release trains and feature toggles to get stuff into production early and often and since culture is all about the people we focus on motivation community and trust rather than structure and control that was part one and now I'd like to talk about failure our founder Daniel put it nicely we aim to make mistakes faster than anyone else the idea is to build something really cool

Spotify Engineering Culture - Part 1

One of the big success factors here at Spotify is our agile engineering culture tends to be invisible we don't notice it because it's there all the time kind of like the air we breathe but if everyone understands the culture we're more likely to be able to keep it and even strengthen it as we grow so that's the purpose of this video when our first music player was launched in 2008 we were pretty much a scrum company scrum is a well-established agile development approach and it gave us a nice team-based culture however a few years later we had grown into a bunch of teams

About Home Study

Technology and Life