A Taxonomy of Inter-Team Coordination Mechanisms in Large-Scale Agile

IEEE Transactions on Software Engineering, Год журнала: 2022, Номер 49(2), С. 699 - 718

Опубликована: Март 22, 2022

In large-scale agile software development, many teams work together to achieve overarching project goals. The more teams, the greater coordination requirements. Despite growing popularity of agile, inter-team is challenging practice and research. We conducted a case study over 1.5 years in development firm better understand which mechanisms are used how they support coordination. Based on thematic analysis 31 interviews, 113 hours observations, supplemental material, we identified 27 mechanisms. From this, offer following contributions. First, propose taxonomy with three categories: meetings, such as communities practice, stand-ups, retrospectives; roles, program architects platform team; tools artefacts, Slack JIRA well task boards, product backlogs, roadmaps. Second, displayed combinations four key characteristics, technical, organizational, physical, social (TOPS), form basis TOPS framework capture multifaceted characteristics Technical relates and/or technical supporting development. xmlns:xlink="http://www.w3.org/1999/xlink">Organizational pertains structural aspects organization. xmlns:xlink="http://www.w3.org/1999/xlink">Physical refers tangible or spatial characteristics. xmlns:xlink="http://www.w3.org/1999/xlink">Social captures interpersonal community-based Finally, provide knowledge base structured approach for researchers practitioners improve agile.

Язык: Английский

---

A longitudinal explanatory case study of coordination in a very large development programme: the impact of transitioning from a first- to a second-generation large-scale agile development method

Empirical Software Engineering, Год журнала: 2022, Номер 28(1)

Опубликована: Ноя. 8, 2022

Abstract Large-scale agile development has gained widespread interest in the software industry, but it is a topic with few empirical studies of practice. Development projects at scale introduce range new challenges managing large number people and teams, often high uncertainty about product requirements technical solutions. The coordination teams been identified as one main challenges. This study presents rich longitudinal explanatory case very programme 10 teams. We focus on inter-team two phases: that applies first-generation method another uses second-generation one. 27 mechanisms first phase, 14 second. Based an analysis strategies mechanisms, we develop five propositions how transition from first- to impacts coordination. These have implications for theory

Язык: Английский

---

Responding to change over time: A longitudinal case study on changes in coordination mechanisms in large-scale agile

Empirical Software Engineering, Год журнала: 2023, Номер 28(5)

Опубликована: Авг. 29, 2023

Abstract Context Responding to change and continuously improving processes, practices, products are core agile software development. It is no different in large-scale agile, where multiple development teams need respond both changes their external environments within the organization. Objective With this study, we aim advance knowledge on coordination by developing a model of types organizational that influence mechanisms. Method We conducted longitudinal case study growing organization, focusing how internal impact over time. collected our data through 62 days fieldwork across one half years. 37 interviews, observed 118 meetings at all levels, supplementary material such as chat logs presentations, analyzed using thematic analysis. Results Our findings demonstrate events, onboarding new clients, team mechanisms program. find events lead introduction mechanisms, or adjustment existing ones. Further, continuous scaling requires adjustment. Finally, having right place time strengthens resilience ability cope with needs complex environments. Conclusions summarized an empirically based provides practical approach analyzing change, aimed supporting researchers practitioners dealing contexts.

Язык: Английский

---

Coordination in Agile Product Areas: A Case Study from a Large FinTech Organization

Lecture notes in business information processing, Год журнала: 2024, Номер unknown, С. 36 - 52

Опубликована: Янв. 1, 2024

Язык: Английский

---

Scaling Agile Company-Wide: The Organizational Challenge of Combining Agile-Scaling Frameworks and Enterprise Architecture in Service Companies

IEEE Transactions on Engineering Management, Год журнала: 2021, Номер 69(6), С. 3489 - 3502

Опубликована: Дек. 15, 2021

Many organizations have embraced agile methods. Studies show a trend of large-scale application frameworks company-wide. Emergent architecture design as part an approach is effective at the project level but causes issues when services need to interact seamlessly enterprise level. Enterprise (EA) can provide such coherence. Combining scaling methods with EA challenging. However, combination could benefit from flexibility that approaches offer and consistency long-term focus pursues. This article uses longitudinal case study research explore how effectively govern Agile in transformations. Our analysis shows for do not sufficient guidance properly handle transformation existing practices We propose be applied transformations despite two seemingly conflicting EA. Based on our findings, we conceptual model future incorporates factors take into account governance agile-scaling frameworks. findings extend current literature coordination mechanisms between architects teams transformations, thereby balancing emergent intentional architectures.

Язык: Английский

---

Knowledge Sharing and Coordination in Large-Scale Agile Software Development – A Systematic Literature Review and an Interview Study

Lecture notes in business information processing, Год журнала: 2025, Номер unknown, С. 81 - 99

Опубликована: Янв. 1, 2025

Язык: Английский

---

Changes to team autonomy in large-scale software development: a multiple case study of Scaled Agile Framework (SAFe) implementations

Deleted Journal, Год журнала: 2022, Номер 10(1), С. 29 - 46

Опубликована: Апрель 5, 2022

Large-scale transformations of agile ways working have received more attention in the industry recent years. Some organizations developed their own solutions for scaling, whereas many chosen trademarked frameworks. In large-scale software development, developers and development teams carry out work simultaneously. When autonomous need to coordinate toward a common goal, they must sacrifice some level autonomy. Development, testing, integrations be coordinated with other aligned an organization´s programs or portfolio. Through conducting 28 interviews 17 on-site visits, this multiple case study explored how team autonomy changed three that implemented Scaled Agile Framework (SAFe). The positive changes experienced as result included getting better overview, making long-term decisions, giving receiving help, signaling limitations. We found two negative impacts on autonomy: limited feature choice enforced refinement. extends previous research improves our understanding

Язык: Английский

---

Quality culture boosts agile transformation—Action research in a business‐to‐business software business

Journal of Software Evolution and Process, Год журнала: 2022, Номер 35(1)

Опубликована: Авг. 29, 2022

Abstract Agile methodologies are sometimes adopted, with the assumption that benefits can be attained by only using a set of best practices, which work to degree. In this paper, case is discussed where software‐producing organization seven teams achieved significant improvements. The goal research was answer two questions: how an already agile could improve its performance further and what impact promoting quality aspects? questions were answered implementing interventions based on prior literature data emerging from semi‐structured interviews. context established business complex revenue stream structure, meaning mix various project/service/product rendered adoption methods challenge. Action comprising three rounds conducted culture while enforcing code review practices. Interventions resulted in improvement quality, as measured reported defects. Therefore, it suggested not sufficient their own take software forward unless quality‐focused simultaneously through mindset change organizational structures enforce paper contributes managerial practices transformation providing empirical support introducing formal method for practitioners organizations models multiple teams.

Язык: Английский

---

Using Objectives and Key Results (OKRs) and Slack: A Case Study of Coordination in Large-Scale Distributed Agile

Proceedings of the ... Annual Hawaii International Conference on System Sciences/Proceedings of the Annual Hawaii International Conference on System Sciences, Год журнала: 2022, Номер unknown

Опубликована: Янв. 1, 2022

Today, many large-scale software projects have members working from home, which has changed the way teams coordinate work.To better understand coordination in this setting, we conducted a case study through examined two agile project by observing meetings and conducting 17 interviews.Through lens of Relational Coordination Theory (RCT), analyzed use goal-setting framework Objectives Key Results (OKRs) collaboration tool Slack.Slack was used for frequent, timely, problem-solving communication and, its decreased number planned meetings.However, discussions often started on Slack continued virtual ad-hoc meetings.The OKRs facilitated knowledge sharing, helped align their goals, provided inter-team insights.The main implication our research is that using need to support members, especially formulating key results motivate work toward same mission.

Язык: Английский

---

Using Objectives and Key Results (OKRs) and Slack: A Case Study of Coordination in Large-Scale Distributed Agile

Опубликована: Ноя. 3, 2021

Today, many large-scale software projects have members working from home, which has changed the way teams coordinate work. To better understand coordination in this setting, we conducted a case study through examined two agile project by observing meetings and conducting 17 interviews. Through lens of Relational Coordination Theory (RCT), analyzed use goal-setting framework Objectives Key Results (OKRs) collaboration tool Slack. Slack was used for frequent, timely, problem-solving communication and, its decreased number planned meetings. However, discussions often started on continued virtual ad-hoc The OKRs facilitated knowledge sharing, helped align their goals, provided inter-team insights. main implication our research is that using need to support members, especially formulating key results motivate work toward same mission.

Язык: Английский

---