This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
May/June 2008 (vol. 25 no. 3)
pp. 24-28
ASCII Text
x 
 
Bill Curtis, Girish V. Seshagiri, Donald Reifer, Iraj Hirmanpour, Gargi Keeni, "The Case for Quantitative Process Management," IEEE Software, vol. 25, no. 3, pp. 24-28, May/June, 2008.
 
 
BibTex
x
 
@article{ 10.1109/MS.2008.80,
author = {Bill Curtis and Girish V. Seshagiri and Donald Reifer and Iraj Hirmanpour and Gargi Keeni},
title = {The Case for Quantitative Process Management},
journal ={IEEE Software},
volume = {25},
number = {3},
issn = {0740-7459},
year = {2008},
pages = {24-28},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2008.80},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - The Case for Quantitative Process Management
IS - 3
SN - 0740-7459
SP24
EP28
EPD - 24-28
A1 - Bill Curtis,
A1 - Girish V. Seshagiri,
A1 - Donald Reifer,
A1 - Iraj Hirmanpour,
A1 - Gargi Keeni,
PY - 2008
KW - Quantitative Process Management
KW - Quantitative Project Management
KW - Quantitative Software Models
KW - Predictive Software Models
KW - Statistical Project Management
VL - 25
JA - IEEE Software
ER -
 
Bill Curtis, CAST Software
Girish V. Seshagiri, Advanced Information Services
Donald Reifer, Reifer Consultants
Iraj Hirmanpour, Software Engineering Intitute
Gargi Keeni, Tata Consultancy Services
This article introduces a special section on "Embedding Statistical Methods into Software Engineering Practices." It provides a background on Quantitative Process Management and makes the case for why these methods are important. It presents an example of how a model can be developed to predict project outcomes by using data emerging from the performance of process tasks. It discusses how these methods can be used with different software development paradigms. It ends by summarizing develops needed in five different communities in order for these methods to be widely adopted.

1. D.L. Gibson, D.R. Goldenson, and K. Kost, Performance Results of CMMI-Based Process Improvement, tech. report CMU/SEI-2006-TR004, Software Eng. Inst., Carnegie Mellon Univ., 2006.
2. W.E. Deming, The New Economics, 2nd ed., MIT Center for Educational Computing Initiatives, 1994.
3. T.H. Davenport and J.G. Harris, Competing on Analytics, Harvard Business School Press, 2007.
4. W.A. Shewhart, Economic Control of Quality of Manufactured Product, Van Nostrand, 1931.
5. D.J. Wheeler, Understanding Variation, SPC Press, 1993.
6. W.S. Humphrey, Introduction to the Personal Software Process, Addison-Wesley, 1997.
7. W.S. Humphrey,Introduction to the Team Software Process, Addison-Wesley, 2000.
8. A. Cockburn, Agile Software Development, Addison-Wesley, 2002.

Index Terms:
Quantitative Process Management, Quantitative Project Management, Quantitative Software Models, Predictive Software Models, Statistical Project Management
Citation:
Bill Curtis, Girish V. Seshagiri, Donald Reifer, Iraj Hirmanpour, Gargi Keeni, "The Case for Quantitative Process Management," IEEE Software, vol. 25, no. 3, pp. 24-28, May-June 2008, doi:10.1109/MS.2008.80
Usage of this product signifies your acceptance of the Terms of Use.