Agile Software Quality: One Team, One Approach, Build Quality In (January 2018) – Using a third-party group to try to inspect or test quality into your products as they are developed does not work. Instead, you must engineer it in. The result is beneficial because focus is shifted from defect detection to prevention. This new book provides its readers with a framework, guidance and example to help them put its advice into practice. We have also developer a two-day seminar which trains agile teams on how to implement the book’s concepts which we are debuting in Seattle in October 2017. For more information, follow our announcements.
Benchmark Report (July 2017) – The benchmarking report issued in July of this year expands our software productivity findings into subdomains in the following four applications domains: naval (defense), space (defense), telecommunications, and web business. In total, the report, which is sold as a subscription service, provides benchmarks for 36 application domains starting with the next issue of our benchmarking report. Information about subscribing is available on our web site at http://www.reifer.com.
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.