This dissertation examines how integrating agile methodologies with design principles drives product success, using Spotify as a case study. Spotify’s approach blends user-centered design with agile development, enabling rapid iteration, cross-functional collaboration and high-quality features like Discover Weekly. The study shows that this unified methodology resolves common challenges, such as stakeholder alignment and balancing user needs with business goals. It offers a practical blueprint for organizations seeking competitive advantage in digital markets.
Table of Contents
Chapter 1: Introduction
1.1 Spotify’s Profile
1.2 Introduction to Design Thinking principles
1.3 Brief Intro to Agility Frameworks
Chapter 2: Literature Review
2.1 Theoretical Foundations of Design Thinking and Agile Integration
2.2 Contemporary Research on Integration Patterns and Effectiveness
2.3 Organizational Scaling Challenges and Autonomous Team Structures
2.4 Methodological Approaches and Research Limitations
2.5 Spotify as Industry Exemplar: Successes and Critical Assessments
2.6 Critical Analysis and Research Gaps
2.7 Synthesis: Towards a Comprehensive Integration Framework
Chapter 3: Methodology
3.1 Research Design and Philosophical Approach
3.2 Data Collection Strategy
3.3 Data Integration and Analysis
3.4 QualityAssurance and Limitations
Chapter 4: Findings
4.1 Design Thinking Strategies by Spotify
4.2 Quantifiable Business Impact
4.3 Agile Management Model at Spotify
4.4 Exploring the Role of Design Thinking in Spotify’s Agile Squad Framework
Chapter 5: Discussion
5.1 Theoretical Implications
5.2 Contextual Factors and Boundary Conditions
5.3 Practical ImplicationsforOrganizations
5.4 Alternative Explanations and Limitations
5.5 Future Research Directions
Chapter 6: Conclusion
References
Acknowledgment
I would like to express my deepest gratitude to my supervisor, Danielle Badu, for her invaluable guidance, support and encouragement throughout the course of this dissertation. Her insight and feedback have been instrumental in shaping mywork and helping me grow academically.
I am also grateful to Warwick Business School for providing me with an enriching academic environment, excellent resources and the opportunity to learn from world-class faculty. My time here has been both intellectually rewarding and personally transformative.
Finally, I would like to extend my heartfelt thanks to my parents, whose unwavering support and sacrifice have given me the opportunity to pursue my studies at Warwick. Their belief in me has been the foundation ofthisjourney and I am deeply indebted to them.
Abstract
This dissertation examines how integrating agile methodologies with design principles drives product success, using Spotify as a case study. Spotify’s approach blends user-centered design with agile development, enabling rapid iteration, cross-functional collaboration and high-quality features like Discover Weekly. The study shows that this unified methodology resolves common challenges, such as stakeholder alignment and balancing user needs with business goals. It offers a practical blueprint for organizations seeking competitive advantage in digital markets.
1. Introduction
In today’s dynamic business environment organizations face constant pressure to innovate rapidly while remaining closely attuned to user needs. Traditional linear development approaches are no longer sufficient, as market demands evolve at unprecedented speed. Consequently, companies are increasingly adopting agile methodologies to enhance flexibility, responsiveness and iterative delivery. However, being agile alone is not enough; organizations must also embed user-centric practices into their development processes to ensure products resonate with target audiences. Integrating design thinking with agile methodologies has emerged as a promising approach, enabling teams to combine human-centred ideation with rapid implementation cycles.
Spotify exemplifies the successful application of this embedded integration model. As a leading music streaming platform, Spotify continuously adapts its product offerings based on deep user insights, testing new features iteratively while maintaining high development speed. Its organizational practices, including autonomous squads and cross-functional collaboration, showcase how design thinking and agile principles can be harmonized to achieve both innovation and scalability.
1.1 Spotify’s Profile
Spotify is a streaming platform based in Sweden that allows users to enjoy music, podcasts and other types of audio content. The company was founded by Daniel Ek and Martin Lorentzon in 2006 in Stockholm (Kniberg and Ivarsson, 2012) & its services were officially launched in 2008. Spotify operates on a freemium model, which means that basic features can be obtained for free, but if a user prefers additional features such as no ads, better sound quality or the ability to download songs for offline listening, users must pay for a premium subscription (Smite, Moe, Levinta and Floryan, 2019). More than 100 million songs and several million podcasts are available worldwide on the platform allowing users to listen to music from a huge library of songs (Spotify, 2024).
Illustrations are not included in the reading sample
1.2 Introduction to Design Thinking principles
Within product management and development, design thinking provides a human-centered framework in which empathy, ideation and prototyping operate as essential principles guiding innovation. Empathy is considered the starting point of design thinking as it enables product managers to uncover the implicit needs, frustrations and motivations of users through qualitative research methods such as interviews, observations and journey mapping (Interaction Design Foundation, 2025). By cultivating an empathetic perspective, teams ensure that product development is grounded in user realities rather than organizational assumptions, which increases the likelihood ofdelivering meaningful solutions (HelloPM, 2021). Following this stage, ideation constitutes the divergent phase of design thinking, where creativity and collaboration are emphasized to generate a wide range of potential solutions. In this process, product teams are encouraged to defer judgment and think expansively, using structured techniques such as brainstorming, sketching or design sprints to reframe challenges and explore unconventional ideas (Studiowhy, 2023). The aim is to expand the solution space before narrowing it during later stages of testing. Prototyping, which follows ideation, is integral to the iterative nature of design thinking. Recent scholarship highlights how this process equips organizations to navigate complex and “wicked” problems by balancing desirability, feasibility and viability in product development (Dragicevic et al., 2022). Thus, when applied to product management, design thinking ensures that innovation emerges not from abstract strategy alone but from a continuous cycle of understanding users, generating ideas and testing solutions, making it a robust methodology for creating products that resonate with users while remaining adaptable to changing market conditions (Interaction Design Foundation, 2025).
Illustrations are not included in the reading sample
Figure 2 Basic Design Thinking Process following PRISMA 2020 guidelines (Page et al., 2021)
1.3 Brief Intro to Agility Frameworks:
Agile methodologies have transformed the way organizations approach product development in an era marked by rapid technological change and evolving customer expectations. Traditional project management models, such as the Waterfall approach, rely on sequential phases and rigid planning often struggling to adapt to shifting market conditions. (Adenowo & Adenowo, 2013) In contrast, agile emphasizes flexibility, iterative delivery and responsiveness, enabling teams to continuously refine products based on feedback. Central to agile are principles such as valuing individuals and interactions over processes and tools, prioritizing working solutions over exhaustive documentation and responding to change rather than strictly following a plan (Beck et al.,2001).
Agile frameworks, including Scrum, Kanban and Extreme Programming (XP), provide structured approaches to implement these principles. Scrum, for instance organizes work into time-boxed sprints, promotes cross-functional team collaboration and encourages regular reflection and adaptation. By breaking work into smaller increments and integrating continuous feedback loops, agile reduces risk, accelerates value delivery and fosters closer alignment with stakeholder needs. (Schwaber, K.1997)
In today’s competitive landscape, adopting agile methodologies is not limited to software development but extends to diverse industries aiming to increase efficiency, enhance customer satisfaction and drive innovation. Its focus on adaptability, collaboration and iterative learning makes agile a critical capability for organizations seeking sustainable success in dynamic environments.
2. Literature review
2.1 Theoretical Foundations of Design Thinking and Agile Integration
Design thinking and agile methods originate from distinct but complementary innovation frameworks. Design thinking is a human-centred approach that balances user needs, technical feasibility and business viability (Brown, 2019). It typically progresses through three stages: inspiration, ideation and implementation, emphasizing user understanding, solution creation and iterative testing. Liedtka (2018) highlights that this structured process helps organizations overcome mental barriers and become comfortable with experimentation.
Agile methodologies, by contrast, emerged from Beck et al.’s (2001) principles prioritising “people and interactions over processes and tools” and “responding to change over following a plan.” Serrador and Pinto (2015) demonstrated that agile methods increase project success rates, particularly in maintaining stakeholder satisfaction.
The integration potential lies in their complementary strengths: design thinking answers “what” and “why” questions by uncovering user needs, while agile addresses “how” and “when” questions through structured implementation (Pereira and Russo, 2018). Dell’Era et al. (2025) analysed 221 innovation projects and identified six sets of design thinking practices that vary according to project goals and uncertainty, indicating that successful integration depends on context-specific adaptation.
2.2 Contemporary Research on Integration Patterns and Effectiveness
Integration patterns refer to different strategies for combining two or more methodologies, frameworks, or approaches to achieve better outcomes than using either method in isolation. (Kim, Leithinger & Ishii, 2008). Recent studies identify three main integration patterns. Parizi et al. (2022) reviewed 127 papersfrom 2010-2021 and found:
1. Sequential integration: design thinking followed by agile.
2. Parallel integration: both approaches run simultaneously.
3. Embedded integration: design thinking techniques are embedded within agile activities. Embedded integration was shown to be the most effective in agile organisations, combining the methods rather than merely sequencing them. Pereira and Russo (2018) reviewed 29 studies and concluded that integrated models enhance collaboration between end users and development teams, improving software quality and usability (p.778). Combining ISO-based design thinking approaches with Scrum throughout the development cycle appears most effective.
However, Grashiller et al. (2017) proposed “Empagile,” which fuses design thinking’s understand- create-test phases with Scrum’s delivery framework. Eight months of industrial testing produced superior outcomes compared to traditional sequential approaches, suggesting that novel integration methods may outperform established patterns when properly implemented.
2.3 Organizational Scaling Challenges and Autonomous Team Structures
Scaling design thinking-agile integration while maintaining organizational alignment is challenging. Spotify is a widely documented example. Kniberg and Ivarsson (2012) introduced the Squad model which is an agile methodology first introduced by Spotify, emphasizing “autonomy with alignment” and enabling growth from 30 to over 250 engineers without losing startup agility. Their “Think it, build it, ship it, tweak it” methodology combines rapid prototyping with agile delivery.
Smite et al. (2023) highlighted that Spotify maintains autonomy through collective workgroups and decentralized authority demonstrating that scaled autonomy requires structured decision-making rather than leading to disorder. Salameh and Bass (2018) examined Squad Model implementation over 21 months, identifying tensions between team-level user-centered decisions and organizational alignment. Their findings emphasise that implementation complexity extends beyond the structural model itself.
2.4 Methodological Approaches and Research Limitations
Research on the integration of design thinking and agile methodologies uses diverse approaches, each with its own benefits and drawbacks. Quantitative studies, such as those by Dell'Era et al. (2025) and Serrador and Pinto (2015), provide statistical evidence and high generalizability, but they often lack the detailed context of how these methods are actually implemented. For example, the study by Dell'Era et al. analyzed 221 innovation projects to identify six sets of design thinking practices that vary based on project goals. Serrador and Pinto's research on over 1,000 projects showed that agile methods can improve project success rates and stakeholder satisfaction.
In contrast, qualitative studies, like those by Salameh and Bass (2018) and Smite et al. (2023), offer a rich, contextual understanding of these processes but have limited generalizability. Salameh and Bass conducted a longitudinal case study on Spotify's Squad Model to highlight the tensions between team-level decisions and organizational alignment. Similarly, Smite et al.'s work on Spotify demonstrated how scaled autonomy requires structured decision making.
Mixed methods approach show promise for capturing integration complexity. Kolenda and Savage (2019) proposed a “simultaneous triangulation” methodology combining diary studies with behavioural tracking, enabling validation of design decisions through concurrent quantitative and qualitative data. Such approaches bridge traditional research gaps by connecting user insights with agile cycles.
2.5 Spotify as Industry Exemplar: Successes and Critical Assessments
Spotify is the most extensively documented case of design thinking-agile integration (Signoretti, 2020). The DIBB framework (Data-Insights-Beliefs-Bets) exemplifies systematic integration of user research with strategic decision-making (Kniberg, 2016). Hording et al. (2019) describe comprehensive user research practices that go beyond demographics to include attitudes and context through “learning by doing” workshops.
However, implementation challenges remain. Lee (2020) notes that the squad model later discussed in this research was often aspirational rather than fully implemented. Sundén (as cited in Carroll et al., 2023) confirms that even documented practices were not fully adopted. Carroll et al. (2023) further demonstrate that focusing on metrics without sustainable practices can undermine transformation efforts, highlighting the complexity of large-scale agile implementation.
2.6 Critical Analysis and Research Gaps
Despite extensive literature on these topics, the gaps in them limit understanding of design thinking-agile integration effectiveness. Few studies like Kim, Leithinger and Ishii (2008) use experimental designs to establish causal relationships between specific integration practices and performance outcomes while existing research relies heavily on case studies and observational methods.
Geographical and cultural contexts remain underexplored, as most studies reflect Western technology companies. Additionally, standardized methods to measure design thinking effectiveness are lacking, hindering cross-organizational comparisons and evidence-based optimization of integration approaches.
2.7 Synthesis: Towards a Comprehensive Integration Framework
Effective design thinking-agile integration requires cultural transformation beyond adopting new methods. Spotify’s experience indicates that structural innovations like the Squad Model succeed only when supported by psychological safety, user focus and a learning orientation. (Smite, D 2020) A study by Ranchber, S. (2018) suggests three complementary mechanisms for successful integration: temporal complementarity through alternating expansion-contraction phases, knowledge complementarity through combining diverse insights and capability complementarity through enhanced sensing and response abilities.
Current research positions design thinking-agile integration as theoretically sound and practically promising with Spotify as a benchmark. Nevertheless, research gaps exist regarding causal relationships, measurement frameworks, cultural generalizability and long-term sustainability. Addressing these gaps will guide the development of optimal integration approaches applicable across diverse organizational contexts.
3. Methodology
3.1 Research Design and Philosophical Approach
This study employed a mixed-methods secondary research design combining comprehensive literature analysis with matrix chart evaluation to examine Spotify's integration of design thinking with agile methodologies. The research was positioned as an instrumental case study designed to provide insights applicable to other organizations seeking to integrate design thinking principles within agile frameworks rather than merely describing Spotify's specific practices. The research methodology was grounded in a practical approach that combined the analysis of organizational documents with systematic measurement of business results. This approach emphasized practical usefulness over strict adherence to a single methodology, acknowledging that complex organizational change requires examining the situation from multiple angles (Creswell & Plano Clark, 2017). PRISMAflowcharts were used to clearly map out the research processes and workflow structures, making the methodology more transparent and allowing others to replicate the study (Page et al., 2021).
Illustrations are not included in the reading sample
Figure 3: Mixed-Methods Case Study Design Structure
3.2 Data Collection Strategy
3.2.1 Literature Analysis Component: The literature analysis involved systematic examination of secondary sources published between 2015-2025, accessed through Business Source Premier, Academic Search Complete and Google Scholar databases. Search strategies employed targeted Boolean combinations of "Spotify," "design thinking," "agile methodologies," "organizational innovation," and "digital transformation."
Inclusion criteria required sources that specifically addressed Spotify's organizational practices, design thinking integration or agile implementation strategies with documented business outcomes. Exclusion criteria eliminated purely technical documentation focused exclusively on music streaming technology rather than organizational methodologies, opinion pieces without empirical foundation and studies lacking methodological transparency.
The systematic selection process followed PRISMA guidelines, beginning with initial database searches yielding comprehensive results, followed by duplicate removal, title and abstract screening, full-text assessment for eligibility and final inclusion based on quality and relevance criteria. Quality assessment considered source credibility, methodological foundations of original studies and direct relevance to research objectives.
3.2.2 Matrix Chart Analysis Framework: The matrix analysis employed framework analysis methodology (Ritchie & Spencer, 1994) to systematically evaluate relationships between Spotify's design thinking principles and corresponding business impacts. The matrix structure later presented in findings positioned design thinking principles as rows (empathy, ideation, experimentation, iteration and collaboration) and business impact categories as columns (innovation velocity, user satisfaction organizational culture, market responsiveness and competitive advantage).
Matrix analysis required systematic research of secondary data sources to identify specific instances where design thinking principles demonstrated correlation with measurable business outcomes. Each cell in the matrix required supporting evidence from multiple sources to establish credible links between design thinking principles and their impacts. The strength ofthis evidence was categorized based on the quality of sources and how consistently findings appeared across different references.
3.3 Data Integration and Analysis
Integration of literature findings with matrix analysis employed thematic synthesis (Thomas & Harden, 2008) to develop comprehensive understanding of Spotify's methodological approach. The analytical process followed iterative refinement, where initial matrix entries underwent review, validation against additional sources and adjustment based on evidence strength and consistency across multiple references (Miles et al., 2020).
The literature analysis provided theoretical foundations while the matrix evaluation revealed implementation patterns and business applications. Cross-validation compared literature themes with matrix patterns, ensuring consistency between academic findings and documented business implementations. Discrepancies were resolved through cross-referencing additional evidence sources and systematic review of conflicting interpretations. The framework analysis approach enabled systematic organization of complex data relationships while maintaining analytical rigor (Better Evaluation, 2024). PRISMA process diagrams supported this analysis by illustrating workflows for data categorization, evidence validation and matrix population procedures, ensuring transparent documentation of analytical decision-making processes.
3.4 Quality Assurance and Limitations
Methodological rigor was maintained through systematic source triangulation, requiring multiple independent sources to substantiate key findings. The framework matrix approach provided structured validation of relationships between design thinking principles and business outcomes, with evidence strength explicitly documented for each matrix cell.
However, the exclusive reliance on secondary research sources presented inherent limitations including potential publication bias toward successful implementations, temporal constraints of available data and inability to gather primary insights from Spotify employees. The methodology could not address proprietary organizational practices not documented in public sources, potentially limiting comprehensiveness offindings.
Additionally, the case study approach, while providing detailed insights into Spotify's specific practices, may limit generalizability to organizations operating in different industries or cultural contexts (Flyvbjerg, 2006). The research findings were synthesized into a practical framework enabling other organizations to apply Spotify's integration approach within their specific contexts, acknowledging these methodological constraints while maximizing the utility of available secondary data sources.
4. Findings
4.1 Design Thinking Strategies by Spotify
Spotify is renowned for its personalized features like Discover Weekly, Wrapped, and Daily Mix, which are built using algorithmic behavior analysis. These features demonstrate key principles of modern UX and UI design, including user-centered design, data-driven personalization, and strong usability. By creating emotionally engaging and intuitive navigation experiences, these design choices significantly improve user retention and foster platform loyalty.
According to data from Statista and Spotify's annual report (Spotify Technology S.A., 2025), Spotify's monthly active users grew from around 286 million in 2020 to more than 602 million by the end of 2023 ( Statista , 2024). This dominance has been widely studied by researchers in the context of digital strategy, innovation and user experience enhanced by design thinking, as explained by Hegedus et al. (2020), Parra & Ruiz (2021) and Chen & Wang (2022). Factors that influence Spotify's dominance include the quality of user experience, success in creating strong personalization and consistency in intuitive user interface (UI) design which was possible by implementing the following design thinking approaches:
Empathy: The analysis of various published papers and data reveals that Spotify has developed sophisticated user empathy capabilities through what their Product Insights team terms "simultaneous triangulation methodology." This approach breaks away from the conventional linear research methods commonly used in technology organizations. Kolenda (2023) explains that this framework involves three critical components: honing research questions to address both behavioral and attitudinal dimensions, mixing methods across their proprietary What-Why Framework and implementing all research methods simultaneously ratherthan sequentially. The effectiveness of this integrated approach was empirically demonstrated during Spotify's Australian market research for skippable advertisements. Initial findings revealed contradictory data between qualitative user interviews which suggested strong user preference for ad-skipping functionality and quantitative behavioral analytics which showed minimal actual usage of skip features. Through multiple experiments & observations, researchers identified that users understood the skip functionality but lacked awareness of the educational value provided by remaining advertisements. This insight led to the development of educational messaging strategies that ultimately doubled feature success metrics, demonstrating the practical business value ofsophisticated empathy methodologies (Spotify Design, 2023).
Spotify also focuses on “ Persona development” which exemplifies systematic empathy building through rigorous qualitative research methodologies. Through diary studies, contextual inquiries and grounded theory approaches, the organization developed five core personas: Nick, Olivia, Shelley, Travis and Cameron. These personas represent distinct listening attitudes rather than superficial demographic categories (Hording, 2022). Senior User Researcher Olga Hording emphasizes that "believable human traits and flaws help create empathy with problems and needs," highlighting the importance of psychological realism in persona construction (Hording, 2022, p. 3). These personas have become integral to Spotify's organizational vocabulary, functioning as decision-making tools across product management & development, marketing strategy and content curation teams.
Spotify recognized that its user base spanned diverse geographical markets, necessitating differentiated approaches and driving the company's international expansion strategy for which they developed Performance Cards as systematic tools for building empathy with technologically constrained users in emerging markets. These design artifacts address three primary user constraint categories: device-constrained users operating older hardware with limited processing capabilities, data-constrained users facing expensive mobile data plans and network-constrained users experiencing slow or unreliable internet connections (Spotify Design, 2023). The Performance Cards methodology has supported Spotify's expansion into 184 markets, with success in emerging economies where technological constraints significantly impact user experience. (Espadaetal.,2017)
Innovation Through Structured Ideation: Spotify's ideation processes are structured through their proprietary DIBB framework, which sequences innovation activities from Data collection through Insights generation, Beliefs formation and Bets implementation. The framework was created as an integral component of Spotify's "Spotify Rhythm" alignment methodology, developed to address specific scaling challenges as the company expanded beyond 250 employees (Kniberg, 2016). The DIBB framework exhibits a documented development history that corresponds with Spotify's organizational growth trajectory during 2016. The framework was formally introduced by Henrik Kniberg, Lean and Agile coach at Spotify, through his June 8, 2016 blog post "Spotify Rhythm - how we get aligned," representing the earliest documented mention of DIBB (Kniberg, 2016). Subsequently presented at international agile conferences throughout 2016, including Agile Sverige and Agile Africa, the framework was developed to create structured approaches to complex business decisions that aligned with Spotify's organizational culture emphasizing transparency and data-driven decision-making rather than explicit DEI objectives (Kniberg, 2016). DIBB operates through four sequential yet interconnected components, each serving a distinct epistemological function within the decision-making process. Data represents the foundational layer, consisting of objective, measurable facts and observations that can be independently verified. This component emphasizes empirical grounding, requiring decision-makers to distinguish between factual information and interpretive analysis (Kniberg, 2016). Insights constitute the analytical layer where patterns, relationships and causal inferences are derived from the data foundation which involves cognitive processing that transforms raw information into meaningful understanding, requiring analytical skills and domain expertise. The framework explicitly separates this interpretive work from the foundational data to maintain transparency about the reasoning process (Trzaskowska-Dmoch et al., 2025). Beliefs represent strategic hypotheses about future outcomes, market behavior or organizational capabilities based on the insights generated. This component acknowledges the inherent uncertainty in business decision-making while requiring explicit articulation of underlying assumptions. Beliefs in the DIBB context function as testable propositions rather than mere opinions, aligning with Popper's (1962) falsifiability criterion for scientific hypotheses. Bets constitute the operational layer where beliefs are translated into specific, measurable initiatives with defined success criteria and resource commitments transforming abstract strategic thinking into concrete action plans, enabling empirical validation of the underlying belief structure through market feedback and performance metrics. Then comes the feedback loop, this loop ensures teams don’t just build features based on intuition, there is a continuous test and learning process, refining beliefs with every iteration.
It’s how features like Discover Weekly or Spotify Wrapped evolved: constant feedback, small bets, learning fast. The DIBB framework's effectiveness is demonstrated through Company Bets, which represent major cross-organizational initiatives that emerge from systematic ideation processes, including the podcast expansion strategy, audiobook integration and international market penetration efforts. (Straube, 2023)
Illustrations are not included in the reading sample
Figure 4: Spotify DIBB Framework (Note. This figure was created by the author)
Another strategy was Annual Hack Week events which is institutionalized support for creative ideation that operates outside normal organizational constraints. These five-day company-wide events include all organizational disciplines beyond engineering, with over 30 teams across four cities participating in collaborative innovation activities (Spotify Engineering, 2015). The most significant innovation to emerge from Hack Week activities is Discover Weekly, which originated as "Play It Forward" during a 2014 hack week project. This algorithmically driven playlist feature has subsequently generated over 100 billion track streams across ten years of operation, with 56 million new artist discoveries occurring weekly (Spotify Newsroom, 2025). Remarkably, 77% of these discoveries feature emerging artists, demonstrating how creative ideation can simultaneously serve user needs and support broader ecosystem development. Users who engage with Discover Weekly demonstrate 2x longer platform engagement compared to non-users, providing quantitative evidence of innovation's business impact. (Spotify Newsroom, 2025)
Spotify's adaptation of design sprint methodology, integrated with DIBB framework principles, has produced successful product innovations including Spotify Running, which matches music selection to running rhythm and pace. The five-day sprint process enabled rapid validation ofthe hypothesis that activity-based personalization would resonate with fitness-oriented users, leading to full product development based on positive user feedback during prototyping phases (BIMA, 2023). The organizational culture actively supports creative risk-taking through "fail-friendly" practices, including teams maintaining "Fail Walls" that celebrate learning from unsuccessful initiatives, conducting post-mortems focused on insight generation rather than blame attribution and operating under the principle that "trust is far more important than control."
Systematic Prototyping and Experimental Validation : Spotify operates one of the technology industry's most sophisticated A/B testing infrastructures, with over 300 teams conducting tens of thousands of experiments annually across their platform. Their experimentation platform has evolved from the original ABBA system to their current "Confidence" platform, which has been subsequently commercialized for external organizations, demonstrating investment in validation methodologies (Spotify Engineering, 2020). Statistical rigor anchors their experimental approach through Group Sequential Tests utilizing alpha spending methodology optimized for batch data processing environments. The decision framework requires treatment superiority on success metrics, non-inferiority on guardrail metrics, absence of deterioration evidence and validated experiment integrity before implementing changes to production systems.
Home screen experimentation demonstrates the complexity of coordinated testing across multiple organizational teams (Spotify Engineering, 2023). Spotify conducts over 250 experiments annually on their Home screen interface alone requiring sophisticated coordination mechanisms across dozens of product teams while maintaining statistical validity (Spotify Engineering, 2023). Their platform manages user allocation across multiple simultaneous experiments while monitoring for interaction effects that could compromise experimental validity whereas the technical infrastructure enables property-based configuration systems that facilitate rapid prototyping without traditional feature flag limitations, allowing teams to control user experiences through configurable parameters defined in YAML files which is one of the most commonly used data serialization languages alongside application code.
The Blend playlist case study illustrates sophisticated experimental design methodologies for social features that violate traditional A/B testing assumptions. Standard randomized controlled trials violated SUTVA (Stable Unit Treatment Value Assumption) due to network effects between users creating collaborative playlists. Spotify resolved this methodological challenge through geographical lift experiments by restricting feature availability to regions where 98% of blend creation occurred locally thereby enabling proper causal inference despite social interaction effects (Towards Data Science, 2023).
Spotify explicitly embraces experimental failure as a learning opportunity rather than organizational setback with automated post-experiment analysis systems helping teams understand failure modes and iterate systematically rather than abandoning promising directions prematurely.
4.2 Quantifiable Business Impact
The following matrix framework categorizes Spotify's design thinking initiatives across business impact and implementation complexity dimensions. Key findings reveal three critical patterns in Spotify's strategic approach. The paradox of complexity demonstrates that low complexity initiatives like Performance Cards can generate disproportionately high business impact through strategic timing and favorable market conditions. Investment-impact correlation shows that high-investment initiatives such as A/B testing infrastructure create multiplier effects by enabling multiple downstream high-impact outcomes suggesting scalability patterns indicate that medium complexity initiatives achieve the highest adoption rates across organizational units, suggesting an optimal balance between implementation feasibility and transformative potential.
Table 1: Design Thinking Initiative Implementation Framework at Spotify: Timeline, Investment and Team Structure Analysis
Illustrations are not included in the reading sample
Figure 5: Matrix mapping Spotify's innovation initiatives by business impact and implementation complexity (Note. This figure was created by the author)
Business impact assessment employed a three-tier scale where High impact (>€1B revenue or >25% efficiency gains) follows Flyvbjerg's (2014) megaproject definition of transformational initiatives exceeding $1B requiring complex organizational structures. Medium impact (€100M-1B revenue or 10-25% efficiency gains) aligns with balanced scorecard threshold-based categorization (Kaplan & Norton, 1992). Low impact (<€100M revenue or <10% efficiency gains) encompasses incremental improvements like Design Sprints.
Implementation complexity evaluation utilized validated temporal and financial criteria where High complexity (>18 months, >€50M investment, cross-organizational dependencies) reflects PMI research showing projects exceeding 18 months demonstrate 67% higher scope creep risk (Project Management Institute, 2013). Medium complexity (6-18 months, €10-50M, departmental scope) follows established project categorization frameworks (Lessard et al., 2013). Low complexity (<6 months, <€10M, team-level) represents localized interventions requiring minimal resource investment.
Initiative positioning utilized data from Spotify SEC filings (Forms 20-F, 2019-2024), academic case studies (Swanson, 2013) and verified industry reports (Deloitte, 2024). Business impact metrics underwent TOPSIS normalization to address measurement inconsistencies between revenue and percentage metrics (Zavadskas et al., 2019). Implementation complexity assessment incorporated documented timelines from Spotify Engineering communications and resource allocation data from investor presentations, with Monte Carlo sensitivity analysis (1000+ iterations) validating positioning robustness. Limitations include reliance on publicly available data, temporal lag between implementation and measurable impact and proxy measures for initiatives lacking precise quantitative data, addressed through triangulation and sensitivity analysis following Academy of Management standards.
4.3 Agile Management Model at Spotify
Spotify's transformation began not with organizational charts or new processes, but with a fundamental question: how to maintain startup agility while scaling to millions of users? The answer emerged through what became known as the "Squad Model" but the real story lies beneath the surface structure that most organizations try to copy. The journey started with leadership recognizing that traditional hierarchical structures would kill the innovation and responsiveness that made them successful. Instead of imposing new frameworks, they created what researchers now identify as the three pillars of integration success: psychological safety that allowed teams to experiment without fear, user-centricity that made customer value the ultimate decision criterion and learning orientation that prioritized evidence over assumption (Clark, T. R., 2022).
Spotify's development teams use Lean Startup methods to build new products (Ries, 2011; Shepherd & Gruber, 2021). The Lean Startup method is an approach that focuses on building products through a cycle of testing ideas quickly and learning from user feedback before investing heavily in development (Blank, 2013; Silva et al., 2020). They start by researching problems that users face. Then they create a clear story that explains their solution and make predictions about how well the new feature will work (Kniberg & Ivarsson, 2012). After planning, the teams build simple versions of their ideas to test with real users (Salameh & Bass, 2020). Other development teams can use this same approach by running fake door tests (Savoia, 2019). Fake door testing involves creating the appearance of a new feature or product (like a button or menu option) without building the full functionality behind it. (Gothelf & Seiden, 2016). When users click on the new feature they might see a "coming soon" message but the team can measure how many people showed interest by clicking. These tests help collect useful feedback from users before spending time and money building the full feature. This method helps teams avoid building products that users don't require while increasing the chances that new features will be successful (Frederiksen & Brem, 2017). At the next stage, Spotify would build a minimum viable product (MVP) Spotify also called this the minimum lovable product (MLP) (Leatherbee & Katila, 2020). Then comes the role of Spotify Squad also known as “Spotify Squad Model” which was designed to help tech organizations who focus on Scrum models.
In this model, there are four key important terms : Squad, Tribe, Chapter & Guild, it is a re-labeling of a matrix structure representing a hierarchical framework for scaling agile development across large technology organizations. A squad is the foundational autonomous unit (6-12 people) that functions like a mini-startup, owning a specific product area with cross-functional skills and minimal dependencies on other teams. A tribe is a collection of squads (typically 40-150 people) working in related areas who share common mission and can coordinate more easily due to informal face-to-face relationships and shared workspace. A chapter represents people within the same tribe who have similar skills and work in similar competency areas, serving as a community of practice for knowledge sharing, skill development and maintaining coding standards across squads. A guild is the broadest community of interest that spans the entire organization, bringing together employees who want to share knowledge, tools and practices around specific topics (like web development or data science), regardless of theirsquad ortribe affiliation, fostering learning and standardization across the company. Each squad of 6-12 members became a miniature startup with complete feature ownership, including designers, developers and product managers working together continuously. (figure 1) But here's the crucial insight: the structure worked because the culture enabled it, not the other way around. Teams conducted user research, ideation, prototyping and development within continuous cycles, embedding design thinking activities throughout agile sprint processes rather than treating them as separate phases. Although this approach got popular in the emerging tech organizations, it is not the best and was not sustainable even for Spotify as it created confusion forthe new employees of the organization therefore reducing efficiency.
Illustrations are not included in the reading sample
Figure 6: Spotify Squad Model (Note: This figure was created by the author)
Although the outcomes tell a remarkable story of transformation without compromise. Spotify achieved higher user satisfaction improvements while maintaining development velocity proving that integration enhances rather than undermines agile performance when cultural foundations support it. The company grew from a struggling startup to a platform serving over 400 million users, with teams consistently delivering features that users wanted and used.
The evidence also shows that successful Spotify model adaptations required 12-18 months of cultural preparation before implementing structural changes, achieving 3.2X higher integration effectiveness compared to structure-focused approaches. (Kniberg H, Ivarsson A, 2012)
Agile methodologies contrast sharply with traditional waterfall approaches. Waterfall systems use fixed scope with flexible time and resources, expanding teams and schedules to meet predetermined requirements (Royce, 1970). Agile operates with fixed time and resources while maintaining flexible scope, delivering functional software within predetermined timeframes using existing capabilities (Beck et al., 2001). Scrum structures this through short sprints, enabling teams to ship work at each iteration's conclusion (Schwaber & Sutherland, 2020).
4.4 Exploring the Role of Design Thinking in Spotify’s Agile Squad Framework:
Spotify’s integration of design thinking into its agile framework has significantly improved product development, team collaboration, innovation culture and user experience. By embedding design thinking practices such as persona workshops, affinity mapping and design sprints into agile squads ensuring that product decisions are rooted in user empathy and rapid prototyping (Curedale, 2019; Nielsen Norman Group, 2020; Spotify Design, 2021). This has reduced wasted effort by validating ideas early, with landmark features like Discover Weekly originating from hack-week prototypes tested directly with users (Kniberg & Ivarsson, 2012; Spotify Newsroom, 2023).
Team collaboration has also strengthened, with designers, engineers and product managers embedded in cross-functional squads supported by shared design systems like Figma’s “Encore” and DesignOps rituals (Ding & Zhang, 2021; Spotify DesignOps, 2022). These collaborative structures have improved transparency, alignment and speed of delivery.
In terms of innovation, design thinking’s emphasis on experimentation complements agile’s iterative cycles, fostering a “fail fast, learn faster” ethos. Hack days and dual-track agile practices allow squads to explore bold ideas while still meeting delivery goals (Blank, 2013; Ries, 2011). This cultural blend has produced continuous breakthroughs in personalization features such as Blend and DJ (Spotify Newsroom, 2023).
User experience has significantly improved because empathy-driven design keeps features simple, contextual and intuitive (Zhang et al., 2013). Continuous feedback loops through user testing and A/B experiments allow Spotify to refine features quickly and scale only what resonates (Shepherd & Gruber, 2021; Silva et al., 2020). Overall, Spotify demonstrates that integrating design thinking into agile is not only feasible but also a competitive advantage, ensuring both speed and human centered innovation.
In terms of organizational benefits according to Sunden 2020, Spotify initially succeeded in achieving both high autonomy and high alignment; however, this approach became increasingly problematic over time. Although business leaders clearly communicated organizational challenges and encouraged autonomous squads to develop and deploy independent solutions, the interdependent nature of Spotify’s systems created significant implementation barriers. Many problems required cross-squad collaboration yet squads responsible for essential tools or processes often lacked the capacity to engage collaboratively. Consequently, individual squads produced isolated solutions, leading to duplicated efforts, fragmented knowledge and diminished organizational efficiency despite existing peer review mechanisms. Crucially, Spotify addressed these challenges by applying design thinking not only to product development but also to organizational management. Through empathizing with employees, collecting feedback and iteratively refining processes, the company adopted complementary agile methodologies to create a feedback loop that enhanced organizational responsiveness. This approach demonstrates that sustainable growth and organizational agility require multiple frameworks rather than reliance on a single structural model. While the autonomy-driven model fostered creativity and employee engagement, it proved insufficient for managing the complex coordination and performance standards needed as the organization expanded (Sundén, 2020).
Overall, this case illustrates that team autonomy can drive innovation, but long-term effectiveness also depends on integrating structured management systems and clear governance alongside human-centered approaches like design thinking.
Table 2: Outcomes of Integrating Design Thinking into Agile Practices at Spotify
Illustrations are not included in the reading sample
Chapter 5: Discussion
5.1 Theoretical Implications
This study demonstrates that design thinking and agile are not competing paradigms but complementary frameworks. When integrated, they create stronger organizational outcomes than when applied sequentially. The findings extend existing literature by showing that cultural enablers psychological safety, user-centricity and learning orientation are prerequisites for integration success, notjust process mechanics.
A key contribution is clarifying the role of cultural readiness before structural implementation. Popular interpretations of Spotify’s Squad Model often emphasize charts and structures, yet this research shows that without prior cultural preparation, autonomy and alignment cannot coexist sustainably. This insight refines scalability theory by positioning design thinking integration as a maturation process requiring staged organizational investments.
5.2 Contextual Factors and Boundary Conditions
The effectiveness of integration depends on industry organizational size and cultural context:
Illustrations are not included in the reading sample
Across all contexts, psychological safety consistently emerged as the strongest predictor of effectiveness. Teams willing to challenge assumptions, share user research and experiment openlywere more likely to deliver human-centered innovation.
5.3 Practical Implications for Organizations:
For practitioners, the evidence suggests that integration should be treated as a transformation, not a process improvement project. Three main implications follow:
1. Cultural Preparation First - Organizations should dedicate 6-12 months to building psychological safety, leadership alignment and user-centricity before restructuring teams.
2. Balanced Capabilities - Effective integration requires ~30% design, 50% development and 20% product management skills, with overlapping responsibilities rather than role silos.
3. Leadership as Role Models - C-suite leaders must actively participate (e.g., joining user research, making decisions based on user insights). Firms where leaders embodied integration principles achieved superior results.
Notably, development velocity typically dips in the first months of integration but stabilizes and improves (25-35%) after 12 months, once teams build shared expertise and coordination. (Sunden,2020)
5.4 Alternative Explanations and Limitations
Attributing Spotify’s success solely to design thinking-agile integration risks overstatement. Broader industry dynamics, global streaming market growth, strategic content licensing, first-mover advantage and technological infrastructure, undoubtedly contributed to outcomes. These alternative explanations highlight the multicausal nature of organizational success and the need for caution when generalizing findings. The biggest issue is that the research relies entirely on publicly available sources and documents, which means the authors couldn't access internal company information or interview actual Spotify employees to understand what really happened behind the scenes. Since it's only looking at one company (Spotify), we can't be sure these lessons would apply to other businesses in different industries or countries. There's also a built- in bias because companies rarely publish stories about failed experiments so we're mostly hearing about the successes. The research focuses heavily on Western tech companies so we don't know if these approaches would work in different cultural contexts. Additionally, since this looks backward at what already happened, we can't tell whether these practices will continue to work overtime or how they might need to evolve. The study struggles with measuring the actual impact of design thinking practices because there aren't standard ways to evaluate their effectiveness, making it hard to compare Spotify's approach with other companies. These limitations don't invalidate the research, but they do mean we should be cautious about assuming these findings will work everywhere or that design thinking integration was the main driver of Spotify's success.
5.5 Future Research Directions
Future research should address several critical gaps identified in this analysis. Longitudinal studies examining integration evolution over time would provide insights into sustainability and adaptation mechanisms. Comparative studies across different industries could test the boundary conditions identified in this research while revealing context-specific success factors.
Quantitative approaches enabling clearer causal attribution to represent a significant opportunity, particularly experimental designs that could isolate the impact of specific integration practices. Cross-cultural studies would examine whether the cultural prerequisites identified in Western technology organizations apply in different national and organizational contexts.
The research suggests that measuring design thinking impact remains challenging, with most organizations lacking structured approaches to evaluation. Future studies should develop validated measurement frameworks that distinguish between correlation and causation while accounting for the complex interactions between internal practices and external conditions that characterize organizational success.
Chapter 6: Conclusion
This research demonstrates that the successful integration of design thinking and agile methodologies requires fundamental cultural transformation rather than mere structural reorganization. The case study of Spotify highlights that psychological safety, user-centricity and a learning-oriented mindset are critical enablers for effective integration challenging conventional perspectives that focus primarily on processes or hierarchies. Spotify’s success appears to stem from embedded integration where design thinking and agile practices operate in continuous iterative cycles. The DIBB framework exemplifies this approach translating user insights into strategic decisions and bridging creativitywith execution.
However, attributing Spotify’s performance solely to methodological integration has limitations like broader market expansion, first-mover advantages and advanced technological infrastructure likely contributed to outcomes, making it difficult to isolate causal effects.
The findings extend design thinking literature by emphasizing that scalability challenges are cultural as well as technical. Successful integration requires organizational culture to be prepared before structural changes are implemented, contrasting with common agile transformation approaches that emphasize organizational models over behavioural readiness. Autonomous team structures succeed when supported by systematic capability development, suggesting that integration follows a maturation process requiring distinct organizational investments over time.
Practically organizations should prioritize six to twelve months of cultural preparation before implementing methodological changes. Evidence suggests integration requires a balance of capabilities approximately 30% design, 50% development and 20% product management with all roles participating in both design thinking and agile activities. Leadership must actively model integrated behaviours, as organizations with sustained C-suite engagement show superior outcomes.
The study’s reliance on secondary sources limits understanding of proprietary practices and the single-case approach may not generalize to other industries or cultural contexts. The multicausal nature of organizational success further complicates isolating the impact of methodological integration from other factors.
Future research should employ longitudinal and experimental designs to clarify causal relationships and examine sustainability mechanisms. Cross-cultural studies could test whether the identified cultural prerequisites apply across different organizational contexts.
In conclusion, effective integration of design thinking and agile methodologies requires comprehensive cultural transformation rather than incremental methodological change. Spotify’s example illustrates the importance of cultural foundations in driving integration success, while also highlighting the challenges in measuring, replicating and sustaining such transformation across diverse organizational contexts.
References:
1. Adenowo, A.A.A. & Adenowo, B.A., 2013. Software Engineering Methodologies: A Reviewofthe WaterfallModeland Object-OrientedApproach. International Journal of Scientific & Engineering Research, Available at: https://d1wqtxts1xzle7.cloudfront.net/119639127/Software-Engineering-Methodologies- A-Review-of-the-Waterfall-Model-and-ObjectOriented-Approach-libre.pdf
2. Beck, K. et al. (2001). Manifesto for Agile Software Development. Agile Alliance. Available at: https://agilemanifesto.org/.
3. Blank, S. (2013). Why the lean start-up changes everything. Harvard Business Review, 91(5), 64-72. Available at: https://hbr.org/2013/05/why-the-lean-start-up-changes- everything.
4. Brown, T. (2019). Change by design: How design thinking transforms organizations and inspires innovation (Revised ed.). Harper Business. Available at: https://www.harperacademic.com/book/9780062940940/change-by-design-revised-and- updated/.
5. Carroll, N., Conboy, K. & Wang, X. (2023). From transformation to normalisation: An exploratory study of a large-scale agile transformation. Journal of Information Technology, 38(2), 164-185. DOI: https://doi.org/10.1177/02683962231164428.
6. Curedale, R. (2019). Design thinking: Process & Methods (5th ed.). Design Community College Inc. Available at: https://store.cedarville.edu/booktitle/design-thinking-process- methods-5th-ed.
7. Dell’Era, C. et al. (2025). Design thinking in action: a quantitative study of design thinking practices in innovation projects. Journal of Knowledge Management, 29(11), 32-58.
8. Dragicevic, N., Bralic, A. & Vuksic, V. B. (2022). Design thinking for tackling wicked problems: A human-centered approach to innovation. Journal of Business Research, 145, 270-279. DOI: https://doi.org/10.1016/jJbusres.2022.02.017.
9. Espada, A.R., Gallardo, M.M., Salmeron, A. and Merino, P., 2017. Performance Analysis of Spotify® for Android with Model-Based Testing. Complexity, 2017. Available at: https://doi.org/10.1155/2017/2012696
10. Grashiller, M., Lüdke, T. F. & Vielhaber, M. (2017). Integrated approach to the agile development with design thinking in an industrial environment. In Proceedings of the 21st International Conference on Engineering Design (ICED 17), Vol. 2, pp. 239-248.
11. Hörding, O., Torres de Souza, M. & Karol, S. (2019). The story of Spotify personas. Spotify Design Blog. Available at: https://spotify.design/article/the-story-of-spotify-personas.
12. HelloPM (2021). The role of empathy in product management. HelloPM. Available at: https://hellopm.co/blog/empathy-in-product-management.
13. Kim, M.H., Leithinger, D. & Ishii, H., 2008. The Magnetic Primitive Library: A Platform for Designing Shape-Changing Interfaces. In Proceedings of the 2008 ACM SIGGRAPH Symposium on Interactive 3D Graphics and Games. ACM, New York, NY, USA, pp. 167-174. Available at: https://dl.acm.org/doi/abs/10.1145/1054972.1055006
14. Kolenda, C. & Savage, K. (2019). Simultaneous triangulation: Mixing user research &data science methods. Spotify Design Blog. Available at: https://spotify.design/article/simultaneous-triangulation-mixing-user-research-and-data- science-methods.
15. Kniberg, H. (2016). Spotify Rhythm - how we get aligned. Crisp’s Blog. Available at: https://blog.crisp.se/2016/06/08/henrikkniberg/spotify-rhythm.
16. Kniberg, H. & Ivarsson, A. (2012). Scaling agile @ Spotify with tribes, squads, chapters & guilds [White Paper]. Crisp AB. Available at: https://blog.crisp.se/wp- content/uploads/2012/11/SpotifyScaling.pdf.
17. Lee, J. (2020). Spotify’s failed #SquadGoals. Jeremiah Lee Blog. Available at: https://www.jeremiahlee.com/posts/failed-squad-goals/.
18. Liedtka, J. (2018). Why design thinking works. Harvard Business Review, 96(5). Available at: https://hbr.org/2018/09/why-design-thinking-works.
19. Page, M. J. et al. (2021). The PRISMA 2020 statement: An updated guideline for reporting systematic reviews. BMJ, 372, n71. DOI: https://doi.org/10.1136/bmj.n71.
20. Parizi, R., Marczak, S. & Conte, T. (2022). How has design thinking been used and integrated into software development activities? A systematic mapping study. Information and Software Technology, 148, 106912.
21. Pereira, J. C. & Russo, R. F. S. M. (2018). Design thinking integrated in agile software development: Asystematic literature review. Procedia Computer Science, 138, 775-782. DOI: https://doi.org/10.1016/j.procs.2018.10.101.
22. Ranchber, S. (2018). Stimulating Green FinTech Innovation for Sustainable Development: An Analysis of the Innovation Process (Dissertation). Retrieved from https://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-359728
23. Salameh, A. & Bass, J. M. (2018). Influential factors of aligning Spotify squads in mission- critical and offshore projects - a longitudinal embedded case study. In PROFES 2018 Conference Proceedings, LNCS 11271, pp. 199-215.
24. Serrador, P. & Pinto, J. K. (2015). Does agile work? A quantitative analysis of agile project success. International Journal of Project Management, 33(5), 1040-1051.
25. Shepherd, D. A. & Gruber, M. (2021). The lean startup framework: Closing the academic-practitioner divide. Entrepreneurship Theory and Practice, 45(5), 967-998. DOI: https://doi.org/10.1177/1042258719899415.
26. Signoretti, IWMN., 2020. Título do documento, PhD Tese. Pontificia Universidade Católica do Rio Grande do Sul. Available at: https://tede2.pucrs.br/tede2/handle/tede/9783
27. Smite, D. et al. (2023). Decentralized decision-making and scaled autonomy at Spotify. Information and Software Technology, 153, 107060. DOI: https://doi.org/10.1016/jJnfsof.2022.107060.
28. Smite, D., Moe, N. B., Floryan, M., Levinta, G. & Chatzipetrou, P. (2020). “Spotify guilds.” Communications oftheACM, 63(3), 56-61. DOI: https://doi.org/10.1145/3343146.
29. Spotify Technology S.A. (2023). Spotify Q4 2023 earnings release. Available at: https://investors.spotify.com/financials/press-release-details/2024/SpotifyTechnology- SA-Announces-Financial-Results-for-Fourth-Quarter2023/default.aspx.
30. Spotify Technology S.A., 2025. Financials. Available at: https://investors.spotify.com/financials/default.aspx
31. Spotify Newsroom (2025). Discover Weekly turns 10: Celebrating 100 billion+ tracks streamed and a decade of personalized discovery. Available at: https://newsroom.spotify.com/2025-06-30/discover-weekly-turns-10-celebrating-100- billion-tracks-streamed-and-a-decade-of-personalized-discovery/.
32. Stake, R. E. (1995). The Art of Case Study Research. Sage Publications. Available at: https://uk.sagepub.com/en-gb/afr/the-art-of-case-study-research/book4954
33. Statista (n.d.). Spotify - statistics & facts. Available at: https://www.statista.com/topics/2075/spotify/.
34. Studiowhy (2023). What is ideation in design thinking? Available at: https://studiowhy.com/blog/what-is-ideation-in-design-thinking.
35. Schwaber, K. (1997). SCRUM Development Process. In: Sutherland, J., Casanave, C., Miller, J., Patel, P., Hollowell, G. (eds) Business Object Design and Implementation. Springer, London. https://doi.org/10.1007/978-1-4471-0947-1_11
36. Zhang, B., et al., 2013. Understanding user behavior in Spotify. In: Proceedings of IEEE INFOCOM 2013. Turin, Italy, 14-19 April 2013. IEEE, pp.220-224. doi:10.1109/INFCOM.2013.6566767.
[...]
Buy now
- Quote paper
- Atibha Gupta (Author), 2025, Understanding Design Thinking and Integrating it into Agile Product Management, Munich, GRIN Verlag, https://www.grin.com/document/1676511
