Eliani RamosVice President| PMI-SCJoinville, Sc, Brazil
Have you implemented the Spotify organisation structure? Which roles do you have in the squads? Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Hi Eliani - Are you referring to their SAFe implementation? From what I understand, they are very mature with their SAFe state. I'd be interested to hear about a successful mirror of their configuration.
...
1 reply by Eliani Ramos
Feb 17, 2018 9:24 AM
Eliani Ramos
...
Hi, thank you for the answer! No, I'm not talking about SAFe. We implemented the Spotify Organisation Structure 2 years ago.
I would like to know if anyone had any experience to share.
I wrote an article about this, but is in portuguese, here: https://www.linkedin.com/feed/update/urn:l...55445731246080/
I had never looked into this, Eliani - and having just read up on it, it looks to be very interesting.
While we do provide a lot of autonomy to our high-skill team members, one of them is often a process lead or a solution lead - this is to minimise the number of communication channels.
We do have informal communication and collaboration options that align to the Guilds concept. We do have teams aligned into what the Spotify structure defines as Tribes and Chapters (the primary difference being the presence of an Architect - as above - for each Tribe and Guild).
The formal structure would work for a projectised organisation whose delivery is internal. It would not work that well for us as our delivery is external - even if we have informally adopted a lot of these principles.
...
1 reply by Eliani Ramos
Feb 19, 2018 9:10 AM
Eliani Ramos
...
Thank you por your answer. Wich other challenges do you think we have for external deliveries?
Looks good. It's basically Scrum with rope. Saving Changes...
Eliani RamosVice President| PMI-SCJoinville, Sc, Brazil
Feb 16, 2018 3:43 PM
Replying to Drew Craig
...
Hi Eliani - Are you referring to their SAFe implementation? From what I understand, they are very mature with their SAFe state. I'd be interested to hear about a successful mirror of their configuration.
Hi, thank you for the answer! No, I'm not talking about SAFe. We implemented the Spotify Organisation Structure 2 years ago.
I would like to know if anyone had any experience to share.
I wrote an article about this, but is in portuguese, here: https://www.linkedin.com/feed/update/urn:l...55445731246080/ Saving Changes...
Eliani RamosVice President| PMI-SCJoinville, Sc, Brazil
Feb 16, 2018 9:29 PM
Replying to Karan Shah
...
I had never looked into this, Eliani - and having just read up on it, it looks to be very interesting.
While we do provide a lot of autonomy to our high-skill team members, one of them is often a process lead or a solution lead - this is to minimise the number of communication channels.
We do have informal communication and collaboration options that align to the Guilds concept. We do have teams aligned into what the Spotify structure defines as Tribes and Chapters (the primary difference being the presence of an Architect - as above - for each Tribe and Guild).
The formal structure would work for a projectised organisation whose delivery is internal. It would not work that well for us as our delivery is external - even if we have informally adopted a lot of these principles.
Thank you por your answer. Wich other challenges do you think we have for external deliveries?
...
1 reply by Karan Shah
Feb 20, 2018 10:30 PM
Karan Shah
...
Primary challenges are around co-locating team members. There are myriad issues with global mobility, commitment to a contract, cost allocation, margin calculation, cultural sensitivities (geographical and organisational).
These are not show-stopper issues - but is the long hard road worth it? Especially as the principles, themselves, have been adopted. Would it need to be adopted formally as a structure?
Saving Changes...
Eliani RamosVice President| PMI-SCJoinville, Sc, Brazil
Feb 16, 2018 9:35 PM
Replying to Kevin Drake
...
This is very new to me, interesting. got something to read then this weekend
This structure is gain a lot of organizations around the World. In my opinion, we need maturity scrum teams to succeed in its implementation. Saving Changes...
Thank you por your answer. Wich other challenges do you think we have for external deliveries?
Primary challenges are around co-locating team members. There are myriad issues with global mobility, commitment to a contract, cost allocation, margin calculation, cultural sensitivities (geographical and organisational).
These are not show-stopper issues - but is the long hard road worth it? Especially as the principles, themselves, have been adopted. Would it need to be adopted formally as a structure?
...
1 reply by Eliani Ramos
Feb 21, 2018 12:14 PM
Eliani Ramos
...
This is a good question! Here, we have another structure to software implementation projects those have this challenges.
We've adopted spotify structure only to software develpment teams (new products, innovation, maintenance and customer support). These teams are in the same place. Our squads are responsible for everything: development, maintain, customer support. In our structure we have only one leader do response all of it. He has the "power" to asignee his resources from innovation to maintenance, or from maintenance to customer support as his needs.
Saving Changes...
Eliani RamosVice President| PMI-SCJoinville, Sc, Brazil
Feb 20, 2018 10:30 PM
Replying to Karan Shah
...
Primary challenges are around co-locating team members. There are myriad issues with global mobility, commitment to a contract, cost allocation, margin calculation, cultural sensitivities (geographical and organisational).
These are not show-stopper issues - but is the long hard road worth it? Especially as the principles, themselves, have been adopted. Would it need to be adopted formally as a structure?
This is a good question! Here, we have another structure to software implementation projects those have this challenges.
We've adopted spotify structure only to software develpment teams (new products, innovation, maintenance and customer support). These teams are in the same place. Our squads are responsible for everything: development, maintain, customer support. In our structure we have only one leader do response all of it. He has the "power" to asignee his resources from innovation to maintenance, or from maintenance to customer support as his needs. Saving Changes...
