Statistical analysis of deviation of actual cost from estimated cost using actual project data

Graduate School of Engineering Science, Osaka University, 1-3 Machikaneyama, Toyonaka, Osaka 560-8531, Japan
Information and Software Technology (Impact Factor: 1.33). 05/2000; DOI: 10.1016/S0950-5849(00)00092-6
Source: DBLP

ABSTRACT This paper analyzes an association of a deviation of the actual cost (measured by person-month) from the estimated cost with the quality and the productivity of software development projects. Although the obtained results themselves may not be new from the academic point of view, they could provide motivation for developers to join process improvement activities in a software company and thus become a driving force for promoting the process improvement.We show that if a project is performed faithfully under a well-organized project plan (i.e. the plan is first constructed according to the standards of good writing, and then a project is managed and controlled to meet the plan), the deviation of the actual cost from the estimated one becomes small. Next we show statistically that projects with small deviation of the cost estimate tend to achieve high quality of final products and high productivity of development teams. In this analysis, the actual project data on 37 projects at a certain company are extensively applied.


Available from: Osamu Mizuno, Jun 21, 2014
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: When the final tally was in, the year 2000 (Y2K) software compliance issue had cost over a hundred billion dollars worldwide. The fact that essentially everyone was busy tackling the same problem provided a unique opportunity to use data envelopment analysis (DEA) to measure software team efficiency and productivity. The data set analyzed in this paper contained about 70 programs from a large Canadian bank. While there were about a dozen different programming languages and a number of hardware platforms involved, the work was very similar in nature as they were all fixing the Y2K "bug". We examined both team productivity and programmer efficiency when maintaining code where the maintenance objective was the same in all cases. DEA models were developed to measure software project efficiency focusing on the factors that affect software productivity, and we discuss how these findings could be applied to other projects. Suggestions are offered on how DEA could be combined with the bank's own ratio-based rating system to improve their software production metrics. Finally, potential management uses of these DEA results are presented.
    IEEE Transactions on Engineering Management 09/2004; DOI:10.1109/TEM.2004.830843 · 0.94 Impact Factor
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: During software development, projects often experience risky situations. If projects fail to detect such risks, they may exhibit confused behavior. In this paper, we propose a new scheme for characterization of the level of confusion exhibited by projects based on an empirical questionnaire. First, we designed a questionnaire from five project viewpoints, requirements, estimates, planning, team organization, and project management activities. Each of these viewpoints was assessed using questions in which experience and knowledge of software risks are determined. Secondly, we classify projects into Bconfused'' and Bnot confused,'' using the resulting metrics data. We thirdly analyzed the relationship between responses to the questionnaire and the degree of confusion of the projects using logistic regression analysis and constructing a model to characterize confused projects. The experimental result used actual project data shows that 28 projects out of 32 were characterized correctly. As a result, we concluded that the characterization of confused projects was successful. Furthermore, we applied the constructed model to data from other projects in order to detect risky projects. The result of the application of this concept showed that 7 out of 8 projects were classified correctly. Therefore, we concluded that the proposed scheme is also applicable to the detection of risky projects.
    Empirical Software Engineering 10/2005; 10(4):495-515. DOI:10.1007/s10664-005-3864-z · 1.64 Impact Factor
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: This paper aims to provide a basis for the improvement of software-estimation research through a systematic review of previous work. The review identifies 304 software cost estimation papers in 76 journals and classifies the papers according to research topic, estimation approach, research approach, study context and data set. A Web-based library of these cost estimation papers is provided to ease the identification of relevant estimation research results. The review results combined with other knowledge provide support for recommendations for future software cost estimation research, including: 1) increase the breadth of the search for relevant studies, 2) search manually for relevant papers within a carefully selected set of journals when completeness is essential, 3) conduct more studies on estimation methods commonly used by the software industry, and 4) increase the awareness of how properties of the data sets impact the results when evaluating estimation methods
    IEEE Transactions on Software Engineering 02/2007; DOI:10.1109/TSE.2007.256943 · 2.29 Impact Factor