2004Information ProfessionalRequires access

Counting the cost of IT projects

Philip H. Coombs

Open publisher page 0 citations

Abstract

We discuss about counting the cost of IT projects. Estimating the cost of a project has to be the most thankless task in IT, but it should be one of the most important. We also discuss how we justify projects when we do not try to find out the real cost. Estimates are need for three reasons: the first is to justify a project. It enables the cost to be compared with anticipated benefit. Second is the estimate used to enforce the discipline which is needed to make the project succeed and the third is to improve software production procedures and evaluate the effects of process improvement.

About this research paper

What this paper is about

We discuss about counting the cost of IT projects. Estimating the cost of a project has to be the most thankless task in IT, but it should be one of the most important. We also discuss how we justify projects when we do not try to find out the real cost. Estimates are need for three reasons: the first is to justify a project. It enables the cost to be compared with anticipated benefit. Second is the estimate used to enforce the discipline which is needed to make the project succeed and the third is to improve software production procedures and evaluate the effects of process improvement.

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

We discuss about counting the cost of IT projects. Estimating the cost of a project has to be the most thankless task in IT, but it should be one of the most important. We also discuss how we justify projects when we do not try to find out the real cost. Estimates are need for three reasons: the first is to justify a project. It enables the cost to be compared with anticipated benefit. Second is the estimate used to enforce the discipline which is needed to make the project succeed and the third is to improve software production procedures and evaluate the effects of process improvement.

Key concepts: Task (project management), Computer science, Process (computing), Cost estimate, Software, Cost contingency, Project management, Risk analysis (engineering)

Related papers

Back to paper searchBrowse research topicsOriginal source
Counting the cost of IT projects — Research Paper | ScholarLens