Module - Design, Development and Creativity
Class or Article - Article
Lesson or Name - Henrik Kniberg and Anders Ivarsson. Scaling agile @ spotify with tribes, squads, chapters & guilds. White Paper, 2012.
Additional Info - 1-14
Precis
In this article "Scaling agile @ spotify with tribes, squads, chapters & guilds" by Kniberg and Ivarsson the reader is presented with the application of Agile in to the business of Spotify. Kniberg and Ivarsson bring the reader on a journey through the article highlighting the different elements that make up their introduction and application of Agile, in the firm of Tribes. Tribes consist of a breakdown of teams called squads, chapters and guilds. A squad is the most basic until, they are a core team who build and deploy enhancements within Spotify. The unique thing about squads is they are responsible for different components within the organisation and applications itself. A squad is headed up by a product owner. Within each tribe can be multiple squads. From squads comes chapters that are the accumulation of people with similar skills working on different elements of the application in different teams. Then we are presented the idea of a guild. A guild is a community of interest group who share knowledge and tools. The one thing I find great about this read is that Spotify have not overlooked the architecture component of their work, something that Agile as a whole fails to address. Spotify have implemented System Owners, a pair of colleagues forming a Development and Operations partnership. Kniberg and Ivarsson accept that this system is perfect and that a they grow they will encounter problems, but for now based in their retrospectives and surveys they are on track and it is something that the business feel is working well.
Relflection
I really enjoyed this article and it is something in which I believe all companies could aspire to implement in a form that works for themselves. I believe all organisations have moment of Agile, whether it be starting a project, developing it or delivering it. It is when all people are focused on the outcome and not the individual parts is when work is truly achieved. A sense of slow is found and people work as one to deliver the end game. All organisations perform some for or agile, but using agile is not a one size fits all and that is why I feel spotifys' approach to taking it and tweaking ti to suit their business is a step in the right direction of developing this methodology.
For some large organisations this is hard to see but organisation that are set up to succeeded, know where they are going and what people are doing will in the long term scale better and provide a better service. This is why I really like the Spotify Agile approach.
Should I ever get the opportunity to implement an agile approach I feel i will take Spotifys approach and implement the pieces that work for me and the company and enable the team to work and structure themselves in a way that delivers the outcomes.
Quotes
Additional Info - 1-14
Precis
In this article "Scaling agile @ spotify with tribes, squads, chapters & guilds" by Kniberg and Ivarsson the reader is presented with the application of Agile in to the business of Spotify. Kniberg and Ivarsson bring the reader on a journey through the article highlighting the different elements that make up their introduction and application of Agile, in the firm of Tribes. Tribes consist of a breakdown of teams called squads, chapters and guilds. A squad is the most basic until, they are a core team who build and deploy enhancements within Spotify. The unique thing about squads is they are responsible for different components within the organisation and applications itself. A squad is headed up by a product owner. Within each tribe can be multiple squads. From squads comes chapters that are the accumulation of people with similar skills working on different elements of the application in different teams. Then we are presented the idea of a guild. A guild is a community of interest group who share knowledge and tools. The one thing I find great about this read is that Spotify have not overlooked the architecture component of their work, something that Agile as a whole fails to address. Spotify have implemented System Owners, a pair of colleagues forming a Development and Operations partnership. Kniberg and Ivarsson accept that this system is perfect and that a they grow they will encounter problems, but for now based in their retrospectives and surveys they are on track and it is something that the business feel is working well.
Relflection
I really enjoyed this article and it is something in which I believe all companies could aspire to implement in a form that works for themselves. I believe all organisations have moment of Agile, whether it be starting a project, developing it or delivering it. It is when all people are focused on the outcome and not the individual parts is when work is truly achieved. A sense of slow is found and people work as one to deliver the end game. All organisations perform some for or agile, but using agile is not a one size fits all and that is why I feel spotifys' approach to taking it and tweaking ti to suit their business is a step in the right direction of developing this methodology.
For some large organisations this is hard to see but organisation that are set up to succeeded, know where they are going and what people are doing will in the long term scale better and provide a better service. This is why I really like the Spotify Agile approach.
Should I ever get the opportunity to implement an agile approach I feel i will take Spotifys approach and implement the pieces that work for me and the company and enable the team to work and structure themselves in a way that delivers the outcomes.
Quotes
Comments
Post a Comment