Why are industrial agile teams using metrics and how do they use them?

5th International Workshop on Emerging Trends in Software Metrics, WETSoM 2014 - Proceedings

Volumn , Issue , 2014, Pages 23-29

  Kupiainen, Eetu ^a   Mäntylä, Mika V ^a   Itkonen, Juha ^a  

^a AALTO UNIVERSITY   (Finland)

Author keywords

Agile software development; Measurement; Metrics

Indexed keywords

ITERATIVE METHODS; MEASUREMENTS; SOFTWARE DESIGN;

AGILE DEVELOPMENT; AGILE DEVELOPMENT METHODS; AGILE SOFTWARE DEVELOPMENT; ITERATION PLANNING; METRICS; PROCESS IMPROVEMENT; RESEARCH TOPICS; SYSTEMATIC LITERATURE REVIEW;

SOFTWARE ENGINEERING;

EID: 84974597136     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/2593868.2593873     Document Type: Conference Paper

References (43)

1. K. Beck, M. Beedle, A. van Bennekum, A. Cockburn, W. Cunningham, M. Fowler, J. Grenning, J. Highsmith, A. Hunt, R. Jeffries, J. Kern, B. Marick, R. C. Martin, S. Mellor, K. Schwaber, J. Sutherland, and D. Thomas. Manifesto for agile software development.
2. C. Catal and B. Diri. A systematic review of software fault prediction studies. Expert Systems with Applications, 36(4):7346-7354, 2009.
3. T.-H. Cheng, S. Jansen, and M. Remmers. Controlling and monitoring agile software development in three dutch product software companies. In Proceedings of the 2009 ICSE Workshop on Software Development Governance, SDG 2009, pages 29-35, Vancouver, BC, 2009.
4. D. Cruzes and T. Dyba. Recommended steps for thematic synthesis in software engineering. In Empirical Software Engineering and Measurement (ESEM), 2011 International Symposium on, pages 275-284, 2011.
5. P. S. M. dos Santos, A. Varella, C. R. Dantas, and D. B. Ao Borges. Visualizing and managing technical debt in agile development: An experience report. In Agile Processes in Software Engineering and Extreme Programming, volume 149 of Lecture Notes in Business Information Processing, pages 121-134, 2013.
6. Y. Dubinsky, D. Talby, O. Hazzan, and A. Keren. Agile metrics at the israeli air force. In Proceedings-AGILE Confernce 2005, volume 2005, pages 12-19, Denver, CO, 2005.
7. T. Dyba and T. Dingsoyr. Empirical studies of agile software development: A systematic review. Information and Software Technology, 50(9):833-859, Aug. 2008.
8. A. Elssamadisy and G. Schalliol. Recognizing and responding to "bad smells" in extreme programming. In Proceedings-International Conference on Software Engineering, pages 617-622, Orlando, FL, 2002.
9. P. Green. Measuring the impact of scrum on product development at adobe systems. In Proceedings of the Annual Hawaii International Conference on System Sciences, Koloa, Kauai, HI, 2011.
10. D. Greening. Enterprise scrum: Scaling scrum to the executive level. In Proceedings of the Annual Hawaii International Conference on System Sciences, Koloa, Kauai, HI, 2010.
11. D. Hartmann and R. Dymond. Appropriate agile measurement: using metrics and diagnostics to deliver business value. In Agile Conference, 2006, pages 6 pp.-134, 2006.
12. N. Haugen. An empirical study of using planning poker for user story estimation. In Proceedings-AGILE Conference, 2006, volume 2006, pages 23-31, Minneapolis, MN, 2006.
13. P. Hodgetts. Refactoring the development process: Experiences with the incremental adoption of agile practices. In Proceedings of the Agile Development Conference, ADC 2004, pages 106-113, Salt Lake City, UT, 2004.
14. P. Hodgkins and L. Hohmann. Agile program management: Lessons learned from the verisign managed security services team. In Proceedings-AGILE 2007, pages 194-199, Washington, DC, 2007.
15. N. Hong, J. Yoo, and S. Cha. Customization of scrum methodology for outsourced e-commerce projects. In Proceedings-Asia-Pacific Software Engineering Conference, APSEC, pages 310-315, Sydney, NSW, 2010.
16. ISO/IEC. ISO/IEC 25010-Systems and software engineering-Systems and software Quality Requirements and Evaluation (SQuaRE)-System and software quality models. Technical report, 2010.
17. C. Jakobsen and T. Poppendieck. Lean as a scrum troubleshooter. In Proceedings-2011 Agile Conference, Agile 2011, pages 168-174, Salt Lake City, UT, 2011.
18. A. Janus, R. Dumke, A. Schmietendorf, and J. Jager. The 3c approach for agile quality assurance. In Emerging Trends in Software Metrics (WETSoM), 2012 3rd International Workshop on, pages 9-13, 2012.
19. B. Kitchenham. Procedures for performing systematic reviews. Keele, UK, Keele University, 33:2004, 2004.
20. B. Kitchenham. What's up with software metrics?-a preliminary mapping study. Journal ofSystems and Software, 83(1):37-51, Jan. 2010.
21. B. Kitchenham and P. Brereton. A systematic review of systematic review process research in software engineering. Information and Software Technology, 55(12):2049-2075, 2013.
22. K. Korhonen. Migrating defect management from waterfall to agile software development in a large-scale multi-site organization: A case study. In P. Abrahamsson, M. Marchesi, and F. Maurer, editors, Agile Processes in Software Engineering and Extreme Programming, volume 31 of Lecture Notes in Business Information Processing, pages 73-82. Springer Berlin Heidelberg, 2009.
23. J. Landis and G. Koch. The measurement of observer agreement for categorical data. Biometrics, 33(1):159-174, 1977.
24. V. Mahnic and N. Zabkar. Measuring progress of scrum-based software projects. Electronics and Electrical Engineering, 18(8):73-76, 2012.
25. P. Middleton, P. Taylor, A. Flaxel, and A. Cookson. Lean principles and techniques for improving the quality and productivity of software development projects: A case study. International Journal of Productivity and Quality Management, 2(4):387-403, 2007.
26. S. Mujtaba, R. Feldt, and K. Petersen. Waste and lead time reduction in a software product customization process with value stream maps. In Proceedings of the Australian Software Engineering Conference, ASWEC, pages 139-148, Auckland, 2010.
27. C. Patel, M. Lycett, R. Macredie, and S. de Cesare. Perceptions of agility and collaboration in software development practice. In System Sciences, 2006. HICSS '06. Proceedings of the 39th Annual Hawaii International Conference on, volume 1, pages 10c-10c, 2006.
28. K. Petersen. A palette of lean indicators to detect waste in software maintenance: A case study. Lecture Notes in Business Information Processing, 111 LNBIP:108-122, 2012.
29. K. Petersen and C. Wohlin. The effect of moving from a plan-driven to an incremental software development approach with agile practices: An industrial case study. Empirical Software Engineering, 15(6):654-693, 2010.
30. K. Petersen and C. Wohlin. Software process improvement through the lean measurement (spi-leam) method. Journal of Systems and Software, 83(7):1275-1287, 2010. cited By (since 1996)6.
31. K. Petersen and C. Wohlin. Measuring the flow in lean software development. Software-Practice and Experience, 41(9):975-996, 2011.
32. R. Polk. Agile & kanban in coordination. In Proceedings-2011 Agile Conference, Agile 2011, pages 263-268, Salt Lake City, UT, 2011.
33. S. Purao and V. Vaishnavi. Product metrics for object-oriented systems. ACM Computing Surveys (CSUR), 35(2):191-221, 2003.
34. G. Seber. The Estimation of Animal Abundance and Related Parameters. Blackburn Press, 2002.
35. M. Seikola, H.-M. Loisa, and A. Jagos. Kanban implementation in a telecom product maintenance. In Proceedings-37th EUROMICRO Conference on Software Engineering and Advanced Applications, SEAA 2011, pages 321-329, Oulu, 2011.
36. B. Shen and D. Ju. On the measurement of agility in software process. Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), 4470 LNCS:25-36, 2007.
37. M. Staron and W. Meding. Monitoring bottlenecks in agile and lean software development projects-a method and its industrial use. Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), 6759 LNCS:3-16, 2011.
38. M. Staron, W. Meding, and B. Soderqvist. A method for forecasting defect backlog in large streamline software development projects and its industrial evaluation. Information and Software Technology, 52(10):1069-1079, 2010.
39. D. Talby and Y. Dubinsky. Governance of an agile software project. In Proceedings of the 2009 ICSE Workshop on Software Development Governance, SDG 2009, pages 40-45, Vancouver, BC, 2009.
40. D. Talby, O. Hazzan, Y. Dubinsky, and A. Keren. Reflections on reflection in agile software development. In Proceedings-AGILE Conference, 2006, volume 2006, pages 100-110, Minneapolis, MN, 2006.
41. V. Trapa and S. Rao. T3-tool for monitoring agile development. In Proceedings-AGILE Conference, 2006, volume 2006, pages 243-248, Minneapolis, MN, 2006.
42. J. Trimble and C. Webster. From traditional, to lean, to agile development: Finding the optimal software engineering cycle. In Proceedings of the Annual Hawaii International Conference on System Sciences, pages 4826-4833, Wailea, Maui, HI, 2013.
43. D. Tudor and G. Walter. Using an agile approach in a large, traditional organization. In Proceedings-AGILE Conference, 2006, volume 2006, pages 367-373, Minneapolis, MN, 2006.