UPDATE – As most of my readers know, we have developed quality benchmarks by analyzing reliability (defect rates and densities), maintainability (repair times and defects inserted by repairs) and fitness for use (% functionality delivered versus promised) for projects done using agile, traditional and hybrid methods for over a decade. Our recent analysis of 1,500 projects, 500 of which are agile and none of which were over 10 years old, continues to provide interesting results. As previously noted, about one-third of the agile population used Scrum, another one-third used hybrid methods, many of which combined agile with lean and Kanban methods, and the remaining one-third used other agile methods like DAD, SAFe, etc.    Based on our recent analysis, the overall quality results were: * Defect densities were from 10 to 20 percent lower with agile methods in all of our 10 applications domains * Defect rates were also from 10 to 20 percent lower when agile methods were used except in defense domain where they were on par with traditional methods * Fix repairs were quicker when agile methods were used  averaging about 20 percent better in all cases * Fitness for use was better using traditional methods where an all or nothing delivery philosophy was maintained When agile and lean and/or Kanban methods were used together, quality got even better.  Gains in quality averaged another 10 percent across the board in all areas.  Gains in productivity and cost were even more dramatic as waste was eliminated and efficiencies achieved based on rework reduction.  For those interested, our new white paper entitled “Agile rework, waste and technical debt” provides a detailed discussion on how to use agile and lean in combination to tap these gains.  This white paper is available on the products page of this web site. For those interested, we make our benchmarks and other reports available for a fee at http://www.reifer.com/products. In addition, we often make summary data available at the many keynotes that we are asked to deliver and to the SIGs that we address.