Author:
Sato Danilo,Bassi Dairton,Bravo Mariana,Goldman Alfredo,Kon Fabio
Abstract
Abstract
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.
Publisher
Springer Science and Business Media LLC
Reference42 articles.
1. Sakata Akinori. Niko-niko calendar website. http://www.geocities.jp/ 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.
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. http://agilemanifesto.org, Jul. 2006.
Cited by
3 articles.
订阅此论文施引文献
订阅此论文施引文献,注册后可以免费订阅5篇论文的施引文献,订阅后可以查看论文全部施引文献