Software development projects: An investigation into the factors that affect software project success/ failure in Jordanian firms

2008 ◽  
Author(s):  
Moh'd M. I. Tarawneh ◽  
Haroon AL-Tarawneh ◽  
Asim Elsheikh
Keyword(s):  
Software Development ◽  
Project Success ◽  
Development Projects ◽  
Software Project

scholarly journals Rethinking success in software projects

Tehnika ◽  
2020 ◽  
Vol 75 (6) ◽  
pp. 639-645
Author(s):  
Zorica Mitrović ◽  
Dejan Petrović ◽  
Marko Mihić
Keyword(s):  
Literature Review ◽  
Software Development ◽  
Project Success ◽  
Three Dimensions ◽  
Development Projects ◽  
Software Project ◽  
Software Projects ◽  
Multidimensional Construct ◽  
Strategic Project ◽  
Clear Line

In recent years, one of the most important topics in the field of software development projects is rethinking success in context of increasing complexity and failure of software projects. Literature review shows that there is no clear line between success and failure, especially considering that a project can be both successful in one area and unsuccessful in another. In addition, the increasing complexity, context and broader conceptualization of projects, required both change in project and success definition. The aim of this paper is to perform literature review in field of software project success definition, as well as to propose a multidimensional construct that includes project management success, project success and strategic project success as three dimensions for measuring software's project success.

Empirical comparison of traditional plan-based and agile methodologies

2017 ◽  
Vol 30 (3) ◽  
pp. 400-453 ◽  
Author(s):  
Arthur Ahimbisibwe ◽  
Urs Daellenbach ◽  
Robert Y. Cavana
Keyword(s):  
Software Development ◽  
Project Success ◽  
Time Budget ◽  
Project Managers ◽  
Development Projects ◽  
Potential Threat ◽  
Content Type ◽  
Agile Methodologies ◽  
Project Objectives ◽  
Practical Implications

Purpose Aligning the project management methodology (PMM) to a particular project is considered to be essential for project success. Many outsourced software projects fail to deliver on time, budget or do not give value to the client due to inappropriate choice of a PMM. Despite the increasing range of available choices, project managers frequently fail to seriously consider their alternatives. They tend to narrowly tailor project categorization systems and categorization criterion is often not logically linked with project objectives. The purpose of this paper is to develop and test a contingency fit model comparing the differences between critical success factors (CSFs) for outsourced software development projects in the current context of traditional plan-based and agile methodologies. Design/methodology/approach A theoretical model and 54 hypotheses were developed from a literature review. An online Qualtrics survey was used to collect data to test the proposed model. The survey was administered to a large sample of senior software project managers and practitioners who were involved in international outsourced software development projects across the globe with 984 valid responses. Findings Results indicate that various CSFs differ significantly across agile and traditional plan-based methodologies, and in different ways for various project success measures. Research limitations/implications This study is cross-sectional in nature and data for all variables were obtained from the same sources, meaning that common method bias remains a potential threat. Further refinement of the instrument using different sources of data for variables and future replication using longitudinal approach is highly recommended. Practical implications Practical implications of these results suggest project managers should tailor PMMs according to various organizational, team, customer and project factors to reduce project failure rates. Originality/value Unlike previous studies this paper develops and empirically validates a contingency fit model comparing the differences between CSFs for outsourced software development projects in the context of PMMs.

Evaluation of Project Architecture in Software Development Mixing Waterfall and Agile by Using Process Simulation

2017 ◽  
Vol 02 (02) ◽  
pp. 1750007
Author(s):  
Taiga Mitsuyuki ◽  
Kazuo Hiekata ◽  
Takuya Goto ◽  
Bryan Moser
Keyword(s):  
Software Development ◽  
Process Simulation ◽  
System Development ◽  
Development Project ◽  
Development Projects ◽  
Software Project ◽  
Conditional Response ◽  
Agile Process ◽  
Requirement Changes ◽  
The Impact

For software development, especially massive software systems, a waterfall process is used traditionally. A waterfall process can be highly effective on the condition that a master plan is fixed and the possibility of changes and uncertain rework is low. However, in software development projects, many kinds of reworks occur corresponding to uncertain requirement changes and program bugs. In addition, with the advent of cloud-based software platforms and continuous development operations, it is possible to develop a software system while operating the system. To respond to this situation, software development projects often adopt an agile process. Agility may allow conditional response to uncertain rework, yet at the same time it may be difficult to control the achievement of known project targets. Recently, many cases of adopting mixed processes including waterfall and agile have been reported in the massive software development projects. In this paper, we argue that the mixed process architecture should be designed, considering the scale of the targeted software project, the culture of organization, the probability of uncertain requirement changes, and so on. This paper proposes a methodology of evaluating the impact of waterfall, agile, and mixed project architectures by using process simulation. A project architectural approach is evaluated with a simulator which includes a software reliability growth model and uncertain rework driven by requirement change and error propagation. The proposed methodology was applied to a development project for a simple shopping website. The results showed that the proposed methodology allows exploration of partial agile adoption depending on the nature of the system development project, including its scale and chances of change. For example, in this paper, if the scale of the project is small, the positive effect of increasing agility by adopting agile processes is low. On the other hand, if the scale of the project is large, the effect of increasing agility by adopting agile process can increase. Furthermore, it became clear that it is important to not apply an agile process blindly, but instead to design a mixed project architecture considering the number of errors and development schedule targets across the project scope.

scholarly journals Designing An Application of Software Project Management By Using Framework Scrum (SPM-Scrum)

2021 ◽  
Vol 6 (1) ◽  
pp. 25
Author(s):  
Nurudin Santoso ◽  
Faizatul Amalia
Keyword(s):  
Data Analysis ◽  
Software Development ◽  
System Architecture ◽  
Development Projects ◽  
Software Project ◽  
Or Management ◽  
Main Obstacle ◽  
Front End ◽  
System Architecture Design ◽  
Thesis Work

Most of failures of startup application in many countries reached 75%, while the startup failures in Indonesia reached 90%. These failures were caused by non-technical or management factors in managing startup. The RPL (Software Engineering) Laboratory of FILKOM of Brawijaya University has a roadmap to develop an application to guarantee the success of a management software project. The data analysis had been performed on FILKOM student’s thesis work which generally develops software that has main obstacle in the management. A study solution which was developed through scientific SDLC and PMLC combined with Scrum method becomes an application named SPM-SCRUM. The results of analysis carried out on several software development projects refer to the Iterative SDPM process. Furthermore, the strategy of Iterative SDPM combined with Scrum method produces a system architecture design that separates the Front End and Back End

scholarly journals Juego lúdico GetKanban Game para apoyar el proceso de enseñanza aprendizaje de la disciplina de gestión de proyectos de software en los estudiantes de TIC`S

2020 ◽  
Vol 6 (3) ◽  
pp. 27-34
Author(s):  
E.J. Robles Gómez ◽  
J.A. Flores Lara ◽  
J.C. Ontiveros Neri
Keyword(s):  
Project Management ◽  
Software Engineering ◽  
Software Development ◽  
Systems Engineering ◽  
Educational Institution ◽  
Development Projects ◽  
Software Project ◽  
Software Projects ◽  
Teaching Learning ◽  
On Time Delivery

El juego getKanban es una herramienta para enseñar la metodología Kanban y SCRUM de una manera divertida. Facilita la enseñanza de la gestión de proyectos de software a través de un juego de mesa, donde los jugadores aprenden a formular estrategias de gestión de proyectos y las implementan para elaborar proyectos de calidad en tiempo y forma. El presente artículo muestra los resultados de la implementación del juego en una institución educativa de nivel superior, con alumnos de Ingeniería en Sistemas Computacionales de octavo semestre. Se puede apreciar que al utilizar este juego ayuda de manera efectiva a la enseñanza de Kanban y SCRUM, para la gestión de proyectos de software. Por lo cual se recomienda poder implementar este tipo de juegos como estrategia didáctica para la enseñanza/aprendizaje de Ingeniería de Software aplicada a la Gestión de Proyectos de Desarrollo de Software. The game Kanban is a tool to teach the methodology in a fun way. It facilitates the teaching of software project management through where players learn to formulate strategies and implement them to develop quality projects on time Delivery. This article shows the results of the implementation of the game in an educational institution of higher level, with students of Computer Systems Engineering eighth semester. It can be seen that by using this game it helps in an effective way to teach Kanban for the management of software projects. Therefore, it is recommended to be able to implement this type of games as a didactic strategy for the teaching / learning of Software Engineering applied to the Management of Software Development Projects

A Framework for Risk Management in AI System Development Projects

2019 ◽  
pp. 1-20
Author(s):  
Kitti Photikitti ◽  
Kitikorn Dowpiset ◽  
Jirapun Daengdej
Keyword(s):  
Artificial Intelligence ◽  
Risk Management ◽  
Project Management ◽  
Software Development ◽  
System Development ◽  
Systems Development ◽  
Development Projects ◽  
Software Project ◽  
Software Projects ◽  
Very High

It has been well-known that the chance of successfully delivering a software project within an allocated time and budget is very low. Most of the researches in this area have concluded that “user's requirements” of the systems is one of the most difficult risks to deal with in this case. Interestingly, until today, regardless of amount of effort put into this area, the possibility of project failure is still very high. The issue with requirement can be significantly increased when developing an artificial intelligence (AI) system, where one would like the systems to autonomously behave. This is because we are not only dealing with user's requirements, but we must also be able to deal with “system's behavior” that, in many cases, do not even exist during software development. This chapter discusses a preliminary work on a framework for risk management for AI systems development projects. The goal of this framework is to help project management in minimizing risk that can lead AI software projects to fail due to the inability to finish the projects on time and within budget.

Software Project Managers’ Risk Preferences

1996 ◽  
Vol 11 (4) ◽  
pp. 287-295
Author(s):  
Thomas W. Lauer
Keyword(s):  
Software Development ◽  
Prospect Theory ◽  
Expected Utility ◽  
Utility Theory ◽  
Risk Preferences ◽  
Expected Utility Theory ◽  
Project Managers ◽  
Development Projects ◽  
Software Project ◽  
Potential Importance

A questionnaire was administered to 68 software project managers (SPMs). Questions were designed to test whether SPMs’ risky judgments were more consistent with Expected Utility Theory or Prospect Theory. Although the results were more consistent with Prospect Theory, they differed in important ways showing SPMs’ judgments to be less homogeneous than is assumed by either theory. These results highlight the potential importance of SPMs’ judgments to the outcome of software development projects.

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.

Managing Software Development Projects for Success: Aligning Plan- and Agility-Based Approaches to Project Complexity and Project Dynamism

2019 ◽  
Vol 51 (3) ◽  
pp. 262-277 ◽  
Author(s):  
Charles W. Butler ◽  
Leo R. Vijayasarathy ◽  
Nicholas Roberts
Keyword(s):  
Project Management ◽  
Software Development ◽  
Project Success ◽  
Management Approach ◽  
Development Projects ◽  
Negative Effects ◽  
Project Approach ◽  
Project Outcomes ◽  
Project Complexity ◽  
Management Approaches

In general, project complexity and project dynamism are recognized as potent characteristics that influence, usually in a negative way, the outcome of software development projects. However, with respect to the two dominant paradigms for managing software development projects (i.e., plan-based project approach and agility-based project approach), there is less agreement as to which one is better. Emerging research suggests that the preeminence of one approach over another is a matter of fit between the project management approach and the project context, including its complexity and dynamism. We contribute to this line of research by studying the moderating influence of the two project management approaches on the relationship between project complexity and project dynamism on project outcomes. Our analysis of data gathered from a survey of software development professionals shows that managing dynamism is critical for realizing project success, and an agility-based project approach is best suited for mitigating dynamism’s negative effects on project success.

Business knowledge requirements and onsite offshore work division in Indian software outsourcing projects

2015 ◽  
Vol 8 (1) ◽  
pp. 76-101 ◽  
Author(s):  
Debasisha Mishra ◽  
Biswajit Mahanty
Keyword(s):  
Software Development ◽  
Software Industry ◽  
Project Work ◽  
Development Projects ◽  
Software Project ◽  
Content Type ◽  
Software Outsourcing ◽  
Operation Process ◽  
Expert Interview ◽  
Knowledge Requirements

Purpose – The purpose of the paper is to find out the knowledge requirements and its effect on both onsite and offshore project work division for development, re-engineering and maintenance projects in Indian outsourcing software industry in different phases of software development. Design/methodology/approach – This study employs an expert interview approach in Indian software industry to find out knowledge requirement for project execution and division of work between onsite and offshore locations. The requisite data were collected through expert interviews and direct observations. Findings – The study found that the development projects require higher level of domain, strategic, business process and operation process knowledge in comparison to re-engineering and maintenance projects. So there is a need of higher onsite presence in development projects. The maintenance work is taken up at the offshore location in a phase-wise manner. Research limitations/implications – The implication of the study is in the development of a broad framework of knowledge requirements and work division in on-shore and offshore locations for Indian software outsourcing projects. As the study is based on expert opinion in the context of India, it cannot be generalized for outsourcing scenarios elsewhere. Practical implications – The software project manager can use the findings to get more insight into the project and divide the software team between onsite and offshore location. Originality/value – The study is novel, as there is little attempt at finding the knowledge requirement to execute various kinds of business software development in outsourcing environment in the context of India.

Sign in / Sign up

Export Citation Format

Share Document