Counting the cost of IT projects
Philip H. Coombs
Abstract
Philip H. Coombs
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.
A significance statement is not available in the OpenAlex record.
A contribution statement is not available in the OpenAlex record.
Method details are not available in the OpenAlex metadata.
Findings are not separately available in the OpenAlex metadata.
Limitations are not available in the OpenAlex metadata.
Application details are not available in the OpenAlex metadata.
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)