This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Measuring Developers: Aligning Perspectives and Other Best Practices
November/December 2009 (vol. 26 no. 6)
pp. 92-94
ASCII Text
x 
 
Medha Umarji, Forrest Shull, "Measuring Developers: Aligning Perspectives and Other Best Practices," IEEE Software, vol. 26, no. 6, pp. 92-94, November/December, 2009.
 
 
BibTex
x
 
@article{ 10.1109/MS.2009.180,
author = {Medha Umarji and Forrest Shull},
title = {Measuring Developers: Aligning Perspectives and Other Best Practices},
journal ={IEEE Software},
volume = {26},
number = {6},
issn = {0740-7459},
year = {2009},
pages = {92-94},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2009.180},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Measuring Developers: Aligning Perspectives and Other Best Practices
IS - 6
SN - 0740-7459
SP92
EP94
EPD - 92-94
A1 - Medha Umarji,
A1 - Forrest Shull,
PY - 2009
KW - Software engineering
KW - software metrics
VL - 26
JA - IEEE Software
ER -
 
Medha Umarji, University of Maryland Baltimore County
Forrest Shull, Fraunhofer Center for Experimental Software Engineering, Maryland
An effective metrics program must address both products and processes. However, process metrics can ignite strong opinions because they represent an area where technical considerations bump up against human aspects of software development. On the basis of a literature review and the authors' experiences, including a recent case study, they identify three best practices for instituting a process-metrics program.

1. V.R. Basili and H.D. Rombach, "The TAME Project: Towards Improvement-Oriented Software Environments," IEEE Trans. Software Eng., vol. 14, no. 6, 1988, pp. 758–773.
2. R. Kaplan and D. Norton, "The Balanced Scorecard: Measures That Drive Performance," Harvard Business Rev., vol. 70, no. 1, 1991, pp. 71–79.
3. J.D. Herbsleb and R.E. Grinter, "Conceptual Simplicity Meets Organizational Complexity: Case Study of a Corporate Metrics Program," Proc. 20th Int'l Conf. Software Eng., IEEE CS Press, 1998, pp. 271–280.
4. S.L. Pfleeger, "Lessons Learned in Building a Corporate Metrics Program," IEEE Software, vol. 10, no. 3, 1993, pp. 67–74.
5. T. De Marco and D. Hall, "Software Engineering: An Idea Whose Time Has Come and Gone?" IEEE Software, vol. 26, no. 4, 2009, pp. 96, 95.
6. V. Basili et al., "GQM+Strategies: Aligning Business Strategies with Software Measurement," Proc. 1st Int'l Symp. Empirical Software Eng. and Measurement (ESEM 07), IEEE CS Press, 2007, pp. 488–490.
7. A. Gopal et al., "Measurement Programs in Software Development: Determinants of Success," IEEE Trans. Software Eng., vol. 28, no. 9, 2002, pp. 863–875.
8. C.A. Dekkers, "The Secrets of Highly Successful Measurement Programs," Cutter IT J., Apr. 1999, pp. 29–35.
9. J. Iversen and L. Mathiassen, "Lessons from Implementing A Software Metrics Program," Proc. 33rd Hawaii Int'l Conf. System Sciences, vol. 7, IEEE CS Press, 2000, p. 7,040.
10. M. Umarji and C. Seaman, "Gauging Acceptance of Software Metrics: Comparing Perspectives of Managers and Developers," to be published in Proc. 3rd Int'l Symp. Empirical Software Eng. and Measurement (ESEM 09), IEEE CS Press, 2009.
11. N. Baddoo and T. Hall, "Motivators of Software Process Improvement: An Analysis of Practitioners' Views," J. Systems and Software, vol. 62, no. 2, 2002, pp. 85–96.

Index Terms:
Software engineering, software metrics
Citation:
Medha Umarji, Forrest Shull, "Measuring Developers: Aligning Perspectives and Other Best Practices," IEEE Software, vol. 26, no. 6, pp. 92-94, Nov.-Dec. 2009, doi:10.1109/MS.2009.180
Usage of this product signifies your acceptance of the Terms of Use.