Better Software Magazine Articles

What's on Your Dashboard?

Just because a metric is easy to capture doesn't mean it is useful. The metrics that are really needed are the ones that can help you make good decisions. Find out how to establish a project dashboard with meaningful metrics that will guide your project safely to its destination without getting bogged down in an endless pursuit of unnecessary information.

John Fodeh's picture John Fodeh
Metrics You Can Bet On

An old adage says that you cannot manage what you cannot measure, but Mike Cohn thinks differently. Here, he offers suggestions on when to use metrics and when you can manage without, as well as some guidelines to help you choose your metrics carefully.

Mike Cohn's picture Mike Cohn
Measurements that Matter

No one starts a project with the goal of failing, but some metrics experts claim that 80 percent of software metrics initiatives fail. Just as your software project has goals for success, you should have goals for success in your metrics initiatives. Find out what you can do to better your chance for success.

Alan Page's picture Alan Page
Metrics That Matter: Making Measurements Meaningful for Everyone

Metrics are only worthwhile if you review and use them. Do your quality reports go directly from the inbox to the trash can? A quality metrics program can be a great asset to your organization. Engineering, sales, and the company overall can benefit from having such a program. This article will help you explore ways to make measurements meaningful outside of QA.

Marsha Holliday
A Measured Response

An infinite number of metrics can be applied to various aspects of software development. In fifteen years of managing software development, Mike Cohn has found a handful of metrics that really help him do his job--and keep him cool and confident when the heat is on. Here, he describes product stabilization metrics, programmer quality metrics, customer satisfaction metrics, and complexity metrics.

Mike Cohn's picture Mike Cohn
Don't Use Bug Counts to Measure Testers

Cem Kaner tells us why we should not use bug counts to measure testers. Using examples, he illustrates two problems: 1) bug counts are poor measures of individual performance; and 2) the side effects of using bug counts as a measure are serious.

Cem Kaner
Measuring and Managing Performance in Organizations

Don Gray recommends Measuring and Managing Performance in Organizations by Robert D. Austin. The book is not a five-step program toward measurement success; instead, it gives an in-depth look at what makes or breaks measurement systems. The book presents information in an intuitive way; if you understand algebra and simple logic, you will understand what Austin is presenting.

Don Gray's picture Don Gray
Making Numbers Count

Numbers count—no two ways about it. But any numbers you include in a bug report should also include the appropriate units of measure. In an example from their experience, David Wilson and Leonidas Hepis explain the importance of using consistent terminology and units of measure.

A Cautionary Tale

Technical Editor Brian Marick uses a fairy tale format to warn software professionals against using easy-to-acquire numbers in place of human judgment.

Brian Marick
Software Measurement Programs

A metrics program is any planned activity in which you use measurement to meet some specific goal. If you do not have a clear technical goal for a metrics program, then you are almost certainly not ready for such a program. Here's how to design a measurement program that leads to decisions and actions.

Norman Fenton

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.