Job-shop development model: a case study

Traditional effort-estimation models can be frustrating, especially when staff are divided among multiple projects. The authors evaluate a model based on dividing activities into jobs. It accounts for divided time and more accurately categorizes rework costs. The model lets organizations represent software development in more detail than they can with many existing models. By breaking each project into batches and each batch into jobs, the model recognizes that, at any point in time, parts of the software may be at different stages of completion.<
>