Why is Software Late? An Empirical Study of Reasons for Delay in Software Development
IEEE Transactions on Software Engineering
Iterative design of seamless collaboration media
Communications of the ACM
The fountain model and its impact on project schedule
ACM SIGSOFT Software Engineering Notes
Software Development Productivity of European Space, Military, and Industrial Applications
IEEE Transactions on Software Engineering
A Model for Software Development Effort and Cost Estimation
IEEE Transactions on Software Engineering
The Mythical Man-Month: Essays on Softw
The Mythical Man-Month: Essays on Softw
A General Empirical Solution to the Macro Software Sizing and Estimating Problem
IEEE Transactions on Software Engineering
Managing and Predicting the Costs of Real-Time Software
IEEE Transactions on Software Engineering
Curve fitting for a model of applied research and development scheduling
IBM Journal of Research and Development
| Hi-index | 0.00 |
Schedule slippage can be avoided if timely preventive measures are adopted. The most common solution involves deploying additional manpower to boost productivity. But increasing the manpower deployed can hasten product development only to a certain point. Staffing beyond this elusive optimum can actually delay the ultimate completion of a project. To complicate the issue, optimal staffing for minimal development time is not easily ascertainable. But the predicted development time of a product and the skill level of the development team can be used as indicators of schedule slippage. This paper uses the Gamma model to provide skill level and completion time insights into optimally staffing a project.