icon-carat-right menu search cmu-wordmark

When Measurement Benefits the Measured

Webcast
During this webinar, we shared the performance results of over 100 software teams that have carefully tracked their schedule performance and the quality of their work.
Publisher

Software Engineering Institute

Watch

Abstract

What constitutes stellar performance and best practice? You can't really say what's good or best ... unless you measure it.

High-performing athletes rely on measurement to understand and improve so that they can compete effectively and win. Can knowledge workers such as software engineers use measurement in a similar approach? Absolutely. But the measures need to be practical, relevant, trustworthy, and actionable. They need to be used by the individual to benefit the individual.

Watch to:

  • see the emerging empirical results of over 100 software project teams that have collected accurate performance data
  • learn about the techniques that were developed and used to validate the accuracy of the collected data
  • learn how four basic measures can provide close-looped feedback to help software engineers understand and improve their performance

You don't need to measure everything. It only takes a few basic and easy-to-collect measures to help you and your team manage schedule commitments and software quality. Find out what those key measures are, how you can collect them, and how you and your software development team can use them effectively.

During this webinar, we shared the performance results of over 100 software teams that have carefully tracked their schedule performance and the quality of their work. We showed how high-integrity empirical results such as these can be used at the individual, project, and industry levels to characterize performance in meaningful and insightful ways.



About the Speaker

Headshot of Mark Kasunic

Mark Kasunic

Mark Kasunic is an SEI alumni employee.

Read more
Headshot of Bill Nichols.

Bill Nichols

William "Bill" Nichols joined the SEI in 2006 as a senior member of the technical staff and served as a Personal Software Process (PSP) instructor and Team Software Process (TSP) coach. Before joining the SEI, Nichols led a software-development team at the Bettis Laboratory near Pittsburgh, where he had been …

Read more