BazEkon - Biblioteka Główna Uniwersytetu Ekonomicznego w Krakowie

BazEkon home page

Meny główne

van Heeringen Harold, Prins Theo, van Gorp Edwin
Productivity Measurement of Agile Teams - Overcoming the Issues with Non-Functional Requirements
Roczniki Kolegium Analiz Ekonomicznych / Szkoła Główna Handlowa, 2016, nr 43, s. 117-133, rys., tab., wykr., bibliogr. 6 poz.
Słowa kluczowe
Outsourcing, Benchmarking, Oprogramowanie, Konkurencyjność
Outsourcing, Benchmarking, Software, Competitiveness
Nowadays, as the software industry is slowly becoming more mature, software measurement and performance measurement are becoming increasingly important. Organizations need to know their productivity and competitiveness in software development projects for various reasons. In many software development contracts, targets are set for the suppliers to reach. These targets are based on software metrics like productivity, speed of delivery and software quality. In order to check if the targets are reached, it is necessary to measure the functional size of the software product that is delivered and also the functional size of the software development project that is carried out, as there is usually a difference between these two sizes. To be able to use the functional size in contracts, it must be measured in an objective, repeatable, verifiable and therefore defensible way. That being the case, the industry's best practice is to use an ISO/IEC standard for functional size measurement, e.g. Nesma, COSMIC or IFPUG function points. However, these methods only measure the functional user requirements from the total software requirements to be delivered. In activities like project estimation and productivity measurement, the influence of the non-functional requirements is expressed in the Project Delivery Rate (PDR) which is expressed in effort hours per function point. If more than the average number of non-functional requirements need to be realized in a project (or more severe non-functional requirements), the PDR used should also be higher. In the industry it is customary to set productivity targets based on an average (or calibrated) influence of non-functional requirements and this works quite fine in traditional software projects. In software development projects that are executed in an agile way, this is not always the case. When working agile, there are forces that influence the traditional way of performance measurement significantly, resulting in a number of serious issues. In this paper these issues are explained and a method to overcome these issues is proposed.(author's abstract)
Dostępne w
Biblioteka Szkoły Głównej Handlowej w Warszawie
Biblioteka Główna Uniwersytetu Ekonomicznego w Poznaniu
Pełny tekst
  1. Beck K., Manifesto for Agile Software Development, Agile Alliance 2001, retrieved 14/06/2010.
  2. Bundshuh M., Dekkers C., The IT Measurement Compendium, Estimating and Benchmarking Success with Functional Size Measurement, Spinger, ISBN: 978-3-540- 68187-8, p. 313.
  3. Early Function Point Counting, early-function-point-counting/
  4. International Software Benchmarking Standards Group (ISBSG) New Developments & Enhancements R13, released February 22015,
  5. ISO/IEC 24570:2005, Software Engineering - NESMA Function Size Measurement Method Version 2.1, Definitions and Counting Guidelines for the Application of Function Point Analysis, ISBN: 978-90-76258-19-5.
  6. Letouzey J.-L., The SQALE Method for Evaluating Technical Debt, 3 rd International Workshop on Managing Technical Debt, Zurich, 9-12.06.2012.
Cytowane przez
Udostępnij na Facebooku Udostępnij na Twitterze Udostępnij na Google+ Udostępnij na Pinterest Udostępnij na LinkedIn Wyślij znajomemu