Some consider test metrics and in particular, managing with metrics, a thorn in software development and testing, but when used properly, they provide valuable insights into what occurs during projects and what strategic and tactical adjustments must be made on a daily basis.

Find out how a small set of test metrics were used to successfully manage a major test acceptance effort.  This was done at the conclusion of a two and half year ERP implementation. Bradshaw brings to attention specific use of the S curve analytics.  He provides an interesting history on how  the “S-curve” was first discovered.  Obviously, it had nothing to do with software or test metrics at that time! It was named after Lord Rayleigh.  Also known as the Rayleigh Cumulative Distribution provides a graphical representation of a cumulative work effort — see a highlight —.S-curve and software testing.

S curve software test metrics

S curve results Day 15

The key idea is to manage the progress of the test effort by comparing the scheduled and actual results. Using this method can help  to identify issues earlier and avoid delays. Additionally,  plotting this metrics data provides a great visual indicator of the progress of the test effort over time.
 These graphs also make it possible to measure the effectiveness of the test effort and provide a valuable basis for decisions to keep the test effort on schedule, S-curve analysis also can assist in determining  the stability of the application prior release to production.

Learn how key metrics drove test management decisions and how these same metrics will benefit your organization.