• DocumentCode
    1241328
  • Title

    What can happen when metrics make the call

  • Author

    Bollinger, T.

  • Author_Institution
    DSC Commun., USA
  • Volume
    12
  • Issue
    1
  • fYear
    1995
  • fDate
    1/1/1995 12:00:00 AM
  • Firstpage
    15
  • Abstract
    The software development discipline uses many well-intended metrics in ways that can be detrimental to a company´s financial well-being. The most dangerous are the derived metrics-measures produced from some sort of equation that purport to show progress toward a goal. These are dangerous precisely because they are goal-oriented: they try to measure the goodness of a product or process. Derived metrics are built from feature metrics-they measure readily identifiable and relatively unambiguous features of a product or process. In isolation, feature metrics don´t describe goodness, but they can be used in a derived metric to judge the quality. Bogus software metrics are an almost unavoidable side-effect of trying to understand and manage software products and processes. Yet managers and metrics groups can take one important lesson to heart: listen to your developers and listen very carefully. If you have seen why a metric is bogus, don´t just leave it at that or treat it as a secondary issue. Root out the problem and figure out how to do it right or, at the very least, better than you did it before
  • Keywords
    software management; software metrics; bogus software metrics; derived metrics; feature metrics; goal-oriented metrics; process goodness; product goodness; Engineering profession;
  • fLanguage
    English
  • Journal_Title
    Software, IEEE
  • Publisher
    ieee
  • ISSN
    0740-7459
  • Type

    jour

  • DOI
    10.1109/52.363158
  • Filename
    363158