Computing Optimal Scheduling Policies for Software Projects

  • Authors:
  • Frank Padberg

  • Affiliations:
  • Universität Karlsruhe, Germany

  • Venue:
  • APSEC '04 Proceedings of the 11th Asia-Pacific Software Engineering Conference
  • Year:
  • 2004

Quantified Score

Hi-index 0.00

Visualization

Abstract

The time needed to complete a software development project is hard to estimate in practice. In addition to the uncertainty about the duration of the individual development steps, software projects often suffer from unexpected rework and delays. As a result, project scheduling remains a difficult task for the managers of software projects. In this paper, we compute optimal scheduling strategies for a set of sample software projects.The computations are based on a stochastic Markov decision model for software projects which focuses on capturing the feedback between concurrent development activities. The optimal strategies are computed using a variant of the value iteration algorithm from stochastic dynamic programming.Since the underlying process model is stochastic, the strategies are stochastically optimal, that is, they minimize the expected project duration.The ultimate goal of this research is to develop guidelines for managers how to schedule their software projects under uncertainty in the best possible way. The sample projects are similar, but differ in certain characteristics of the project or product, such as the strength of the coupling between the components or the degree of specialization of the teams on the tasks.By using a set of related projects, we can study how the project characteristics influence the optimal scheduling decisions in a project. In addition to computing the optimal scheduling policies for the sample projects, we use extensive simulations to compare the performance of the optimal policy against the so-called list policies for each given setting. List policies are a simple, but commonly used class of scheduling policies.For our sample projects, we find that the best list policy in general is not optimal. The performance gaop is the larger the higher the degree of specialization of the teams is.On the other hand, the stronger the coupling between the components, the smaller is the improvement which the optimal policy achieves over the best list policy.