Agile Test Metrics (May2017) – This latest blog asks for inputs to our on-going study looking at what agile metrics you might want to use when automating software development, regression and acceptance testing. The study will use the “Goal-Question-Metrics” to develop a list of metrics that can be used to determine whether such testing has been satisfactorily accomplished and if the results are complete, comprehensive and acceptable relative to an organization’s mission.

Benchmark Report (July 2017) – As part of the benchmarking report we will issue in July of this year, we will breakdown our software productivity findings into 8 subdomains within both our telecommunications and web business applications domains. The telecommunications breakouts will include analytics, database and storage, infrastructure, networking, satellite, switching, transmission, and wireless systems. The web business breakouts will include analytics, brokerage, enterprise, financial, social networking, subscription, utilities, and web commerce. We will also divide our naval systems benchmarks within our defense sector into asea and ashore and space systems into ground and spaceborne in this forthcoming report. In total, we will provide benchmarks for 36 application domains starting with the next issue of our benchmarking report.

Agile Test Metrics (June 2017) – This technical note provides a shopping list of candidate agile test metrics. These metrics were defined using the “Goal-Question-Metric” paradigm to address the key questions our stakeholders have relative to test progress, completeness and thoroughness. The results associated with using these metrics at the sprint, project or enterprise-level level are discussed along with agile-at-scale project needs. This note is available on our web site at http://www.reifer.com/products or is provided free to our benchmarking service subscribers.

Agile Quality Survey (February 2017) – This technical note summarizes the findings of a detailed analysis of “hard” data on agile software quality from over two thousand completed software projects. This data was collected to quantitatively assess the quality of software products developed using agile methods. Software quality was measured during both the development phase and the first year of operations using a variety of widely used metrics. Data from over 200 organizations in 26 nations was used to develop the conclusions and recommendations offered.

Size Estimation Approaches for Use with Agile Methods (December 2016) – This popular white paper summarizes and then looks at the strengths and weaknesses of the five primary approaches used to size agile jobs. These methods include: sizing by analogy, function points, Halstead vocabulary, proxies, and user stories/story point counts. The paper concludes with a summary and a forecast for the future.