I would be so curious to know how this whole process evolved from 2014 and mostly how this survived the pandemic and remote work. Does this intensely collaborative approach (closely working together in rooms with whiteboards instead of walls) work well with people working remote? Will there be a part 3?
Great question, would love to hear an update from the current teams at Spotify. One thing is for sure: McKinsey sold this "spotify model" to companies as key to the gates of eternal prosperity. (barf) Now banks, insurance, insurane and pharma companies use it. Companies that have nothing in common whatsoever with Scandinavian IT company developing a streaming software. I love this model, but anyone who uses it exactly like this is going to fail. And guess what, Spotify is (obviously) has moved pretty far from this model. Because they adopted.
FANTASTIC! It literally paints a pretty picture on how Spotify managed to achieve greatness: the platform is a direct reflection of the people maintaining it! KUDOS to Spotify!
I think the concept is fantastic, and it did inspired a lot of organization to adopt this agile model. However not so many of them having a good understanding of the various factors that construct it and get into their expectation by doing this approach.
How are you adjusting your in-person collaboration methods to social distancing in the pandemic environment? Was listening to Sam Harris interview Matt Mullenwegg of Automattic about distributed collaboration and thought back to your model and how awesome it seemed at the time.
Nice explanation. Good for a change out the 10 implementations in this model how many passed would be a good source of inspiration to follow. Really big complex projects would be a good focus for the statistics.
Hi Henrik, this is an awesome video, very informative and inspiring. Thanks! A great solution to lot of cultural problems I have seen in many companies with leadership struggling to solve it. Question: How do you ensure visibility of work across multiple squads within the same flavor of squads to avoid duplicate work and/or to ensure pairing related
In the comments of the video I saw that the author wrote "Many people ask which tools were used. I hand-drew everything in ArtRage using a Wacom drawing tablet, and recorded the drawing and speaking using ScreenFlow."
Release trains - So....You are not done with your feature but it still must be deployed because unmerged code is code debt? But if every squad has there own area?? And via a toggle you hide the functionality and still use the old code. So you cannot change the old code when doing a feature but must create new code which will coexist with the old....Seems cumbersome... And so you carry this code debt around....until when? When you have rolled out to all people and then you remove the old code - risking errors again which are then rolled out to everybody?
I'm having trouble visualizing this. Our 505 branch is being followed by a 506. I can't imagine how to keep 505 working and also "release" 506. perhaps it's because we aren't building new features, but enhancing existing ones. So how to do this? Do you fill the code up with if statements? Or what?
7:15 If I were part of that 4%, I would be hesitant to reply to that email. Employee satisfaction surveys are anonymous for a reason. I don't want to risk my job by telling my manager(s) that I'm unhappy. And I'd be more likely to lie on the next survey.
Yup. To paint an extreme, dark picture: Say 4 of 20 are dissatisfied; so satisfaction is 80%. The 4 speak to HR, 'doxxing' themselves. Then HR makes their work difficult and 2 of them resign. Now you have 2 of 18 being dissatisfied; satisfaction is raised to 88%.
Haha you're grossly misunderstanding the point the video was making. Servant leadership is when you listen to feedback and improve things. What idiot manager would accept feedback and then create problems for the messenger instead of fixing the fixable causes?
I don't get why the Scrum Team is renamed to Autonomous Squad. There does not seem to be any difference. Aren't Scrum Teams autonomous? Is it because there is no PO to influence the team? Or is it because you want to change enough to justify calling it "Spotify model" :)
@@henrikkniberg Any video / blog entry on how the change looks like? What is the most important part which has changed and why? This would be a very interesting info for all of us who try to lift product teams out of the water. Thanks a lot in advance.
@@henrikkniberg We would love to see a new video Henrik on your perspective on the changes that you've experienced - "Especially" with the stay-at-home 2020/2021 situation. What would it take for us to raise the priority of this request in your backlog? :)
If only Spotify wasn't buggy 😅. Podcasts are still super glitchy, sometimes search just doesn't work. Shit like that is super frustrating after all these years
