{"id":103,"date":"2023-12-10T18:03:17","date_gmt":"2023-12-10T18:03:17","guid":{"rendered":"https:\/\/nextagile.ai\/blogs\/?p=103"},"modified":"2025-12-19T08:32:59","modified_gmt":"2025-12-19T08:32:59","slug":"what-is-spotify-model","status":"publish","type":"post","link":"https:\/\/nextagile.ai\/blogs\/agile\/what-is-spotify-model\/","title":{"rendered":"What Is Spotify Model In Agile? Key Elements, Structure &#038; Benefits"},"content":{"rendered":"\r\n<p>If you are looking at scaling agile in your organisation and are considering the Spotify model as one of your options , you have landed at the right place. In this blog &#8220;What Is Spotify Model In Agile?&#8221;, we will attempt to explain the basics of the model listed below and why your organization should explore it as a serious scaling approach.<\/p>\r\n\r\n\r\n\r\n<p>What is the Spotify Model?\u00a0<\/p>\r\n\r\n\r\n\r\n<p>What are the factors organisations need to consider to implement the Spotify model?<\/p>\r\n\r\n\r\n\r\n<p>What are the benefits?<\/p>\r\n\r\n\r\n\r\n<p>Does it suit your organisation?<\/p>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"History_of_Spotify_Model\"><\/span>History of Spotify Model\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2><div id=\"ez-toc-container\" class=\"ez-toc-v2_0_82_2 ez-toc-wrap-left ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 eztoc-toggle-hide-by-default' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/what-is-spotify-model\/#History_of_Spotify_Model\" >History of Spotify Model\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/what-is-spotify-model\/#What_is_the_Spotify_Model\" >What is the Spotify Model?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/what-is-spotify-model\/#Spotify_Model_Structure_And_Key_Elements\" >Spotify Model: Structure And Key Elements\u00a0<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/what-is-spotify-model\/#Squad\" >Squad<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/what-is-spotify-model\/#Tribe\" >Tribe<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/what-is-spotify-model\/#Chapter\" >Chapter<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/what-is-spotify-model\/#Guild\" >Guild<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/what-is-spotify-model\/#Benefits_Of_Spotify_Model\" >Benefits Of Spotify Model<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/nextagile.ai\/blogs\/agile\/what-is-spotify-model\/#Realisation_of_Spotify_Model\" >Realisation of Spotify Model<\/a><\/li><\/ul><\/nav><\/div>\n\r\n\r\n\r\n\r\n<p>Spotify, which is one of the biggest music streaming products, came up with a model of delivery which was customised over years according to their needs, org culture and the way they wanted to manage their teams and delivery.\u00a0<\/p>\r\n\r\n\r\n\r\n<p>Henrick Kniberg and Anders Ivarsson with the intention of showcasing how development teams are organised at Spotify, published a whitepaper on the same. And because of the model\u2019s inherent simplicity, less need for control and significantly better collaboration, a wide range of\u00a0 companies\u00a0 using Agile were attracted towards implementing Spotify and hence the model became popular.<\/p>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_is_the_Spotify_Model\"><\/span>What is the Spotify Model?<span class=\"ez-toc-section-end\"><\/span><\/h2>\r\n\r\n\r\n\r\n<p>Spotify Model is a people driven, autonomous approach for scaling agile that emphasizes the importance of culture and network. It is not a framework rather an example of how to manage and organise multiple agile teams and Spotify\u2019s view on scaling from both technical and cultural standpoint.<\/p>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Spotify_Model_Structure_And_Key_Elements\"><\/span>Spotify Model: Structure And Key Elements\u00a0<span class=\"ez-toc-section-end\"><\/span><\/h2>\r\n\r\n\r\n\r\n<p>A typical org \/ team structure in a spotify model is as depicted in the image below.<\/p>\r\n\r\n\r\n\r\n<p>Spotify model emphasises around team autonomy and simplicity and during their tenure of organizing the development, they identified certain ways to organise their teams as well.<\/p>\r\n\r\n\r\n<div class=\"wp-block-image\">\r\n<figure class=\"aligncenter\">\r\n<figure style=\"width: 512px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/benzne.com\/wp-content\/uploads\/2022\/01\/Spotify-Model-2.png\" alt=\"Team structure in spotify model\" width=\"512\" height=\"308\" title=\"\"><figcaption class=\"wp-caption-text\">Team structure in spotify model<\/figcaption><\/figure>\r\n<\/figure>\r\n<\/div>\r\n\r\n\r\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Squad\"><\/span><strong>Squad<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\r\n\r\n\r\n<div class=\"wp-block-image\">\r\n<figure class=\"alignright\">\r\n<figure style=\"width: 102px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/benzne.com\/wp-content\/uploads\/2022\/01\/Spotify-Model3.png\" alt=\"Squads in a spotify model\" width=\"102\" height=\"512\" title=\"\"><figcaption class=\"wp-caption-text\">Squads in a spotify model<\/figcaption><\/figure>\r\n<\/figure>\r\n<\/div>\r\n\r\n\r\n<p><br \/><strong>Definition :<\/strong>\u00a0The smallest unit of development, similar to a normal Scrum team\u00a0<\/p>\r\n\r\n\r\n\r\n<p><strong>Traits :<\/strong>\u00a0<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>6-9 Members team\u00a0<\/li>\r\n\r\n\r\n\r\n<li>Self Organising and Cross functional\u00a0<\/li>\r\n\r\n\r\n\r\n<li>Fully capable of delivering a piece of work\u00a0<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<p><strong>Focus :<\/strong>\u00a0One feature Area<\/p>\r\n\r\n\r\n\r\n<p><strong>Framework :<\/strong>\u00a0Team\u2019s Choice ( Scrum \/ kanban \/ scrumban etc )<\/p>\r\n\r\n\r\n\r\n<p><strong>Supported By :<\/strong>\u00a0<a href=\"https:\/\/nextagile.ai\/blogs\/agile\/what-is-agile-coaching\/\">Agile Coach<\/a> and Product Owner<\/p>\r\n\r\n\r\n\r\n<p><strong>Highlights<\/strong>:<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>A squad does not have a leader designated\u00a0<\/li>\r\n\r\n\r\n\r\n<li>Squad has full access to the management and all the support functions\u00a0<\/li>\r\n\r\n\r\n\r\n<li>They set up their own workspace based on the team\u2019s comfort<\/li>\r\n\r\n\r\n\r\n<li>Product Owner guides the squads on the priorities\u00a0<\/li>\r\n\r\n\r\n\r\n<li>10% of their work capacity goes for hack days<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Tribe\"><\/span><strong>Tribe<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\r\n\r\n\r\n<div class=\"wp-block-image\">\r\n<figure class=\"alignright\">\r\n<figure style=\"width: 266px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/benzne.com\/wp-content\/uploads\/2022\/01\/Spotify-Model4.png\" alt=\"tribe in a spotify model\" width=\"266\" height=\"337\" title=\"\"><figcaption class=\"wp-caption-text\">tribe in a spotify model<\/figcaption><\/figure>\r\n<\/figure>\r\n<\/div>\r\n\r\n\r\n<p><br \/><strong>Definition :<\/strong>\u00a0A collection\u00a0 of Squads working on one product area<\/p>\r\n\r\n\r\n\r\n<p><strong>Traits :<\/strong>\u00a0<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>100 and less membered team\u00a0<\/li>\r\n\r\n\r\n\r\n<li>Internally manage dependencies\u00a0<\/li>\r\n\r\n\r\n\r\n<li>Working on one part of the product ( Eg : Search Engine , etc )<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<p><strong>Focus :<\/strong>\u00a0One product Area \/ Module\u00a0<\/p>\r\n\r\n\r\n\r\n<p><strong>Framework :<\/strong>\u00a0Squad\u2019s Choice ( Scrum \/ kanban \/ scrumban etc )<\/p>\r\n\r\n\r\n\r\n<p><strong>Supported By :<\/strong>\u00a0Tribe Leader<\/p>\r\n\r\n\r\n\r\n<p><strong>Highlights<\/strong>:<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>Help build common alignment within squads<\/li>\r\n\r\n\r\n\r\n<li>Tribe Leader ensures all squads are well equipped with the support they need<\/li>\r\n\r\n\r\n\r\n<li>Common ceremonies like Tribe demos , hack days , knowledge sharing<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Chapter\"><\/span><strong>Chapter<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\r\n\r\n\r\n\r\n<p><strong>Definition :<\/strong>\u00a0Group of development team members with same skill set or expertise from the same Tribe<\/p>\r\n\r\n\r\n\r\n<p><strong>Traits :<\/strong>\u00a0<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>Constant collaboration on expertise , challenges\u00a0<\/li>\r\n\r\n\r\n\r\n<li>COE \/ Community structure which is self sustaining and\u00a0 promoting learnability<\/li>\r\n\r\n\r\n\r\n<li>Setting norms and guidelines within skillset<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<p><strong>Focus :<\/strong>\u00a0Same technology \/ skillset<\/p>\r\n\r\n\r\n\r\n<p><strong>Supported By :<\/strong>\u00a0Chapter Leader<\/p>\r\n\r\n\r\n\r\n<p><strong>Highlights<\/strong>:<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>Managed by a chapter lead\u00a0<\/li>\r\n\r\n\r\n\r\n<li>Frequent meetings to promote cross pollination of skillset<\/li>\r\n\r\n\r\n\r\n<li>Resolving challenges , Promoting learnability as unit<\/li>\r\n<\/ul>\r\n\r\n\r\n<div class=\"wp-block-image\">\r\n<figure class=\"aligncenter\">\r\n<figure style=\"width: 512px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/benzne.com\/wp-content\/uploads\/2022\/01\/Spotify-Model5.png\" alt=\"chapter in a spotify model\" width=\"512\" height=\"327\" title=\"\"><figcaption class=\"wp-caption-text\">chapter in a spotify model<\/figcaption><\/figure>\r\n<\/figure>\r\n<\/div>\r\n\r\n\r\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Guild\"><\/span><strong>Guild<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\r\n\r\n\r\n\r\n<p><strong>Definition :<\/strong>\u00a0A group of people who share a common passion \/ interest ( Eg : Performance , Testing etc )<\/p>\r\n\r\n\r\n\r\n<p><strong>Traits :<\/strong>\u00a0<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>Community of interest<\/li>\r\n\r\n\r\n\r\n<li>Share coding practices, knowledge and new learnings , tools etc<\/li>\r\n\r\n\r\n\r\n<li>Guilds cut across an organisations \/ multiple tribes \/ squads<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<p><strong>Focus :<\/strong>\u00a0Same Interest \/ Passion\u00a0<\/p>\r\n\r\n\r\n\r\n<p><strong>Supported By :<\/strong>\u00a0Guild Leader ( optional )<\/p>\r\n\r\n\r\n<div class=\"wp-block-image\">\r\n<figure class=\"aligncenter\">\r\n<figure style=\"width: 512px\" class=\"wp-caption alignnone\"><img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/benzne.com\/wp-content\/uploads\/2022\/01\/Spotify-Model6.png\" alt=\"guild in a spotify model\" width=\"512\" height=\"274\" title=\"\"><figcaption class=\"wp-caption-text\">guild in a spotify model<\/figcaption><\/figure>\r\n<\/figure>\r\n<\/div>\r\n\r\n\r\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Benefits_Of_Spotify_Model\"><\/span>Benefits Of Spotify Model<span class=\"ez-toc-section-end\"><\/span><\/h2>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li><strong>Less Control promotes autonomy and productivity<\/strong>\u00a0\u2013 Squads are responsible for their own decision and the way they choose their working model. This promotes self management and builds good team rapport and trust. Also Squads are created keeping dependencies in mind and since they are mostly independent, they tend to have faster release cycles\u00a0<\/li>\r\n\r\n\r\n\r\n<li><strong>Encourages teamwork and collaboration over silo working<\/strong>\u00a0\u2013 Spotify Model is a matrix type model i.e it is structured around people and collaboration. This model allows everyone to communicate with anyone in the system, helping solve dependencies or problems. At various levels, i.e be it squads, tribes or chapters, this model encourages a sense of belonging and collaborating effectively to make better decisions among people.<\/li>\r\n\r\n\r\n\r\n<li><strong>Shared Goals helps create a Fail Safe environment helping teams experiment more<\/strong>\u00a0\u2013 No managers and informal communications as well as team structure ( ownership and accountability ) enables a highly effective Fail Safe environment. Also teams and individuals spare 10% of their productive time in hack days \/ projects. These aspects of spotify ensures there is enough room for continuous experiments.<\/li>\r\n\r\n\r\n\r\n<li><strong>No Formal Ceremony or Process \u2013<\/strong>\u00a0Spotify lets the teams decide their own framework for their delivery it does not have a set template of ceremonies to be followed, rather it counts on the teams to align with other teams to become more productive<\/li>\r\n<\/ul>\r\n\r\n\r\n\r\n<p><strong>Faster Dependency solving<\/strong> \u2013 The model designed keeping in mind the teams at the center, promotes faster problem solving and collaboration by avoiding formal approvals, calls which usually is the case with other scaling methods.<\/p>\r\n<blockquote>\r\n<p>Partner with the leading <a href=\"https:\/\/nextagile.ai\/agile-consulting-services\/\" target=\"_blank\" rel=\"noopener\">agile consulting company<\/a> for tailored solutions and expert guidance. Transform your business with agility. Explore our offerings now.<\/p>\r\n<\/blockquote>\r\n\r\n\r\n\r\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Realisation_of_Spotify_Model\"><\/span>Realisation of Spotify Model<span class=\"ez-toc-section-end\"><\/span><\/h2>\r\n\r\n\r\n\r\n<p>Quite often in any <a href=\"https:\/\/nextagile.ai\/blogs\/agile-transformation\/agile-transformation-journey\/\">agile transformation<\/a> or any framework implementation, teams tend to become a slave of the process than enjoying \/ realising the essense of what is being implemented. Below are a few points \/ aspects \/ changes which an organisation should realise when spotify is being implemented.\u00a0<\/p>\r\n\r\n\r\n\r\n<p>Real value of Spotify\u2019s model was its engineering and product development culture which Spotify created for it\u2019s fast growing , motivated decoupled agile teams. Below are a few cultural aspects which a team or a company must realise \/ consider\u00a0 before implementing Spotify<\/p>\r\n\r\n\r\n\r\n<ul class=\"wp-block-list\">\r\n<li>\r\n<ul>\r\n<li><strong>Productivity = Environment and Motivation<\/strong>\u00a0\u2013 Productivity of the teams is very much dependent on the Motivation and Environment they work in. ( Spotify\u2019s productivity formula = Effort * Competence * Environment * Motivation ). To create highly productive teams, appropriate environment has to be maintained\u00a0<\/li>\r\n<li><strong>Healthy Balance of Autonomy and Alignment\u00a0<\/strong>\u2013 Spotify pushes for a healthy balance between Central Alignment ( product vision \/ goals etc ) and team autonomy ( Self sufficient teams ). For instance, managers will tell the teams what to do but not interfere in how to do and when to do<\/li>\r\n<li><strong>System Changes \u2013\u00a0<\/strong>Spotify changed their architecture to support decoupled , faster and easier releases to support more and frequent production releases. Appropriate system changes might have to be in place to support the model<\/li>\r\n<li><strong>Trusting People Over Commanding<\/strong>\u00a0\u2013 Spotify\u2019s immense trust in their employees helped them build a model which led to complete autonomy of the teams and thus the model itself. A culture of trust and belief is a strong need to support spotify<\/li>\r\n<li><strong>Managers to Servant Leadership<\/strong>\u00a0\u2013 Management to align towards how they can be of help rather than asking what they want to what the teams are doing.\u00a0<\/li>\r\n<li><strong>Continuous Improvement Culture<\/strong>\u00a0\u2013 Teams constantly working on how to make their lives better and easier. Shift of thought process where teams are deciding what best works for them without a manager telling. Setting up dedicated people \/ resource to help teams get to their absolute best\u00a0<\/li>\r\n<li><strong>Experiment and Fail Safe Environment<\/strong>: Spotify strongly believed in encouraging their teams to generate ideas and run experiments to measure their results. Which helped them imbibe a culture of maximising value from their experiments by tweaking their approach.<\/li>\r\n<\/ul>\r\nWith this, our blog on \u201cIntroduction to Spotify Model\u201d\u00a0 comes to an end. Please reach out to us at \u201c<a href=\"mailto:consult@nextagile.ai\">consult@nextagile.ai<\/a>\u201d for any feedback , suggestions or questions. Sujith S. Agile Consultant \u2013 NextAgile<\/li>\r\n<\/ul>\r\n","protected":false},"excerpt":{"rendered":"<p>If you are looking at scaling agile in your organisation and are considering the Spotify model as one of your options , you have landed at the right place. In this blog &#8220;What Is Spotify Model In Agile?&#8221;, we will attempt to explain the basics of the model listed below and why your organization should&#8230;<\/p>\n","protected":false},"author":2,"featured_media":4196,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"content-type":"","footnotes":""},"categories":[2],"tags":[5,7,6],"class_list":["post-103","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agile","tag-agile","tag-project-management","tag-scrum"],"_links":{"self":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/103","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/comments?post=103"}],"version-history":[{"count":10,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/103\/revisions"}],"predecessor-version":[{"id":5040,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/posts\/103\/revisions\/5040"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media\/4196"}],"wp:attachment":[{"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/media?parent=103"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/categories?post=103"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nextagile.ai\/blogs\/wp-json\/wp\/v2\/tags?post=103"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}