Product Evaluation Through Contractor and In-House Metrics

Agile methods are gaining in popularity and have already become mainstream in software development due to their ability to produce new functionalities faster, and with higher customer satisfaction. Agile methods require different measurement practices compared to traditional ones. Effort estimation, progress monitoring, improving performance and quality are becoming important as valuable advice for project management. The project team is forced to make objective measures to minimise costs and risks with rising quality at the same time. In this paper, we merge two aspects of agile method evaluation (the contractor and the client view), propose AIM acronym and discuss two important concepts in order to perform objective measurements: “Agile Contractor Evaluation” (ACE) and “Agile In-House Metrics” (AIM). We examine what type of measurements should be conducted during agile software development methods and why.

[1]  Wasif Afzal,et al.  Using Faults-Slip-Through Metric as a Predictor of Fault-Proneness , 2010, 2010 Asia Pacific Software Engineering Conference.

[2]  Pekka Abrahamsson,et al.  Agile methods rapidly replacing traditional methods at Nokia: A survey of opinions on agile transformation , 2011, Inf. Softw. Technol..

[3]  Meghann L. Drury-Grogan Performance on agile teams: Relating iteration objectives and critical decisions to project management success factors , 2014, Inf. Softw. Technol..

[4]  Philip S. Taylor,et al.  Lean principles and techniques for improving the quality and productivity of software development projects: a case study , 2007 .

[5]  Mary Ann Lapham,et al.  Agile Metrics: Progress Monitoring of Agile Contractors , 2014 .

[6]  Bojana Dalbelo Basic,et al.  A systematic data collection procedure for software defect prediction , 2016, Comput. Sci. Inf. Syst..

[7]  Abdul Azim Abdul Ghani,et al.  On the Current Measurement Practices in Agile Software Development , 2013, ArXiv.

[8]  Indika Perera,et al.  Use of software metrics in agile software development process , 2015, 2015 Moratuwa Engineering Research Conference (MERCon).

[9]  E. Goldratt The Haystack Syndrome: Sifting Information Out of the Data Ocean , 1990 .

[10]  Ryan Polk Agile & Kanban In Coordination , 2011 .

[11]  Miroslaw Staron,et al.  Monitoring Bottlenecks in Agile and Lean Software Development Projects - A Method and Its Industrial Use , 2011, PROFES.

[12]  Kai Petersen,et al.  Waste and Lead Time Reduction in a Software Product Customization Process with Value Stream Maps , 2010, 2010 21st Australian Software Engineering Conference.

[13]  Claes Wohlin,et al.  Faults-slip-through - a concept for measuring the efficiency of the test process , 2006, Softw. Process. Improv. Pract..

[14]  Richard Lawrence,et al.  Three-way cultural change: introducing agile within two non-agile companies and a non-agile methodology , 2006, AGILE 2006 (AGILE'06).

[15]  Gary B. Wills,et al.  The Impact of Organization, Project and Governance Variables on Software Quality and Project Success , 2010, 2010 Agile Conference.

[16]  Howard Lei,et al.  A statistical analysis of the effects of Scrum and Kanban on software development projects , 2017 .

[17]  Deborah Hartmann,et al.  Appropriate agile measurement: using metrics and diagnostics to deliver business value , 2006, AGILE 2006 (AGILE'06).

[18]  Juanjuan Zang Agile Estimation with Monte Carlo Simulation , 2008, XP.

[19]  Bob Schatz,et al.  Primavera gets agile: a successful transition to agile development , 2005, IEEE Software.

[20]  Mika Mäntylä,et al.  Using metrics in Agile and Lean Software Development - A systematic literature review of industrial studies , 2015, Inf. Softw. Technol..

[21]  Brian Henderson-Sellers,et al.  A framework to support the evaluation, adoption and improvement of agile methods in practice , 2008, J. Syst. Softw..