top of page

An Analytical Comparison of Software Project Estimation Techniques

Home → Research → Software Project Estimation Techniques

RESEARCH PUBLICATION · SOFTWARE ENGINEERING · PROJECT MANAGEMENT

I co-authored a review paper comparing six widely used software project estimation techniques. The paper examines their strengths, limitations, and suitability across different project environments to help teams make more informed decisions about estimating effort, cost, time, and resources.

A journal review paper comparing established approaches to software project estimation.

Publication type

Journal article / review paper

Journal

IJCA · Volume 187, Issue 1

Publication date

May 2025

Research Problem

Software project estimates influence budgets, timelines, resource allocation, and stakeholder expectations. Since estimation techniques differ in their required inputs, complexity, and suitability for different teams and projects, choosing an appropriate method can be challenging. This paper reviews several established approaches to support that decision.

Methodology

COCOMO — An algorithmic model for estimating software development effort.

Source Lines of Code (SLOC) — A size-based approach that uses estimated code volume as an input to project estimation.

Wideband Delphi — A structured group-estimation method that gathers and reconciles expert judgments.

Expert-Based Estimation — Uses practitioner experience and judgment to estimate project requirements.

Planning Poker — A collaborative estimation technique commonly used by Agile teams.

Function Point Analysis — Estimates software size based on delivered functionality.

Comparison Framework

The paper discusses these estimation techniques in relation to criteria such as accuracy, suitability for different project sizes, adaptability, and adequacy. It does not claim numerical rankings or that one technique is universally best.

Key Takeaways

Estimation methods have different strengths and limitations, so selection should reflect the project’s characteristics, team structure, and development approach. The paper aims to help practitioners make more informed estimation decisions.

My Contribution: Harsh Motiramani is a co-author of this review paper. No individual contribution or sole authorship is claimed.

What It Demonstrates: Comparative analysis, software engineering research, project planning, and evidence-informed decision-making.

bottom of page