Abstract Agile at scale introduces persistent tensions as organizations attempt to balance autonomy, coordination, and control across teams and layers. Some tensions are paradoxes, which are persistent contradictions in which both sides matter. Drawing on a qualitative case study of MarketCorp, a multinational marketplace company, we explore how paradoxes manifest in a large-scale agile context and how leaders respond. Interviews with 15 top managers and reflective conversations with 60 employees reveal three paradoxes: centralization vs. autonomy, internal vs. external focus, and product vs. project approaches. We explored two approaches for designing facilitated dialogue around paradoxes in leadership teams. The study highlights the importance of recognizing, normalizing, and collaboratively managing paradoxes and offers practical guidance for large-scale agile organizations, demonstrating that paradoxes can provide a valuable focus for continuous improvement and strengthen agile learning practices.

This empirical study examines the transformation of a large-scale multinational software engineering organization into a product-oriented enterprise following Continuous Software Engineering (CSE) principles. Focusing on MarketCorp — a digital marketplace organization with distributed software development teams across multiple countries — the study explores the complex dimensions of transformation required for large-scale organizational change. Drawing on 15 interviews with MarketCorp’s top management, our findings reveal that the transformation encompasses three interconnected dimensions: organizational, platform, and cultural transformation. The organizational dimension involves structural changes and software engineering capacity redistribution; the platform dimension requires transitioning from brand-specific software platforms to a unified service-oriented model; and the cultural dimension encompasses shifts in identity, working relationships, and cross-regional software development collaboration. These dimensions are essential to enable successful CSE implementation at scale. The study contributes to empirical software engineering research by highlighting the need for organizations to proactively manage paradoxes and balance multiple competing demands across all transformation dimensions. Our findings provide practical insight for organizations undertaking similar transformations, emphasizing the importance of integrated change management approaches that consider the interdependencies between organizational structure, technology infrastructure, and cultural adaptation.

Abstract Context Organizations opt for continuous delivery of incremental updates to deal with uncertainty and minimize waste. However, applying continuous engineering (CSE) practices requires a continuous feedback loop with input from customers and end-users. Challenges It becomes increasingly challenging to apply traditional requirements elicitation and validation techniques with ever-shrinking software delivery cycles. At the same time, frequent deliveries generate an abundance of usage data and telemetry informing engineering teams of end-user behavior. The literature describing how practitioners work with user feedback in CSE, is limited. Objectives We aim to explore the state of practice related to utilization of user feedback in CSE. Specifically, what practices are used, how, and the shortcomings of these practices. Method We conduct a qualitative survey and report analysis from 21 interviews in 13 product development companies. We apply thematic and cross-case analysis to interpret the data. Results Based on our earlier work we suggest a conceptual model of how user feedback is utilized in CSE. We further report the identified challenges with the continuous collection and analysis of user feedback and identify implications for practice. Conclusions Companies use a combination of qualitative and quantitative methods to infer end-user preferences. At the same time, continuous collection, analysis, interpretation, and use of data in decisions are problematic. The challenges pertain to selecting the right metrics and analysis techniques, resource allocation, and difficulties in accessing vaguely defined user groups. Our advice to practitioners in CSE is to ensure sufficient resources and effort for interpretation of the feedback, which can be facilitated by telemetry dashboards.

Context Large fintech organizations are increasingly adopting agile methodologies to enhance product development capabilities. However, implementing agile at scale presents unique challenges, particularly related to collaboration essential for successful software product management (SPM). Social capital, comprising structural, cognitive, and relational dimensions, may play a crucial role in facilitating the collaboration needed to overcome these challenges. Objectives We examine the role of social capital in large-scale agile SPM, focusing on how it facilitates coordination, collaboration, and, ultimately, success, in complex, product-focused environments. Methods We employ a multi-case study approach, comprising 33 interviews, observations, and document analysis, analyzing two Scandinavian fintech companies that have adopted large-scale agile practices organized around product areas. Results Our findings, viewed through the lens of social capital theory, show that its three dimensions help explain how large-scale organizations adopting SPM manage dependencies and enable product-focused coordination. Specifically, the structural dimension helps illuminate how networks are formed; the cognitive dimension clarifies how shared understanding of product visions and development practices emerges; and the relational dimension highlights how trust is cultivated among product development actors across multiple operational levels (i.e., product team, product area, organizational, and external levels). Together, these dimensions offer insight into how agile practices are effectively implemented at scale. Conclusion Our study finds that social capital is a critical enabler of effective SPM in large-scale agile contexts. Its three dimensions support the collaboration and relational networks necessary for agility at scale. These insights suggest that fostering social capital should be prioritized in agile transformations to address the sociotechnical complexities inherent in large-scale SPM.

Context: Teamwork is an important aspect of agile software development, and the widespread adoption of agile methodologies emphasizes the need for educational approaches that prepare students for effective teamwork. Capstone courses in agile software engineering provide a valuable setting for students to experience collaborative work. However, the dynamics within these teams, particularly regarding gender, require further exploration. Objectives: This study examines teamwork experiences in an agile capstone course focusing on how team gender composition affects role distribution, teamwork quality, and gender bias. Methods: This study involved 94 teams comprising 561 students over two years (213 women and 348 men). We employed a mixed-methods approach, using four surveys (806 responses) and 12 in-depth interviews to capture ambition level, satisfaction with agile practices, and gender differences. Results: Team gender composition significantly impacted teamwork quality (TWQ), with female-dominated but gender-diverse teams showing the highest TWQ scores. Interestingly, women in token positions in male-majority teams reported unexpectedly high satisfaction levels, challenging aspects of Kanter’s tokenism theory. However, women were more likely to report that team members underestimated their competence, particularly in male-majority teams. Observed gender differences included a tendency for women to engage more in design and process-oriented tasks, while men predominantly focused on programming and technical aspects such as architecture and algorithms. Conclusion: This study underscores the importance of considering team composition in relation to gender in agile teams, as we found this aspect greatly impacts team dynamics. Further, the implementation of agile practices in capstone courses yielded high overall TWQ scores, indicating significant educational value. Our findings provide insights for both software engineering education and agile practitioners.

Abstract Large-scale agile software development is increasingly being organized with product management. Although product management is familiar to software engineering, we need research-based knowledge about organizing product management in an agile development context. This study focuses on product management challenges and configurations in a Nordic fintech organization with 10,000 employees. We conducted 19 interviews with participants involved in core product management activities. The study identifies ten key factors that hinder product management performance in a large-scale agile product company. Further, we present six product management configurations used in the fintech organization. The most suitable setup depends on the product lifecycle stage, product size, and development team setup. Our summary of the product management configurations and challenges can guide software product managers working in large-scale agile companies.

Abstract This paper examines the role of the enterprise social networking (ESN) tool Slack in the daily work of software practitioners within NAV, a large-scale agile public sector organization. Based on 13 interviews with NAV developers, our case study explores how Slack is employed for knowledge sharing and daily communication across the organization. We used a newly developed framework for communication in agile teams as a theoretical lens. Through our analysis, we found that Slack use had become deeply integrated into the organizational culture and fostered alignment in three main ways: Promotingcommunication transparencythrough open discussions visible for developers organization-wide, enhancingcommunication qualitywith prompt responses and constant communication, and encouragingcommunication disciplinethrough structured channels and threads. This study also unveiled some challenges, such as information overload and hindered focus. However, our findings suggest that if common hurdles are overcome, modern ESN tools can reshape how cross-organizational communication plays out in large-scale agile, reinforcing the agile principles of collaboration and motivated individuals.

Pair programming (PP) has been a widespread practice for decades and is known for facilitating knowledge exchange and improving the quality of software. Many agilists advocated the importance of collocation, face-to-face interaction, and physical artifacts incorporated in the shared workspace when pairing. After a long period of forced work-from-home, many knowledge workers prefer to work remotely two or three days per week, which is affecting practices such as PP. In this revelatory single-case study, we aimed to understand how PP is practiced during hybrid work when team members alternate between on-site days and working from home. We collected qualitative and quantitative data through 11 semi-structured interviews, observations, feedback sessions, and self-reported surveys. The interviewees were members of an agile software development team in a Norwegian fintech company. The results presented in this paper indicate that PP can be practiced through on-site, remote, and mixed sessions, where the mixed mode seems to be the least advantageous. The findings highlight the importance of adapting the work environment to suit individual work mode preferences when it comes to PP. In the future, we will build on these findings to explore PP in other teams and organizations practicing hybrid work.

Abstract Datafication processes, the ongoing strive for making organizations data-driven, have in recent years entailed data-focused software projects and more interdisciplinary teamwork. Simultaneously as agile product teams have been directed towards increased use of data for software development, stronger data protection regulations such as GDPR have further complexified the software developer role, whose responsibilities and expectations now expand far beyond mere coding. Seeking to develop an understanding of how data-intensive product teams in the public sector maneuver the legal hurdles emerging in the wake of data governance, this paper builds on 19 interviews with members of two agile product teams in the Norwegian organizations NAV and Entur. Our findings indicate that including a legal expert in the team can boost confidence in data handling practices and avoid delays in deliveries, but it requires effort to synchronize and overcome interdisciplinary barriers.