Integrated Approach of Software Project Size Estimation

Singh, Brajesh Kumar; Punhani, Akash; Misra, A. K.

doi:10.14257/ijseia.2016.10.2.05

Cited by 2 publications

(2 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Despite the strong correlation, the use in practice of function points to measure project size suffers from shortcomings, such as additional training needed, subjective determination of complexity, and not considering the development environment [60].…”

Section: Discussionmentioning

confidence: 99%

The effects of perceived value and stakeholder satisfaction on software project impact

Huijgens

Deursen

Solingen

2017

Information and Software Technology

View full text Add to dashboard Cite

In this paper we present a multiple case study on the insights of software organizations into stakeholder satisfaction and (perceived) value of their software projects. Our study is based on the notion that quantifying and qualifying project size, cost, duration, defects, and estimation accuracy needs to be done in relation with stakeholder satisfaction and perceived value. Objectives: We contrast project metrics such as cost, duration, number of defects and estimation accuracy with stakeholder satisfaction and perceived value. Method: In order to find out whether our approach is practically feasible in an industrial setting, we performed two case studies; one in a Belgian telecom company and the other in a Dutch software company. Results: In this study we evaluate 22 software projects that were delivered during one release in the Belgian telecom company, and 4 additional large software releases (representing an extension of 174% in project size) that were delivered in a Dutch software company. Eightythree (83) key stakeholders of two companies provide stakeholder satisfaction and perceived value measurements in 133 completed surveys. Conclusions: We conclude that a focus on shortening overall project duration, and improving communication and team collaboration on intermediate progress is likely to have a positive impact on stakeholder satisfaction and perceived value. Our study does not provide any evidence that steering on costs helped to improve these. As an answer to our research question-how do stakeholder satisfaction and perceived value relate to cost, duration, defects, size and estimation accuracy of software projects?-we found five takeaway messages .

show abstract

Section: Discussionmentioning

confidence: 99%

The effects of perceived value and stakeholder satisfaction on software project impact

Huijgens

Deursen

Solingen

2017

Information and Software Technology

View full text Add to dashboard Cite

show abstract

Section: The Core Project Metricsmentioning

confidence: 99%

Evidence-based software portfolio management

Huijgens

2016

Proceedings of the 20th International Conference on Evaluation and Assessment in Software Engineering

View full text Add to dashboard Cite

While many studies can be found on estimating the cost (or effort) of software deliveries (Jørgensen & Shepperd, 2007), only a handful exists about the price thereof. For pricing purposes in a commercial context where software delivery is partly performed by suppliers, most companies rely heavily on expert judgment (Boehm, 1984) (Jørgensen, 2004). This is not always a successful approach (Moløkken & Jørgensen, 2003), and software development is often characterized by high cost and schedule overruns (Verhoef, 2002) (Glass, 2002), despite a huge number of tools developed over time to support project estimation (Boehm, 1984

show abstract

Integrated Approach of Software Project Size Estimation

Cited by 2 publications

References 14 publications

The effects of perceived value and stakeholder satisfaction on software project impact

The effects of perceived value and stakeholder satisfaction on software project impact

Evidence-based software portfolio management

Contact Info

Product

Resources

About