Software Measurement: What's in It for Me?

[article]
Summary:

The biggest obstacle to implementing a successful software measurement program is getting the software professionals, the ones in the trenches designing, coding, documenting and testing the software, to measure their work.

Recently I attended a conference where I heard a lot of software quality and process professionals lamenting the fact that the software measurement programs they were responsible for were doomed to failure. Further discussion led me to believe that the problem wasn't poorly conceived or executed measurement programs, but poorly accepted ones.

The biggest obstacle to implementing a successful software measurement program is getting the software professionals, the ones in the trenches designing, coding, documenting and testing the software, to measure their work.

To many software developers, not only is there no obvious incentive, there is actually the disincentive of having their output scrutinized and possibly misunderstood. Who wants his boss to know that the guy in the next cubicle wrote more code than he did last week? If we are to make measurement programs work we need to make sure that the software professionals we are asking to measure understand the personal and professional

About the author

TechWell Contributor's picture TechWell Contributor

The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email editors@techwell.com.

StickyMinds is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Nov 09
Nov 09
Apr 13
May 03