TY - JOUR
T1 - Managing Cultural Variation in Software Process Improvement
T2 - a Comparison of Methods for Subculture Assessment
AU - Mûller, Sune Dueholm
AU - Kræmmergaard, Pernille
AU - Mathiassen, Lars
PY - 2009
Y1 - 2009
N2 - The scale and complexity of change in software process improvement (SPI) are considerable and managerial attention to organizational culture during SPI can therefore potentially contribute to successful outcomes. However, we know little about the impact of variations in organizational subculture on SPI initiatives. On this backdrop, we present an exploratory study of a large-scale SPI project in a Danish high-technology company, Terma. Two of its business units—Integrated Systems (ISY) and Airborne Systems (ASY)—followed similar approaches over a three-year period, but with quite different outcomes. While ISY reached capability maturity model integration (CMMI) level 2 as planned, ASY struggled to implement even modest improvements. To help explain these differences, we analyzed the underlying organizational culture within ISY and ASY using two different methods for subculture assessment. The study demonstrates how variations in culture across software organizations can have important implications for SPI outcomes. Furthermore, it provides insights into how software managers can practically assess subcultures to inform decisions about and help prepare plans for SPI initiatives.
AB - The scale and complexity of change in software process improvement (SPI) are considerable and managerial attention to organizational culture during SPI can therefore potentially contribute to successful outcomes. However, we know little about the impact of variations in organizational subculture on SPI initiatives. On this backdrop, we present an exploratory study of a large-scale SPI project in a Danish high-technology company, Terma. Two of its business units—Integrated Systems (ISY) and Airborne Systems (ASY)—followed similar approaches over a three-year period, but with quite different outcomes. While ISY reached capability maturity model integration (CMMI) level 2 as planned, ASY struggled to implement even modest improvements. To help explain these differences, we analyzed the underlying organizational culture within ISY and ASY using two different methods for subculture assessment. The study demonstrates how variations in culture across software organizations can have important implications for SPI outcomes. Furthermore, it provides insights into how software managers can practically assess subcultures to inform decisions about and help prepare plans for SPI initiatives.
KW - Exploratory embedded case study
KW - organizational change
KW - organizational culture
KW - software process improvement (SPI)
KW - Exploratory embedded case study
KW - organizational change
KW - organizational culture
KW - software process improvement (SPI)
U2 - 10.1109/TEM.2009.2013829
DO - 10.1109/TEM.2009.2013829
M3 - Journal article
SN - 0018-9391
VL - 56
SP - 584
EP - 599
JO - IEEE Transactions on Engineering Management
JF - IEEE Transactions on Engineering Management
IS - 4
ER -