Hybrid Approaches of Verbal Decision Analysis in the Selection of Project Management Approaches

AbstractDecision support methods aim at assisting in the decision-making process by simplifying the analysis of the problem and justifying the choice of a particular potential action. Recent researches have shown that the hybridization of methods is able to overcome limitations presented by the methods when applied separately: the classification of alternatives before submitting them to an ordination methodology would be an e ective way of filtering the set to be ordered. Specific Practices of Capability Maturity Model Integration were analyzed through a decision making model, assisted by the methods SAC and ZAPROS III-i. The results will be compared to previous studies

Communication, culture, competency, and stakeholder that contribute to requirement elicitation effectiveness

In the context of software development, requirement engineering is one of the crucial phases that leads to software project success or failure. According to several disruptive changes in the software engineering landscape as well as the world’s challenge of virus pandemic, the provision of practical and innovative software applications is required. Therefore, issues resolution in requirement elicitation is potentially one of the key success factors resulting in enhanced quality of system requirement. The authors have striven to create new ways of requirement elicitation according to factor effects of communication, culture, competency, and stakeholder, by incorporating tools, processes, methods, and techniques to solve the problems comprehensively, and then proposed an adaptive and applicable conceptual framework. To illustrate these effects, the authors performed a literature review from the past 8 years, and then data analysis from interviews of 27 practitioners, observations and focus groups of software development in real-life projects

A software process assessment model and a tool for XP@SCRUM agile method

Text in English; Abstract: EnglishIncludes bibliographical references (leaves 86-88)xi, 91 leavesIn today's fast and competitive world, Agile Methods has become popular by software producers because for their high-speed, flexibility and responding to change quickly. These methods have been criticized as undisciplined way of hacking. However, these methods are disciplined processes that incorporate good engineer and management practices, albeit with extreme implementations tailored to a specific kind of environment. [35] Mark Paulk showed that organizations applying XP can reach CMM Level 2 and Level3. These methods do not have improvement guide and capability determination. There might be differences between the organizations applying these methods. In this thesis, I will propose a software process assessment model and a tool for proposed model. My approach is selecting an assessment model as a guide and selecting an agile method as target method

Agile methods in biomedical software development: a multi-site experience report

BACKGROUND: Agile is an iterative approach to software development that relies on strong collaboration and automation to keep pace with dynamic environments. We have successfully used agile development approaches to create and maintain biomedical software, including software for bioinformatics. This paper reports on a qualitative study of our experiences using these methods. RESULTS: We have found that agile methods are well suited to the exploratory and iterative nature of scientific inquiry. They provide a robust framework for reproducing scientific results and for developing clinical support systems. The agile development approach also provides a model for collaboration between software engineers and researchers. We present our experience using agile methodologies in projects at six different biomedical software development organizations. The organizations include academic, commercial and government development teams, and included both bioinformatics and clinical support applications. We found that agile practices were a match for the needs of our biomedical projects and contributed to the success of our organizations. CONCLUSION: We found that the agile development approach was a good fit for our organizations, and that these practices should be applicable and valuable to other biomedical software development efforts. Although we found differences in how agile methods were used, we were also able to identify a set of core practices that were common to all of the groups, and that could be a focus for others seeking to adopt these methods

Agile Processes in Software Engineering and Extreme Programming: 18th International Conference, XP 2017, Cologne, Germany, May 22-26, 2017, Proceedings

agile software development; lean development; scrum; project management; software developmen

Social conduct, learning and innovation: an abductive study of the dark side of agile software development

Agile methodologies have been adopted by an increasing number of organizations to improve their responsiveness. However, few studies have empirically analysed the effect of Agile on long-term organizational goals such as learning and innovation. Using an abductive approach, this study examines the relationships between self-regulated teams’ social conduct and their resulting learning and innovation. Results indicate that the perceived time pressure to get the job done greatly impedes team engagement in learning and innovation activities. Time pressure is affected by the various control strategies deriving from the implementation of Agile, which constitute its dark side: concertive, belief, diagnostic and boundary controls

Teaching How to Select an Optimal Agile, Plan-Driven, or Hybrid Software Development Approach: Lessons from Enterprise Software Development Leaders

Over 20 years after introducing and popularizing agile software development methods, those methods have proven effective in delivering projects that meet agile assumptions. Those assumptions require that projects be small and simple in scope and utilize small, colocated teams. Given this success, many agile advocates argue that agile should replace plan-driven methods in most or all project contexts, including those projects that deviate significantly from agile assumptions. However, today’s reality is that a diversity of agile, plan-driven, and hybrid approaches continue to be widely used, with many individual organizations using multiple approaches across different projects. Furthermore, while agile advocates argue that the primary barrier to agile adoption is the inertia of traditional organizational cultures, there are, in fact, many rational motivations for utilizing plan-driven and hybrid methods based on individual project characteristics. For information systems students, this creates confusion in two ways: 1) understanding that there is no single best way to develop software in all circumstances but, rather, teams should choose an optimal project approach based on project characteristics, and 2) unpacking and analyzing the wide range of project characteristics – including multiple dimensions in functional requirements, non-functional requirements (NFRs), and team characteristics – that impact that choice. This paper addresses both sources of confusion by utilizing case studies from 22 interviews of enterprise software development leaders. The paper analyzes each case utilizing a “home grounds” model that graphically portrays key project characteristics and their impact on the optimal choice of software development project approach

How to Design a Successful Digital Product? An Analytic Hierarchy Process (AHP) Analysis of Expert Opinions from the Berlin Start-up Scene

Designing the best digital product is vital for the competitiveness of any organization. Thus, this paper aims to determine the critical success design factors and to create guidelines for start-up founders, product managers, designers and entrepreneurs on how to design a successful digital product. To this end, six key design factors and 24 respective sub-factors were identified based on literature and expert opinions. Further, 21 experts were surveyed regarding their priorities on these factors, using the analytic hierarchy process (AHP). The results suggest that high-level planning design is the most important success factor, while having clear product vision, discovery, strategy and goals, building a great user experience, and creating an aesthetic user interface are the top three priority sub-factors for successful digital products

Management Strategies for Adopting Agile Methods of Software Development in Distributed Teams

Between 2003 and 2015, more than 61% of U.S. software development teams failed to satisfy project requirements, budgets, or timelines. Failed projects cost the software industry an estimated 60 billion dollars. Lost opportunities and misused resources are often the result of software development leaders failing to implement appropriate methods for managing software projects. The purpose of this qualitative multiple case study was to explore strategies software development managers use in adopting Agile methodology in the context of distributed teams. The tenets of Agile approach are individual interaction over tools, working software over documentation, and collaboration over a contract. The conceptual framework for the study was adapting Agile development methodologies. The targeted population was software development managers of U.S.-based companies located in Northern California who had successfully adopted Agile methods for distributed teams. Data were collected through face-to-face interviews with 5 managers and a review of project-tracking documentation and tools. Data analysis included inductive coding of transcribed interviews and evaluation of secondary data to identify themes through methodological triangulation. Findings indicated that coaching and training of teams, incremental implementation of Agile processes, and proactive management of communication effectiveness are effective strategies for adopting Agile methodology in the context of distributed teams. Improving the efficacy of Agile adoption may translate to increased financial stability for software engineers across the world as well as accelerate the successful development of information systems, thereby enriching human lives