Rethinking Success in Software Projects: Looking Beyond the Failure Factors

Далчер, Даррен

doi:10.1007/978-3-642-55035-5_2

Cited by 18 publications

(34 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…After reviewing the results, in particular with respect to the identified benefits, we conclude that research has been biased towards the first level of project management results. In [84], the author argues that there can be several levels of criteria for evaluating the success of software development projects. The first level deals with efficiency and performance of the execution of the project.…”

Section: Semantics Of the Identified Benefitsmentioning

confidence: 99%

What software reuse benefits have been transferred to the industry? A systematic mapping study

Barros-Justo

Pinciroli

Matalonga

et al. 2018

Information and Software Technology

View full text Add to dashboard Cite

Context: The term software reuse was first used in 1968 at the NATO conference. Since then, work in the scientific literature have stated that the application of software reuse offers benefits such as increase in quality and productivity. Nonetheless, in spite of many publications reporting software reuse experiences, evidence that such benefits having reached industrial settings is scarce. Objective: To identify and classify the benefits transferred to real-world settings by the application of software reuse strategies. Method: We conducted a systematic mapping study (SMS). Our search strategies retrieved a set of 2,413 papers out of which 49 were selected as primary studies. We defined five facets to classify these studies: a) the type of benefit, b) the reuse process, c) the industry's domain, d) the type of reuse and e) the type of research reported. Results: Quality increase (28 papers) and Productivity increase (25 papers) were the two most mentioned benefits. Component-Based Development (CBD) was the most reported reuse strategy (41%), followed by Software Product Lines (SPL, 30%). The selected papers mentioned fourteen industrial domains, of which four stand out: aerospace and defense, telecommunications, electronics and IT services. The application of systematic reuse was reported in 78% of the papers. Regarding the research type, 50% use evaluation research as the investigation method. Finally, 13 papers (27%) reported validity threats for the research method applied. Conclusions: The literature analyzed presents a lack of empirical data, making it difficult to evaluate the effective transfer of benefits to the industry. This work did not find any relationship between the reported benefits and the reuse strategy applied by the industry or the industry domain. Although the most reported research method was industrial case studies (25 works), half of these works (12) did not report threats to validity.

show abstract

Section: Semantics Of the Identified Benefitsmentioning

confidence: 99%

What software reuse benefits have been transferred to the industry? A systematic mapping study

Barros-Justo

Pinciroli

Matalonga

et al. 2018

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…Software project management (SPM) is of key importance for failure or success of a software project [1] and there is ongoing need to adjust into dynamically changing technologies and project environments. Overall, while SPM is of tremendous importance, its maturity is lacking.…”

Section: Introductionmentioning

confidence: 99%

Analytics for Software Project Management -- Where are We and Where do We Go?

Nayebi

Ruhe

Mota

et al. 2015

2015 30th IEEE/ACM International Conference on Automated Software Engineering Workshop (ASEW)

View full text Add to dashboard Cite

Software project management is a decision intensive process. Success or failure of the project is highly dependent on these decisions. Analytical techniques and tools can support project managers throughout the software project life cycle by increasing the predictability and chance of success in these projects. In this paper, we report the results of a systematic mapping study within which we investigate the usage of different types of analytics for software project management. We analyze the accessibility of the data as well as the degree of validation reported in the 115 studies selected for final analysis. This resulted in a picture of the status quo (Where are we?) of analytics in software project management. From comparing this status quo with the results of an industrial survey on the industrial needs of different types of analysis, we propose an agenda on future work (Where do we go?).

show abstract

“…Jorgensen studied on failure factors of small‐scale software projects at a global outsourcing marketplace. Dalcher believes software project success needs to be understood at multiple levels. He developed a 4‐level model for success: Project management success focus on efficiency and performance Project success focus on objectives, benefits, and stakeholders Business success focus on value creation and delivery Future potential focus on new markets, skills, and opportunities …”

Section: Software Project Successmentioning

confidence: 99%

Prioritizing key success factors of software projects using fuzzy AHP

Yaghoobi

2017

J Software Evolu Process

View full text Add to dashboard Cite

The main purpose of most software projects is to build an effective and efficient product that satisfies the user's requirements under constraints of basic available resources. Thus, recognizing the critical features that may affect developing the application could be imperative. In this study, we apply the fuzzy analytic hierarchy process (AHP) to the issue of ordering key success factors (KSFs) for software development projects. To do this, we first simplified the constrained fuzzy AHP method, and then from systematic literature reviews, a preliminary list of potential KSFs that influences software development projects was identified and compiled. Subsequently, on the basis of the criteria of the frequency of citation in previous studies, closely related and similar functionality, the preliminary list was consolidated into a final set of 15 possible KSFs and considered at 4 perspectives of project management, development team, product, and processes.Pairwise comparisons, required by fuzzy AHP method, were done by 22 experienced professional internal stakeholders to determine the preference weights of factors and perspectives in terms of natural language expressions. The results reveal that project management has the highest importance in comparison with other 3 perspectives, and the factor of efficient project management skills/methodologies is the major. The procedure used in this paper is simple and accurate to implement and concludes both relative weights and rankings of alternatives in a fuzzy environment. KEYWORDSconstrained fuzzy AHP, key success factors, project management, software development

show abstract

Rethinking Success in Software Projects: Looking Beyond the Failure Factors

Cited by 18 publications

References 20 publications

What software reuse benefits have been transferred to the industry? A systematic mapping study

What software reuse benefits have been transferred to the industry? A systematic mapping study

Analytics for Software Project Management -- Where are We and Where do We Go?

Prioritizing key success factors of software projects using fuzzy AHP

Contact Info

Product

Resources

About