Identification and Quantitative Analysis of Project Success Factors for Large Scale Projects

2014 ◽  
Vol 5 (1) ◽  
pp. 83-95 ◽  
Author(s):  
Basit Shahzad ◽  
Abass Md Said
Keyword(s):  
Resource Allocation ◽  
Quantitative Analysis ◽  
Large Scale ◽  
Success Factors ◽  
Project Success ◽  
Research Area ◽  
Software Project ◽  
Software Projects ◽  
Open Research ◽  
Timely Completion

Software projects require a right mix of the software resources and the expertise to increase the chances of timely completion. The interface for the resource allocation to the software projects is provided by the project factors. The identification of the comprehensive project factors for the diversified nature of projects in itself is an open research area. This paper is based on a quantitative study that helps in identifying the prominent software project factors for large scale projects. The paper then, as a result provides a list of project success factors and provides the statistical evidence to support the result of the survey.

scholarly journals Core Factors for Software Projects Success

2019 ◽  
Vol 3 (1) ◽  
Author(s):  
Mohammad Ibraigheeth ◽  
Syed Abdullah Fadzli
Keyword(s):  
Success Rate ◽  
Case Studies ◽  
Success Factors ◽  
Project Success ◽  
Software Project ◽  
Software Projects ◽  
Quality Cost ◽  
Project Failure ◽  
Definition Of ◽  
Failure Factors

The successful software project can be defined as the project that meets the planned quality, cost, schedule, and effort. It has been suggested that there are many reasons which might lead to software project success.  Several success and failure factors for particular projects were discussed in the literature. This paper aims to identify the most common success factors through reviewing a set of software project reports and case studies. In order to fully understand reasons behind the project success, the reasons behind project failure and the definition of failure itself are discussed. Furthermore, case studies of successful and failed software projects are described. This paper also investigates techniques that have been developed to increase software project success rate and decrease probable failures.

Using Genetic Algorithms to Search for Key Stakeholders in Large-Scale Software Projects

2013 ◽  
pp. 118-134 ◽  
Author(s):  
Soo Ling Lim ◽  
Mark Harman ◽  
Angelo Susi
Keyword(s):  
Genetic Algorithms ◽  
Real World ◽  
Large Scale ◽  
Requirements Elicitation ◽  
Software Project ◽  
Software System ◽  
Software Projects ◽  
Key Stakeholders ◽  
Large Software ◽  
Stakeholder Needs

Large software projects have many stakeholders. In order for the resulting software system and architecture to be aligned with the enterprise and stakeholder needs, key stakeholders must be adequately consulted and involved in the project. This work proposes the use of genetic algorithms to identify key stakeholders and their actual influence in requirements elicitation, given the stakeholders’ requirements and the actual set of requirements implemented in the project. The proposed method is applied to a large real-world software project. Results show that search is able to identify key stakeholders accurately. Results also indicate that many different good solutions exist. This implies that a stakeholder has the potential to play a key role in requirements elicitation, depending on which other stakeholders are already involved. This work demonstrates the true complexity of requirements elicitation – all stakeholders should be consulted, but not all of them should be treated as key stakeholders, even if they appear to be significant based on their role in the domain.

The Impact of Project Initiators on Open Source Software Project Success

2021 ◽  
pp. 221-238
Author(s):  
Ling Wang ◽  
Jinxiao Wang
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Project Success ◽  
Software Project ◽  
Software Projects ◽  
Collective Behaviors ◽  
Collective Wisdom ◽  
Open Source Software Project ◽  
Development Costs ◽  
Collaborative Innovation

This paper focuses on studying the role of open source software project initiator in affecting the OSS project success from the perspective of individual and collective behaviors. The authors collected the data from an emerging OSS hosting platform Gitee in China. This research indicates that the success mode for open source software projects in China relies a lot on the project initiators. Project initiators not only contribute codes to aid the project directly, but also use their social capital to facilitate the project success. But no full play has been given to social network's effect on mass production and collaborative innovation. The authors suggest collaborative innovation which could lead to coherence of global collective wisdom, reduced development costs, and expanded source of innovation should be the further direction for the OSS project in emerging platforms.

scholarly journals Identification-Method Research for Open-Source Software Ecosystems

Symmetry ◽  
2019 ◽  
Vol 11 (2) ◽  
pp. 182 ◽  
Author(s):  
Zhifang Liao ◽  
Ningwei Wang ◽  
Shengzong Liu ◽  
Yan Zhang ◽  
Hui Liu ◽  
...  
Keyword(s):  
Open Source ◽  
Open Source Software ◽  
Clustering Algorithm ◽  
Research Area ◽  
Software Project ◽  
Software Projects ◽  
Virtual Collaboration ◽  
Software Ecosystem ◽  
Software Ecosystems ◽  
Core Project

In recent years, open-source software (OSS) development has grown, with many developers around the world working on different OSS projects. A variety of open-source software ecosystems have emerged, for instance, GitHub, StackOverflow, and SourceForge. One of the most typical social-programming and code-hosting sites, GitHub, has amassed numerous open-source-software projects and developers in the same virtual collaboration platform. Since GitHub itself is a large open-source community, it hosts a collection of software projects that are developed together and coevolve. The great challenge here is how to identify the relationship between these projects, i.e., project relevance. Software-ecosystem identification is the basis of other studies in the ecosystem. Therefore, how to extract useful information in GitHub and identify software ecosystems is particularly important, and it is also a research area in symmetry. In this paper, a Topic-based Project Knowledge Metrics Framework (TPKMF) is proposed. By collecting the multisource dataset of an open-source ecosystem, project-relevance analysis of the open-source software is carried out on the basis of software-ecosystem identification. Then, we used our Spectral Clustering algorithm based on Core Project (CP-SC) to identify software-ecosystem projects and further identify software ecosystems. We verified that most software ecosystems usually contain a core software project, and most other projects are associated with it. Furthermore, we analyzed the characteristics of the ecosystem, and we also found that interactive information has greater impact on project relevance. Finally, we summarize the Topic-based Project Knowledge Metrics Framework.

Quantitative analysis of viable systems model on software projects in the ICT sector in Castilla y León

Kybernetes ◽  
2015 ◽  
Vol 44 (5) ◽  
pp. 806-822 ◽  
Author(s):  
Julio César Puche Regaliza
Keyword(s):  
Quantitative Analysis ◽  
Structural Equation ◽  
Measurement Tool ◽  
Software Project ◽  
Software Projects ◽  
Content Type ◽  
Viable Systems ◽  
Viable Systems Model ◽  
Systems Model ◽  
Castilla Y Leon

Purpose – The purpose of this paper is to detect the degree of influence between applying the Viable Systems Model (VSM), developed by Stafford Beer, on a software project and its viability or success. Design/methodology/approach – The authors performed a quantitative analysis in which it was necessary to identify theoretical constructs of the VSM (Systems One to Five) and of the viability or success of the software project, measuring each of the indicators together. These indicators have been included in a questionnaire or standardised measurement tool, which was subsequently used for data collection by a number of companies in the information and communications technology sector in Castilla y León. The obtained data served as the basis for a number of results through the definition of a structural equation model. Findings – The results support the particular importance of Systems One and Four in a software project. In other words, software projects need to clearly define their operational elements (e.g. organisational units, business units, working environments, and working teams) and the relationships that appear between them. Additionally, in software projects it is necessary to determine the appropriate prevention actions to be able to observe the changes that take place in their environment and thus make decisions that allow the project to adapt to these changes. Originality/value – The originality is based on the VSM application in software projects organisation. The value is based on VSM formalisation and practical application, to overcome the criticism about its abstract nature.

Probabilistic Method for Managing Common Risks in Software Project Scheduling Based on Program Evaluation Review Technique

2020 ◽  
Vol 11 (3) ◽  
pp. 77-94
Author(s):  
Quyet-Thang Huynh ◽  
Ngoc-Tuan Nguyen
Keyword(s):  
Risk Factors ◽  
Resource Allocation ◽  
Program Evaluation ◽  
Bayesian Networks ◽  
Project Scheduling ◽  
Construction Projects ◽  
Probabilistic Method ◽  
Software Project ◽  
Software Projects ◽  
Common Risk Factors

Project management and project scheduling are crucial to help development teams keep track of timing as well as resource allocation. In order to manage software projects, project managers need to anticipate, analyze the risk factors that may occur as well as their impacts on the progress of the project, and assess and adapt the project resource allocation. This paper concentrates on a quantitative approach for risk analysis in software project scheduling by taking advantage of Bayesian networks capacity (including related mathematical calculations) in modeling and assessing uncertainty and incorporates them in software project scheduling with program evaluation and review technique (PERT). Common risk factors in project scheduling are also examined, and a Bayesian networks model of 19 common risk factors and their causal relationships is proposed and confirmed. The research also borrows and implements categories and levels of risk from construction projects into software projects. A tool was built to experiment and validate the proposed model.

Adaptive and Dynamic Hybrid Model for Software Project Management: A Review on its Clarity and Usage to Improve Project Success

2019 ◽  
Vol 892 ◽  
pp. 38-45
Author(s):  
Marzanah A. Jabar ◽  
Norhayati Mohd. Ali ◽  
Yusmadi Yah Jusoh ◽  
Salfarina Abdullah ◽  
S. Mohanarajah
Keyword(s):  
Project Management ◽  
Software Development ◽  
Project Success ◽  
Software Project ◽  
Software Projects ◽  
Software Developers ◽  
Effective Role ◽  
Software Development Methodologies ◽  
Dynamic Hybrid ◽  
Current Research Interest

Software developers have shown a lot of interest in using agile approaches and methods to manage projects. The Agile Manifesto in 2001 provided a good basis to use this as it formulated its 4 values and 12 principles. Adaptability was a common feature in the Agile Manifesto to make agility happen and there appears a need to combine dynamism to ensure agility takes a more concrete and effective role. Whilst the term adaptability is discussed more often than dynamism by most researchers, the clarity in its meaning needs improvement as the terms are used interchangeably. This paper proposes a useful clarity on its differences and how it should be used. In addition, this approach would also facilitate the current research interest in mixing and combining software development methodologies to create hybrid versions as pure methods (traditional and agile) have not worked well in most software projects.

scholarly journals A Review of Critical Success Factors for Offshore Software Development Projects

Organizacija ◽  
2013 ◽  
Vol 46 (6) ◽  
pp. 282-296 ◽  
Author(s):  
Goparaju Purna Sudhakar
Keyword(s):  
Critical Success Factors ◽  
Success Factors ◽  
Project Success ◽  
Organizational Factors ◽  
Cultural Factors ◽  
Development Projects ◽  
Software Projects ◽  
Critical Success ◽  
Efficient Communication ◽  
Contract Type

AbstractOffshore project success is very much important to both customer and the vendor. Based on very less success rate of overall software projects globally, critical success factors (CSFs) for offshore software projects is gaining much importance. In the current study based on literature review, a total of 75 success factors for offshore software projects are identified. Further based on their appearance in literature 20 critical success factors from 10 CSF categories are identified. Finally top six most critical success factors for offshore software projects such as trust, efficient communication, cultural understanding, relationship between client and vendor, contract type and efficient knowledge transfer are identified. The CSFs categories are prioritized in the order of importance. The important CSF categories for offshore projects found are organizational factors (both client and vendor), project factors, cultural factors and environmental factors.

scholarly journals La gestión ágil de proyectos de software en la formación Académica Universitaria: Una revisión sistemática de la literatura

2020 ◽  
pp. 8-21
Author(s):  
Luz María Hernández-Cruz ◽  
Margarita Castillo-Téllez ◽  
Diana Concepción Mex-Álvarez ◽  
José Ramón Cab-Chan
Keyword(s):  
Project Management ◽  
Project Success ◽  
Software Project ◽  
Effective Management ◽  
Software Projects ◽  
Scientific Publications ◽  
Agile Project Management ◽  
Revisión Sistemática ◽  
Basic Concepts ◽  
Agile Software

Agile project management is an iterative approach that allows you to plan and guide project processes that require special speed and flexibility to achieve project success. It is for this reason that today professionals must master the basic concepts of this work as disciplinary or professionalizing competence. The objective of the study lies mainly in compiling recent research, including the last three years, in relation to Agile Software Project Management, its current situation and its application in practice. The study shows the implementation of the methodology proposed by Kitchenham for the systematic literature review (RSL) analyzing 40 scientific publications, concluding that the agile management of software projects allows efficient and effective management with the application of a standard o priority methodology and with the unavoidable use of software tools of specific use for it.

scholarly journals Testing Non-Functional Requirements: Lacking of Technologies or Researching Opportunities?

2016 ◽  
Author(s):  
Victor V. Ribeiro ◽  
Guilherme H. Travassos
Keyword(s):  
Software Testing ◽  
Project Success ◽  
Software Project ◽  
Functional Requirements ◽  
Software Projects ◽  
Technical Literature ◽  
Body Of Knowledge ◽  
Insufficient Amount ◽  
Literature Reviews ◽  
And Performance

Software testing aims to reveal failures due to the lack of conformity (defects) among functional and non-functional requirements and the implemented system. Thus, defects can be identified and fixed, improving software quality. However, despite several works emphasizing the importance of non-functional requirements (NFRs), there is an insufficient amount of software testing approaches dealing with them. The lack of NFR evaluation may be the cause of low-quality software that does not meet users need, influencing software project success. Goal: To organize a body of knowledge regarding NFRs and software testing approaches available in the technical literature and reveal the gaps between testable NFRs and software testing approaches. Method: To perform structured literature reviews to identify NFRs and software testing approaches dealing with testable NFRs. To combine both results, reveal research opportunities and organize a body of knowledge regarding NFRs and software testing approaches. Results: From 224 identified NFRs, 87 were described, and 47 software testing approaches observed. Only eight approaches are empirically evaluated. No testing approaches were identified for 11 testable NFRs. Furthermore, regarding the testing process, we did not observe any testing approach covering the test planning phase. Conclusion: Despite their importance, many testable NFRs seem not be tested due to the lack of appropriate software testing approaches yet. Also, the existing testing approaches do not cover all testing processes activities and, in general, lack empirical evidence about their feasibility and performance, making their use in software projects risky.

Sign in / Sign up

Export Citation Format

Share Document