kth.sePublications KTH
Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Barriers to deploying agile methods in established product development organizations
KTH, School of Electrical Engineering and Computer Science (EECS), Computer Science, Network and Systems Engineering.ORCID iD: 0000-0002-3590-6932
KTH, School of Electrical Engineering and Computer Science (EECS), Computer Science, Network and Systems Engineering.ORCID iD: 0000-0003-0724-2283
2026 (English)In: IEEE Engineering Management Review, ISSN 0360-8581, E-ISSN 1937-4178, Vol. 54, no 1, p. 52-71Article in journal (Refereed) Published
Abstract [en]

This research presents four barriers to deploying agile methods in established R&D organizations that develop complex, mechatronic products. While prior research has identified success factors and common challenges when implementing agile methods, their adaptation in established multidisciplinary product development work, where coordination across diverse engineering domains is crucial, remains underexplored. Drawing on a qualitative case study based on two years of interviews and discussion meetings, we have studied barriers that emerge when deploying agile methods in an organization where legacy practices and organizational logics conflict with the new methods.

Our findings highlight twelve challenges that are categorized into four key barriers: complex dependencies & coordination, existing structures, new application & setting, and ambiguous values & benefits. The study thus offers insights into the barriers of changing workways in established R&D organizations and makes a threefold contribution: (1) identifying four barriers to agile adoption, (2) suggesting future research questions, and (3) providing practical advice for managers planning to deploy agile methods or other technological or methodological transformations that challenge the status quo. Managers should not assume immediate benefits, but instead be prepared to adapt the agile methods to their specific context. They should listen to those perceived as change averse and consider educating ‘boundary spanners’, that is, individuals who bridge engineering knowledge with method know-how. These roles help evaluate dependencies for coordination, identify rigid structures and articulate potential benefits to bridge the gap between the old and the new.

Place, publisher, year, edition, pages
Institute of Electrical and Electronics Engineers (IEEE) , 2026. Vol. 54, no 1, p. 52-71
Keywords [en]
Agile methods, Barriers, Challenges, Complex mechatronic products, Product development, R&D organization
National Category
Business Administration
Research subject
Industrial Economics and Management
Identifiers
URN: urn:nbn:se:kth:diva-372983DOI: 10.1109/emr.2025.3588930ISI: 001715214300012Scopus ID: 2-s2.0-105012549706OAI: oai:DiVA.org:kth-372983DiVA, id: diva2:2014144
Note

QC 20260320

Available from: 2025-11-17 Created: 2025-11-17 Last updated: 2026-05-29Bibliographically approved

Open Access in DiVA

No full text in DiVA

Other links

Publisher's full textScopus

Authority records

Linse, CharlottaLilliesköld, Joakim

Search in DiVA

By author/editor
Linse, CharlottaLilliesköld, Joakim
By organisation
Network and Systems Engineering
In the same journal
IEEE Engineering Management Review
Business Administration

Search outside of DiVA

GoogleGoogle Scholar

doi
urn-nbn

Altmetric score

doi
urn-nbn
Total: 52 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf