[go: up one dir, main page]
More Web Proxy on the site http://driver.im/ skip to main content
research-article

Quantitatively measuring a large-scale agile transformation

Published: 01 July 2016 Publication History

Abstract

We provide a quantitative metrics model to evaluate the impact of an agile and lean transformation.We propose eight rigorously described metrics within that model.We establish and apply the model in a large international telecommunication organization with 350 employees in two sites.Our findings show significant improvement in six of the eight metrics whereas one metric showed deteriorated results. Context: Agile software development continues to grow in popularity and is being adopted by more and more organizations. However, there is a need for empirical evidence on the impact, benefits and drawbacks of an agile transformation in an organization since the cost for such a transformation in terms of money, disrupted working routines and quality of development can become considerable. Currently, such evidence exists in the form of success stores and case studies, mostly of qualitative nature.Objective: Provide a metrics model to quantitatively measure the impact of an agile transformation in a software development organization.Method: The metrics model was elicited with the use of the Goal Question Metric approach.Results: A quantitative metrics model containing eight rigorously described metrics is presented and followed by its application to evaluate an agile and lean transformation in a large international telecommunication organization with 350 employees in two sites.Conclusions: The metrics model was sensitive to the changes that occurred in the organization and revealed significant improvements in six of the eight metrics and a deterioration in one of the metrics.

References

[1]
ACM Digital Library. www.dl.acm.org/.
[2]
Agile Alliance. Agile Manifesto. www.agilemanifesto.org/.
[3]
Agile Journal. www.agilejournal.com/.
[4]
D.J. Anderson, Prentice Hall, 2004.
[5]
V.R. Basili, G. Caldiera, H.D. Rombach, The goal question metric approach, Wiley, 1994.
[6]
V.R. Basili, H.D. Rombach, The tame project: towards improvement-oriented software environments, IEEE Trans. Softw. Eng., 14 (1988) 758-773.
[7]
B.W. Boehm, North-Holland Pub. Co, 1978.
[8]
L.C. Briand, S. Morasca, V.R. Basili, Property-based software engineering measurement, IEEE Trans. Softw. Eng, 22 (1996) 68-86.
[9]
Cloud Software Programme, 2013. Cloud Software Finland.
[10]
A. Cockburn, What engineering has in common with manufacturing and why it matters, J. Defence Softw. Eng, 20 (2006) 4-7.
[11]
M. Cohn, Addison-Wesley Professional, 2009.
[12]
G. Concas, M. Marchesi, G. Destefanis, R. Tonelli, An empirical study of software metrics for assessing the phases of an agile project, Int. J. Softw. Eng. Knowl. Eng., 22 (2012) 525-548.
[13]
P. Deemer, G. Benefield, C. Larman, B. Vodde, The Scrum Primer-A Lightweight Guide to the Theory and Practice of Scrum, 2012.
[14]
G. Destefanis, S. Counsell, G. Concas, T. Roberto, Software metrics in agile software: an empirical study, Springer International Publishing, 2014.
[15]
T. Dingsøyr, T. Fægri, J. Itkonen, What is large in large-scale? A taxonomy of scale for agile software development, in: Product-Focused Software Process Improvement (PROFES ), Springer International Publishing, 2014, pp. 273-276.
[16]
T. Dingsøyr, N.B. Moe, Research challenges in large-scale agile software development, SIGSOFT Softw. Eng. Notes, 38 (2013) 38-39.
[17]
R.G. Dromey, A model for software product quality, IEEE Trans. Softw. Eng., 21 (1995) 146-162.
[18]
Y. Dubinsky, D. Talby, O. Hazzan, A. Keren, Agile metrics at the Israeli Air Force, IEEE, 2005.
[19]
T. Dybå, T. Dingsøyr, Empirical studies of agile software development: a systematic review, Inf. Softw. Technol., 50 (2008) 833-859. http://dx.doi.org/10.1016/j.infsof.2008.01.006
[20]
C. Ebert, P. Abrahamsson, N. Oza, Lean software development, IEEE Softw., 29 (2012) 22-25.
[21]
T. Gilb, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, USA, 1988.
[22]
D. Hartmann, R. Dymond, Appropriate agile measurement: using metrics and diagnostics to deliver business value, IEEE Computer Society, 2006.
[23]
O. Hazzan, Y. Dubinsky, Agile software engineering, Springer, Berlin, 2008.
[24]
V. Heikkilä, M. Paasivaara, C. Lassenius, C. Engblom, Continuous release planning in a large-scale scrum development organization at Ericsson, Springer-Verlag, Berlin, Heidelberg, 2013.
[25]
IEEE. IEEE Xplore Digital Library. www.ieeexplore.ieee.org/.
[26]
ISO, ISO 9004:2000, Quality Management Systems-Guidelines for Performance Improvements, International Organisation for Standardization, 2000.
[27]
ISO, ISO 9126-1:2001, Software Engineering-Product quality, Part 1: Quality Model, International Organisation for Standardization, 2001.
[28]
ISO/IEC, ISO/IEC 25010-Systems and software Engineering-Systems and Software Quality Requirements and Evaluation (SQuaRE)-System and Software Quality Models, ISO/IEC, 2010.
[29]
C. Kaner, W.P. Bond, Software engineering metrics: what do they measure and how do we know?, IEEE CS Press, 2004.
[30]
B.A. Kitchenham, Blackwell Publishers, Inc., Cambridge, MA, USA, 1996.
[31]
K. Korhonen, Evaluating the impact of an agile transformation: a longitudinal case study in a distributed context, Softw. Qual. J., 21 (2013) 599-624.
[32]
K. Korhonen, Migrating defect management from waterfall to agile software development in a large-scale multi-site organization: a case study, Springer, Berlin, Heidelberg, 2014.
[33]
D. Leffingwell, Addison-Wesley Professional, 2007.
[34]
J. Li, N.B. Moe, T. Dybå, New York, New York, USA, 2010.
[35]
J.A. McCall, P.K. Richards, W.G. F., Factors in Software Quality. Concept and Definitions of Software Quality., 1977.
[36]
A. Meneely, B. Smith, L. Williams, Validating software metrics: a spectrum of philosophies, ACM Trans. Softw. Eng. Methodol., 21 (2013) 24:1-24:28.
[37]
Mikkonen, K., Seikola, M., Jouppila, M., Christian, E., 2012. How We Learn to Stop Worrying and Live with the Uncertainties? https://www.cloudsoftwareprogram.org/results/deliverables-and-other-reports/i/27891/1941/ericsson-journey-of-change.
[38]
E. Parnell-Klabo, Introducing lean principles with agile practices at a fortune 500 company, IEEE Computer Society, Washington, DC, USA, 2006.
[39]
K. Petersen, An empirical study of lead-times in incremental and agile software development, Springer-Verlag, Berlin, Heidelberg, 2010.
[40]
K. Petersen, C. Wohlin, The effect of moving from a plan-driven to an incremental software development approach with agile practices, Empirical Softw. Eng., 15 (2010) 654-693.
[41]
K. Petersen, C. Wohlin, Measuring the flow in lean software development, Softw.: Pract. Exp., 41 (2011) 975-996.
[42]
D.G. Reinertsen, Celeritas Publishing, 2009.
[43]
P. Rodríguez, J. Markkula, M. Oivo, K. Turula, Survey on agile and lean usage in Finnish software industry, ACM, New York, NY, USA, 2012.
[44]
M. Rönkkö, A. Järvi, M.M. Mäkelä, Measuring and comparing the adoption of software process practices in the software product industry, Springer, Berlin, Heidelberg, 2012.
[45]
D.I. Sjøberg, A. Johnsen, J. Solberg, Quantifying the effect of using Kanban versus Scrum: a case study, IEEE Softw., 29 (2012) 47-53. http://doi.ieeecomputersociety.org/10.1109/MS.2012.110
[46]
D. Šmite, N.B. Moe, P.J. Ågerfalk, Springer-Verlag, Berlin, Heidelberg, 2010.
[47]
Springer. Springer Link. www.link.springer.com/.
[48]
M. Staron, W. Meding, Monitoring bottlenecks in agile and lean software development projects-a method and its industrial use, in: LNCS, Vol. 6759, Springer, Berlin, Heidelberg, 2011, pp. 3-16.
[49]
The World Café. http://www.theworldcafe.com/method.html.
[50]
C. Wohlin, P. Ruenson, M. Höst, M.C. Ohlsson, B. Regnell, A. Wesslén, Springer, 2012.

Cited By

View all
  • (2022)Exploring the challenges and benefits for scaling agile project management to large projects: a reviewRequirements Engineering10.1007/s00766-021-00363-327:1(117-134)Online publication date: 1-Mar-2022
  • (2020)Agile Project Management Challenges and Mapping SolutionsProceedings of the 3rd International Conference on Software Engineering and Information Management10.1145/3378936.3378949(123-129)Online publication date: 12-Jan-2020
  • (2018)Scaling agile in large organizationsJournal of Software: Evolution and Process10.1002/smr.195430:10Online publication date: 17-Oct-2018
  • Show More Cited By

Recommendations

Comments

Please enable JavaScript to view thecomments powered by Disqus.

Information & Contributors

Information

Published In

cover image Journal of Systems and Software
Journal of Systems and Software  Volume 117, Issue C
July 2016
658 pages

Publisher

Elsevier Science Inc.

United States

Publication History

Published: 01 July 2016

Author Tags

  1. Agile
  2. Metrics
  3. Transformation

Qualifiers

  • Research-article

Contributors

Other Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

  • Downloads (Last 12 months)0
  • Downloads (Last 6 weeks)0
Reflects downloads up to 13 Dec 2024

Other Metrics

Citations

Cited By

View all
  • (2022)Exploring the challenges and benefits for scaling agile project management to large projects: a reviewRequirements Engineering10.1007/s00766-021-00363-327:1(117-134)Online publication date: 1-Mar-2022
  • (2020)Agile Project Management Challenges and Mapping SolutionsProceedings of the 3rd International Conference on Software Engineering and Information Management10.1145/3378936.3378949(123-129)Online publication date: 12-Jan-2020
  • (2018)Scaling agile in large organizationsJournal of Software: Evolution and Process10.1002/smr.195430:10Online publication date: 17-Oct-2018
  • (2017)Group development and group maturity when building agile teamsJournal of Systems and Software10.1016/j.jss.2016.11.024124:C(104-119)Online publication date: 1-Feb-2017

View Options

View options

Media

Figures

Other

Tables

Share

Share

Share this Publication link

Share on social media