What makes measuring software so hard?

  • Rifkin S
  • 17

    Readers

    Mendeley users who have this article in their library.
  • 12

    Citations

    Citations of this article.

Abstract

We often hear that it is difficult to get software measurement
into practice. Traditional measurement addresses the decisions that
support increased quality, increased programmer productivity, and
reduced costs: key elements for organizations strategically focused on
operational excellence. But what if the organization's highest priority
isn't operational excellence? The article shows that such organizations
have different measurement needs and presents ideas on how to address
those needs, thereby making measurement more appealing. While the
disparity discussed here involves measurement, it applies to all areas
of software process improvement. For example, the Software Engineering
Institute's Capability Maturity Model for Software is silent on two of
the three strategies of high-performing organizations: customer intimacy
and product innovation. Like traditional measurement, the Capability
Maturity Model applies only to organizations wanting to be operationally
excellent

Get free article suggestions today

Mendeley saves you time finding and organizing research

Sign up here
Already have an account ?Sign in

Find this document

Authors

  • Stan Rifkin

Cite this document

Choose a citation style from the tabs below

Save time finding and organizing research with Mendeley

Sign up for free