Communities of practice in a large distributed agile software development organization – Case Ericsson
Reads0
Chats0
TLDR
A large organization within Ericsson with 400 persons in 40 Scrum teams at three sites adopted the use of Communities of Practice (CoP) as part of their transformation from a traditional plan-driven organization to lean and agile.Abstract:
Context: Communities of practice—groups of experts who share a common interest or topic and collectively want to deepen their knowledge—can be an important part of a successful lean and agile adoption in particular in large organizations. Objective: In this paper, we present a study on how a large organization within Ericsson with 400 persons in 40 Scrum teams at three sites adopted the use of Communities of Practice (CoP) as part of their transformation from a traditional plan-driven organization to lean and agile. Methods: We collected data by 52 semi-structured interviews on two sites, and longitudinal non-participant observation of the transformation during over 20 site visits over a period of two years. Results: The organization had over 20 CoPs, gathering weekly, bi-weekly or on a need basis. CoPs had several purposes including knowledge sharing and learning, coordination, technical work, and organizational development. Examples of CoPs include Feature Coordination CoPs to coordinate between teams working on the same feature, a Coaching CoP to discuss agile implementation challenges and successes and to help lead the organizational continuous improvement, an end-to-end CoP to remove bottlenecks from the flow, and Developers CoPs to share good development practices. Success factors of well-functioning CoPs include having a good topic, passionate leader, proper agenda, decision making authority, open community, supporting tools, suitable rhythm, and cross-site participation when needed. Organizational support include creating a supportive atmosphere and providing a suitable infrastructure for CoPs. Conclusions: In the case organization, CoPs were initially used to support the agile transformation, and as part of the distributed Scrum implementation. As the transformation progressed, the CoPs also took on the role of supporting continuous organizational improvements. CoPs became a central mechanism behind the success of the large-scale agile implementation in the case organization that helped mitigate some of the most pressing problems of the agile transformation. 2014 The Authors. Published by Elsevier B.V. This is an open access article under the CC BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/3.0/).read more
Citations
More filters
Journal ArticleDOI
Exploring software development at the very large-scale: a revelatory case study and research agenda for agile method adaptation
TL;DR: An interpretative revelatory case study on one of the largest software development programmes in Norway shows how agile methods were adapted and complemented with practices from traditional methods to handle the scale.
Journal ArticleDOI
Large-scale agile transformation at Ericsson: a case study
TL;DR: How Ericsson introduced agile in a new R&D product development program developing a XaaS platform and a related set of services, while simultaneously scaling it up aggressively is reported.
Journal ArticleDOI
Scaling agile in large organizations: Practices, challenges, and success factors
TL;DR: Company culture, prior agile and lean experience, management support, and value unification were found to be key success factors during the action research process, and resistance to change, an overly aggressive roll‐out time frame, quality assurance concerns, and integration into preexisting nonagile business processes were found.
Journal ArticleDOI
Coordination Challenges in Large-Scale Software Development: A Case Study of Planning Misalignment in Hybrid Settings
TL;DR: This case study within a large software development unit of 13 teams at a global enterprise software company explores how and why a combination of traditional planning on an inter-team level and agile development on a team level can result in ineffective coordination.
Journal ArticleDOI
Software teams and their knowledge networks in large-scale software development
TL;DR: It is suggested that, along with investments into training programs, software companies should also cultivate a networking culture to strengthen their social capital, a known driver of better performance in large-scale software development projects.
References
More filters
Book
Case Study Research: Design and Methods
TL;DR: In this article, buku ini mencakup lebih dari 50 studi kasus, memberikan perhatian untuk analisis kuantitatif, membahas lebah lengkap penggunaan desain metode campuran penelitian, and termasuk wawasan metodologi baru.
Book
Qualitative Data Analysis: An Expanded Sourcebook
TL;DR: This book presents a step-by-step guide to making the research results presented in reports, slideshows, posters, and data visualizations more interesting, and describes how coding initiates qualitative data analysis.
Journal ArticleDOI
Qualitative Evaluation And Research Methods
TL;DR: The Nature of Qualitative Inquiry Theoretical Orientations Particularly Appropriate Qualitative Applications as mentioned in this paper, and Qualitative Interviewing: Qualitative Analysis and Interpretation Enhancing the quality and credibility of qualitative analysis and interpretation.
Book
Communities of Practice: Learning, Meaning, and Identity
TL;DR: Identity in practice, modes of belonging, participation and non-participation, and learning communities: a guide to understanding identity in practice.
Journal Article
Qualitative evaluation and research methods
TL;DR: The Nature of Qualitative Inquiry Theoretical Orientations Particularly Appropriate Qualitative Applications as mentioned in this paper, and Qualitative Interviewing: Qualitative Analysis and Interpretation Enhancing the quality and credibility of qualitative analysis and interpretation.