A conflict between the use of estimating and planning tools in the management of information systems

@article{Edwards1994ACB,
  title={A conflict between the use of estimating and planning tools in the management of information systems},
  author={John S. Edwards and Trevor T. Moores},
  journal={European Journal of Information Systems},
  year={1994},
  volume={3},
  pages={139-147}
}
This paper argues that there is a difference between how software development project managers perceive the task of estimating project costs and duration and the way in which commercially available estimating tools are designed to be used. A model of the early estimating/planning stages of a project (the EEPS model) is presented which suggests estimation could be first carried out either before or during the first detailed planning stage. A survey was carrried out which confirmed that project… 
Producing Task-Based Estimates of Software Development Projects
TLDR
It will be argued that TABatHA is particularly useful on projects where user requirements change, because the effort involved in revising the project plan occurs at a task level, exactly the point at which TABATHA generates estimates.
An examination of the effect of decision style on the use of a computerized project management tool
  • T. Fox
  • Engineering, Business
  • 1998
Managing a software development project presents many difficulties. Most software development projects are considered less than successful, and many are simply canceled. Ineffective project
System dynamics in software project management: towards the development of a formal integrated framework
TLDR
A conceptual integrated model, the SYDPIM, is developed which has been tested and improved within a large on-going software project, and specifies the roles of SD models, how they are to be used within the traditional management process,How they exchange information with the traditional models, and a general method to support model development.
A comparison of software project overruns - flexible versus sequential development models
TLDR
An in-depth survey of software development projects supports the claim that projects which employ a flexible development model experience less effort overruns than do those whichemploy a sequential model.
A survey on software estimation in the Norwegian industry
TLDR
An in-depth survey of software companies' estimation methods suggests that expert estimation is the dominating estimation method, that estimation accuracy is not much impacted by use of formal estimation models, and that software managers tend to believe that the estimation accuracy of their company is better than it actually is.
Function Point: A Quality Loom for the Effort Assessment of Software Systems
Summary Accurate estimation of software development effort is critical in software engineering. Underestimates lead to time pressures that may compromise full functional development and thorough
Software Development Effort Estimation - Demystifying and Improving Expert Estimation
The main determinant of many types of software-related investments is the amount of development effort required. The ability of software clients to make investment decisions based on cost estimates
Developing a Scoring Model to Evaluate Project Management Software Packages Based on ISO/IEC Software Evaluation Criterion
TLDR
The aim of this paper was to develop an evaluation/scoring module suitable for comparing different project management software packages to help select the most appropriate package.
A review of studies on expert estimation of software development effort
Expert Estimation of Software Development Cost: Learning through Feedback
TLDR
Four guidelines for improved learning are described and validated that extend the general software experience learning frameworks, e.g., the “experience factory” framework, with estimation specific learning guidelines and made the estimation accuracy feedback significantly more useful for improvement of estimation performance through feedback.
...
...