Skip to main content

Experiences tracking agile projects: an empirical study


In this article, we gather results from several projects we conducted recently that use some kind of agile method. We analyze both academic and governmental software development projects, some of them using agile methods since the beginning and others in which agile methods were introduced afterwards. Our main goals are to classify the different projects, and to analyze the collected data and discover which metrics are best suited to support tracking an agile project.

We use both quantitative and qualitative methods, obtaining data from the source code, from the code repository, and from the feedback received from surveys and interviews held with the team members. We use various kinds of metrics such as lines of code, number of tests, cyclomatic complexity, number of commits, as well as combinations of these.

In this article, we describe in detail the projects, the metrics, the obtained results, and their analysis from our main goals standpoint, providing guidelines for the use of metrics to track an agile software development project.


  1. Sakata Akinori. Niko-niko calendar website. nikonikocalendar/index_en.html, Jul. 2006.

  2. Victor R. Basili, Lionel C. Briand, and Walcélio L. Melo. A validation of object-oriented designmetrics as quality indicators.IEEE Transactions on Software Engineering, 22(10):751–761, 1996.

    Article  Google Scholar 

  3. Kent Beck.Extreme Programming Explained: Embrace Change. Addison-Wesley, 1st edition, 1999.

  4. Kent Beck and Cynthia Andres.Extreme Programming Explained: Embrace Change. Addison-Wesley, 2nd edition, 2004.

  5. Kent Beck et al. Manifesto for agile software development., Jul. 2006.

  6. Barry Boehm and Richard Turner.Balancing Agility and Discipline: A Guide for the Perplexed. Addison-Wesley, 2003.

  7. Barry Boehm and Richard Turner. Using risk to balance agile and plan-driven methods. InIEEE Computer, volume 36, pages 57–66, 2003.

  8. Piergiuliano Bossi. Extreme Programming applied: a case in the private banking domain. InProceedings of OOP, Munich, 2003.

  9. S.R. Chidamber and C.F. Kemerer. A metrics suite for object oriented design.IEEE Transactions on Software Engineering, 20(6):476–493, 1994.

    Article  Google Scholar 

  10. Alistair Cockburn.Agile Software Development. Addison-Wesley, 2002.

  11. Alistair Cockburn.Crystal Clear: A Human-Powered Methodology for Small Teams. Addison-Wesley Professional, 2004.

  12. Yael Dubinsky, David Talby, Orit Hazzan, and Arie Keren. Agile metrics at the israeli air force. InAgile 2005 Conference, pages 12–19, 2005.

  13. Martin Fowler. Continuous integration., Jul. 2006.

  14. Martin Fowler, Kent Beck, John Brant, William Opdyke, and Don Roberts.Refactoring: Improving the Design of Existing Code. Addison-Wesley, 1999.

  15. Alexandre Freire da Silva, Fabio Kon, and Cicero Torteli. XP south of the equator: An experience implementing XP in Brazil. InProceedings of the 6th International Conference on Extreme Programming and Agile Processes in Software Engineering (XP’2005), pages 10–18, 2005.

  16. Alfredo Goldman, Fabio Kon, Paulo J. S. Silva, and Joe Yoder. Being extreme in the classroom: Experiences teaching XP.Journal of the Brazilian Computer Society, 10(2):1–17, 2004.

    Article  Google Scholar 

  17. Eliyahu M. Goldratt.The Haystack Syndrome: Sifting Information Out of the Data Ocean. North River Press, 1991.

  18. Tibor Gyimóthy, Rudolf Ferenc, and István Siket. Empirical validation of object-oriented metrics on open source software for fault prediction.IEEE Transactions on Software Engineering, 31(10):897–910, 2005.

    Article  Google Scholar 

  19. Deborah Hartmann and Robin Dymond. Appropriate agile measurements: Using metrics and diagnostics to deliver business value. InAgile 2006 Conference, pages 126–131, 2006.

  20. Jim Highsmith. Messy, exciting, and anxietyridden: Adaptive software development. InAmerican Programmer, volume 10, 1997.

  21. Ronald E. Jeffries, Ann Anderson, and Chet Hendrickson.Extreme Programming Installed. Addison-Wesley, 2000.

  22. Capers Jones.Software Assessments, Benchmarks, and Best Practices. AddisonWesley, 2000.

  23. Mira Kajko-Mattsson, Ulf Westblom, Stefan Forssander, Gunnar Andersson, Mats Medin, Sari Ebarasi, Tord Fahlgren, Sven-Erik Johansson, Stefan Törnquist, and Margareta Holmgren. Taxonomy of problem management activities. InProceedings of the Fifth European Conference on Software Maintenance and Reengineering, pages 1–10, 2001.

  24. Norman L. Kerth.Project Retrospectives: A Handbook for Team Reviews. Dorset House Publishing Company, 2001.

  25. William Krebs. Turning the knobs: A coaching pattern for XP through agile metrics.XP/Agile Universe 2002, LNCS 2418:60–69, 2002.

  26. Wei Li and Sallie Henry. Object oriented metrics that predict maintainability.J. Systems and Software, 23:111–122, 1993.

    Article  Google Scholar 

  27. Kim Man Lui and Keith C.C. Chan. Test driven development and software process improvement in china. InProceedings of the 5th International Conference on Extreme Programming and Agile Processes in Software Engineering (XP 2004), volume 3092 ofLecture Notes on Computer Science, pages 219–222, 2004.

  28. C. Mann and F. Maurer. A case study on the impact of scrum on overtime and customer satisfaction. InAgile 2005 Conference, pages 70–79, 2005.

  29. Thomas J. McCabe and Arthur H. Watson. Software complexity.Crosstalk: Journal of Defense Software Engineering, 7:5–9, 1994.

    Google Scholar 

  30. Jacques Morel et al. Xplanner website. http://, Jul. 2006.

  31. Roger A. Müller. Extreme programming in a university project. InProceedings of the 5th International Conference on Extreme Programming and Agile Processes in Software Engineering (XP 2004), volume 3092 ofLecture Notes on Computer Science, pages 312–315, 2004.

  32. Stephen R Palmer and John M. Felsing.A Practical Guide to Feature Driven Development. Prentice Hall, 2002.

  33. Mary Poppendieck and Tom Poppendieck.Lean Software Development: An Agile Toolkit for Software Development Managers. Addison-Wesley, 2003.

  34. Lawrence H. Putnam and Ware Meyers.Measures For Excellence: Reliable Software On Time, Within Budget. Yourdon Press Computing Series, 1992.

  35. Ken Schwaber andMike Beedle.Agile Software Development with Scrum. Alan R. Apt, 2001.

  36. Carolyn B. Seaman. Qualitative methods in empirical studies of software engineering.IEEE Transactions on Software Engineering, 25:557–572, 1999.

    Article  Google Scholar 

  37. Jennifer Stapleton.DSDM: A framework for business centered development. Addison-Wesley Professional, 1997.

  38. Ramanath Subramanyam and M.S. Krishnan. Empirical analysis of CK metrics for object-oriented design complexity: Implications for software defects.IEEE Transactions on Software Engineering, 29(4):297–310, 2003.

    Article  Google Scholar 

  39. Abbas Tashakkori and Charles Teddlie.Mixed Methodology: Combining Qualitative and Quantitative Approaches. Sage Publications, 1998.

  40. Laurie Williams.Pair Programming Illuminated. Addison-Wesley Professional, 2002.

  41. Laurie Williams, William Krebs, Lucas Layman, and Annie I. Antón. Toward a framework for evaluating Extreme Programming. In8th International Conference on Empirical Assessment in Software Engineering (EASE ’04), pages 11–20, 2004.

  42. Laurie Williams, Lucas Layman, and William Krebs. Extreme Programming evaluation framework for object-oriented languages — version 1.4. Technical report, North Carolina State University Department of Computer Science, 2004.

Download references

Author information

Authors and Affiliations


Rights and permissions

Open Access This article is distributed under the terms of the Creative Commons Attribution 2.0 International License ( ), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.

Reprints and permissions

About this article

Cite this article

Sato, D., Bassi, D., Bravo, M. et al. Experiences tracking agile projects: an empirical study. J Braz Comp Soc 12, 45–64 (2006).

Download citation

  • Issue Date:

  • DOI: