An Ideal Team Size in Development and Maintenance Project


The KIPS Transactions:PartD, Vol. 10, No. 1, pp. 77-84, Feb. 2003
10.3745/KIPSTD.2003.10.1.77,   PDF Download:

Abstract

Experts work teams generally agree that small teams are better than large teams for getting things done. Also, always aim for the lowest practical team size. But what does 'small' mean? We introduce to productive metrics such as project delivery rate (PDR) and speed of delivery (SOD) for decision criteria of ideal team size. The experimental is based on the analysis of 300 project data. These data sets are divide in two subgroups. One is a development project the other is a maintenance project. As a result of experimental in two subgroup, we come to the conclusion that the most successful projects has small teams indeed staffed with maximum five persons. This paper presents ideal team size in order to provide information that can be used as a guide in selecting the most practical and productive-based team size for a software development project.


Statistics
Show / Hide Statistics

Statistics (Cumulative Counts from September 1st, 2017)
Multiple requests among the same browser session are counted as one view.
If you mouse over a chart, the values of data points will be shown.


Cite this article
[IEEE Style]
S. U. Lee, J. Y. Park, J. H. Park, "An Ideal Team Size in Development and Maintenance Project," The KIPS Transactions:PartD, vol. 10, no. 1, pp. 77-84, 2003. DOI: 10.3745/KIPSTD.2003.10.1.77.

[ACM Style]
Sang Un Lee, Joong Yang Park, and Jae Heong Park. 2003. An Ideal Team Size in Development and Maintenance Project. The KIPS Transactions:PartD, 10, 1, (2003), 77-84. DOI: 10.3745/KIPSTD.2003.10.1.77.