Large-scale agile transformation at Ericsson: a case study

dc.contributorAalto-yliopistofi
dc.contributorAalto Universityen
dc.contributor.authorPaasivaara, Mariaen_US
dc.contributor.authorBehm, Benjaminen_US
dc.contributor.authorLassenius, Casperen_US
dc.contributor.authorHallikainen, Minnaen_US
dc.contributor.departmentDepartment of Computer Scienceen
dc.contributor.groupauthorProfessorship Lassenius Casperen
dc.contributor.organizationAalto Universityen_US
dc.contributor.organizationEricsson ABen_US
dc.date.accessioned2018-02-09T10:01:10Z
dc.date.available2018-02-09T10:01:10Z
dc.date.issued2018-10en_US
dc.description.abstractMany large organizations are adopting agile software development as part of their continuous push towards higher flexibility and shorter lead times, yet few reports on large-scale agile transformations are available in the literature. In this paper we report 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. The overarching goal for the R&D organization, distributed to five sites at two continents, was to achieve continuous feature delivery. This single case study is based on 45 semi-structured interviews during visits at four sites, and five observation sessions at three sites. We describe how the organization experimented with different set-ups for their tens of agile teams aiming for rapid end-to-end development: from component-based virtual teams to totally cross-functional, cross-component, cross-site teams. Moreover, we discuss the challenges the organization faced and how they mitigated them on their journey towards continuous and rapid software engineering. We present four lessons learned for large-scale agile transformations: 1) consider using an experimental approach to transformation, 2) consider implementing the transformation step-wise in complex large-scale settings, 3) team inter-changeability can be limited in a complex large-scale product — specialization might be needed, and 4) not using a common agile framework for the whole organization, in combination with insufficient common trainings and coaching may lead to a lack of common direction in the agile implementation. Further in-depth case studies on large-scale agile transformations, on customizing agile to large-scale settings, as well as on the use of scaling frameworks are needed.en
dc.description.versionPeer revieweden
dc.format.mimetypeapplication/pdfen_US
dc.identifier.citationPaasivaara, M, Behm, B, Lassenius, C & Hallikainen, M 2018, 'Large-scale agile transformation at Ericsson : a case study', Empirical Software Engineering, vol. 23, no. 5, pp. 2550–2596. https://doi.org/10.1007/s10664-017-9555-8en
dc.identifier.doi10.1007/s10664-017-9555-8en_US
dc.identifier.issn1382-3256
dc.identifier.issn1573-7616
dc.identifier.otherPURE UUID: 8b6d26ab-9759-4b87-839a-166e505e1024en_US
dc.identifier.otherPURE ITEMURL: https://research.aalto.fi/en/publications/8b6d26ab-9759-4b87-839a-166e505e1024en_US
dc.identifier.otherPURE FILEURL: https://research.aalto.fi/files/31393278/Paasivaara2018_Article_Large_scaleAgileTransformation.pdf
dc.identifier.urihttps://aaltodoc.aalto.fi/handle/123456789/29895
dc.identifier.urnURN:NBN:fi:aalto-201802091391
dc.language.isoenen
dc.publisherSpringer
dc.relation.ispartofseriesEmpirical Software Engineeringen
dc.relation.ispartofseriesVolume 23, issue 5, pp. 2550–2596en
dc.rightsopenAccessen
dc.subject.keywordAdopting agileen_US
dc.subject.keywordAgile software developmenten_US
dc.subject.keywordEnterprise agileen_US
dc.subject.keywordLarge-scale agileen_US
dc.subject.keywordScaling agileen_US
dc.titleLarge-scale agile transformation at Ericsson: a case studyen
dc.typeA1 Alkuperäisartikkeli tieteellisessä aikakauslehdessäfi
dc.type.versionpublishedVersion

Files

Original bundle

Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
Paasivaara2018_Article_Large_scaleAgileTransformation.pdf
Size:
1.69 MB
Format:
Adobe Portable Document Format