Software Project Outcome Research Papers (original) (raw)

It is no secret that many projects fail, regardless of the business sector, software projects are notoriously disaster victims, not necessarily because of technological failure, but more often due to their uncertainties. The threats identified by uncertainty in day-to-day of a project are real and immediate and the stakes in a project are often high. This paper presents a systematic review about software project management uncertainties. It helps to identify the difficulties and the actions that can minimize the uncertainties effects in the projects and how managers and teams can prepare themselves for the challenges of their projects scenario, with the aim of contributing to the improvement of project management in organizations as well as contributing to project success.

Software project management is the utilization of resources in efficient manner to complete a project within time and budget. It is like a corner stone in every successful project. Sound software project management techniques are very important for the development of software projects both for organizations that develop outsourced projects and in-house projects. The data was collected through interviews and questionnaire. Most of the respondents were project managers having postgraduate degrees. From analysis it is concluded that project management practices play important role in the successful completion of projects. Sixteen percent of projects had no project plan. Many standard software practices are not being applied constantly in the projects. The risk assessment and mitigation are not carried out until the risk occurs. The role of software project management tools and techniques and their practices are also analyzed in detail in this paper. Many believed that decision making is the most important ability of project managers. In this paper we have described different factors that cause the success or failure of projects. Our results present general guidance for project managers to make sure that their projects be successful. This study shows the importance of project management tools and techniques in the industry. It also shows how project management is important for a successful and quality software product. If a project is managed properly, we get a quality product within allocated time and budget.

- by Basharat Jehan
- •
- Computer Science, Software Engineering, Statistics, Computer Engineering
- by June Verner
- •
- Software Engineering, Project Management, Software Development, Risk assessment
- by Ita Richardson
- •
- Management, Software Engineering, Communication, Intercultural Communication

- by Kamran Ghani and +2
- •
- Computer Science, Software Engineering, Statistics, Requirements Engineering
- by J. Verner
- •
- Software Engineering, Software Project Outcome, Team Motivation

This work is focused on a project that integrates the curriculum such as thermodynamic, chemical reactor
engineering, linear algebra, differential equations and computer programming. The purpose is that
students implement the most knowledge and tools to analyse the stirred tank chemical reactor as a simple
dynamic system. When the students finished this practice they should have learned about analysis of
dynamic system through bifurcation analysis, hysteresis phenomena, find equilibrium points, stability
type, and phase portrait. Once the steps were accomplished, we concluded that the purpose was
satisfactorily reached with an increment in creative ability. The student showed a bigger interesting in
this practice, since they worked in group. The most important fact is that the percentage of failure among
students was 10%. Finally, using alternative teaching-learning process improves the Mexican system
education.

Engineering efficiency in continuous software delivery can be impacted by multiple factors. In this paper, citing one ultra-large-scale software-Intel Media Driver as an example, we analyse the hotspots impacting the engineering efficiency in continuous software delivery, their challenges to our software design and the experiences on software delivery efficiency boost against the targeted design enhancements. We expect the identified hotspots can help more researchers to form the corresponding research agendas and the experiences shared can help following practitioners to apply similar enhancements.

ABSTRACT During discussions with a group of U.S. software developers we explored the effect of software development practices on software project outcomes. Later we asked our practitioners to respond to a questionnaire that covered many important project risk topics. Then, in order to compare practices in different environments, another group of practitioners from the U.S. and a group of practitioners from Australia completed our questionnaire. Most software engineering research stresses the importance of good requirements engineering practices and suggests that they are essential to successful projects. We report on requirements engineering risk practices, including 1) the effects of the sponsor and customer/users, 2) requirements issues, and 3) the project manager and management of the development process, in order to identify early lifecycle factors useful in predicting project outcomes. If project managers are able to identify problematic projects early enough, they can take mitigating action. Our results suggest that the best predictor of project success is that the requirements are completed at some stage during the development process.

ABSTRACT ABSTRACT. While research on project failure tends to supply lists of risk and failure factors, and negative business effects, the objective of this research is to identify specific factors behind failure and who is to blame. We analyze practitioners’ perspectives on 57 development and management factors for projects they considered failures across 70 failed projects. Results show that all projects reviewed suffered 6 to 48 failure factors. While no single set of factors is identified, nearly all projects suffered from organizational factors outside the project manager’s control. We conclude with suggestions to minimize the most common ones. RÉSUMÉ : Tandis que la recherche sur l’échec de projets logiciels tend à fournir des listes de facteurs de risque et d’erreurs, et des effets négatifs sur l’activité des organisations, l’objectif de ces travaux de recherche est d’identifier les facteurs sous-jacents spécifiques et les éléments responsables. Nous analysons le point de vue des spécialistes sur 57 facteurs de développement et de gestion pour des projets qu’ils ont considérés comme des échecs parmi 70 projets infructueux. Les résultats montrent que les projets considérés sont critiques sur 6 à 48 facteurs d’échec. Bien qu’un unique ensemble de facteurs ne soit pas identifié, il s’agit en majorité de facteurs organisationnels hors du contrôle du chef de projet. Nous concluons par des suggestions sur la manière de réduire les plus fréquents. KEYWORDS: software project failure, software project management, failure factors, project risk. MOTS-CLÉS : échec de projet logiciel, gestion de projet logiciel, facteurs d’échec, risque des projets.

In the age of fast evolution, software development project must accept many challenges of unpredicted requirements change and new technology environment. Software development processes should have adjustable and extendable features to meet the multifaceted needs of the users. Iterative and Incremental Development (IID) is a practical approach to overcome the various challenges of software development. However, continuous testing and building new versions need to spend more time and human resources that is a major obstacle of IID. The other, the iterative operations must have a sound communication skills. Lack of standard version control and intercommunication manner often lead to failure of software project. High quality Continuous Integration (CI) environment can effectively make up the defects of IID. In this paper, CI environment and advantages are deeply surveyed. In order to overcome the defects of IID, CI environment needs combine the perfect procedures and qualified tools, and concretely enhance the quality of CI environment. Based on the process quality measurement model, this paper proposes the Process Quality Improvement Mechanism (PQIM). Applying PQIM, in software development, the processes problems and the CI environment quality defects can identify timely and indeed revise to reduce the risk of CI environment.

The question raised here is about the extent that liberal individualism and the consumerist ethos is the result of technology and to what extent is it the cultural norm of modernity. There has been a polarization in the way technology is understood. Predominantly it is assumed to be neutral but it can also be argued that technology exacerbates the understanding of people as ‘rational individual utility maximisers.’ C.A. Bowers argues that computer technology amplifies the conduit model of learning. The machine stores information and the student learns how to retrieve it and this constitutes neutral and objective research. Bowers advocates critical enquiry and an awareness of the socio-cultural factors that contribute to the generation of knowledge and community. The physiological parameters of machines are neither neutral nor strictly political. Technology shifts the constraints of phenomenological experience and encourages new and arguably impoverished ways of experiencing the world. However, by insisting on a critical dimension to understanding technology we could be able to transform education from its emphasis on vocationalism and governmentality to a more creative, equitable, and ecological set of factors.

- by Ruth Irwin
- •
- Critical Theory, Cultural Studies, Social Theory, Computer Science
- by June Verner
- •
- Software Engineering, Software Project Outcome, Team Motivation

The focus of this paper is to outline the experience of a European based software organization utilizing the IDEAL model, while implementing a tailored Capability Maturity Model (CMM) software process improvement program. The goal was to achieve process improvement rather than a specific CMM maturity level. In doing this, the IDEAL model was extensively researched and employed. The benefits and limitations of the IDEAL model are presented as experienced. Further details on this research are available in [1]. Research was carried out on a number of software process improvement paradigms prior to the selection of the CMM. A key element of this approach was to see the requirements of the organization as paramount and immediate. It was deemed important to achieve process improvement in specific Key Process Areas regardless of their position in the CMM. This provided the flexibility for future investment in SPI to capitalize on the current work.

Today software development has truly become a globally sourced commodity. This trend has been facilitated by the availability of highly skilled software professionals in low cost locations in Eastern Europe, Latin America and the Far East. Organisations endeavouring to leverage the opportunities this provides and to avail of the benefits of establishing operations close to emerging markets have embraced this strategy in large numbers. Software testing plays a key role in delivering high quality products and is a labour intensive, complex and expensive activity. In the context of Global Software Development (GSD) to date testing has been perceived as a well defined task that is relatively straightforward and lends itself to being outsourced or offshored. This volume considers this specific topic and demonstrates that testing in a GSD environment is not a simple activity. It is prone to be negatively impacted by all the factors associated with distributed software development.This work also provides practical solutions which can be utilised to address these important issues. While the primary focus of this work is software testing it is also the culmination of 10 years research by the author in the area of GSD. During this period he has considered all aspects of the software development life cycle. This experience and knowledge has been incorporated into this volume. It is therefore relevant to note this work is of value to the wider software community not just to those interested in testing. It specifically considers the establishment of virtual teams and their efficient and effective operation. Therefore this book has relevance to all those interested in implementing or improving a GSD strategy. Its particular strengths are that while it is a scholarly work it is industry based and practical