Agile Software Development for Customizing ERPs

2010 ◽  
pp. 20-39 ◽  
Author(s):  
Rogério Atem de Carvalho ◽  
Prof. Björn Johansson ◽  
Rodrigo Soares Manhães
Keyword(s):  
Software Development ◽  
Great Part ◽  
Fast Response ◽  
The Other ◽  
Agile Methods ◽  
Complex Task ◽  
Agile Practices ◽  
Agile Approach ◽  
Agile Software ◽  
Business Requirements

Customization of ERP systems is a complex task, and great part of this complexity is directly related to requirements management. In this context, a well-known problem is the misfit between the ERP functionalities and the business requirements. This problem comprises communication bottlenecks and difficulties on responding to changes. The proposals for minimizing these misfits are mostly focused on traditional, heavyweight waterfall-like approaches for software development. On the other side, the last decade has witnessed the rise and growth of Agile methods, which have both close communication and fast response to changes among their main values. This chapter maps some of the main agile practices to ERP customization processes, using, where applicable, practices from a real-world ERP project. Moreover, some limitations on the agile approach to ERP customization are presented and discussed.

scholarly journals Optimizing the Self-Organizing Team Size Using a Genetic Algorithm in Agile Practices

2018 ◽  
Vol 29 (1) ◽  
pp. 1151-1165
Author(s):  
Wael Almadhoun ◽  
Mohammad Hamdan
Keyword(s):  
Genetic Algorithm ◽  
Software Development ◽  
Objective Function ◽  
The Self ◽  
Performance Characteristics ◽  
Team Size ◽  
Agile Practices ◽  
Team Characteristics ◽  
Agile Software ◽  
Self Organizing

Abstract In agile software processes, the issue of team size is an important one. In this work we look at how to find the optimal, or near optimal, self-organizing team size using a genetic algorithm (GA) which considers team communication efforts. Communication, authority, roles, and learning are the team’s performance characteristics. The GA has been developed according to performance characteristics. A survey was used to evaluate the communication weight factors, which were qualitatively assessed and used in the algorithm’s objective function. The GA experiments were performed in different stages: each stage results were tested and compared with the previous results. The results show that self-organizing teams of sizes ranged from five to nine members scored more. The model can be improved by adding other team characteristics, i.e. software development efforts and costs.

Exploring the Role of Project Management in the Development of the Academic Agile Software Discourse: A Bibliometric Analysis

2017 ◽  
Vol 48 (1) ◽  
pp. 3-18 ◽  
Author(s):  
Thomas G. Lechler ◽  
Siwen Yang
Keyword(s):  
Project Management ◽  
Software Development ◽  
Bibliometric Analysis ◽  
Agile Methods ◽  
Management Research ◽  
Practical Applications ◽  
Time Period ◽  
Time Periods ◽  
Agile Software

The practical applications of agile methods and their impact on the productivity and efficiency of software development dominate the agile literature. We analyzed 827 academic articles with bibliometric techniques to explore the role project management research played in the development of the academic agile discourse. Bibliometric analyses over two time periods reveal that project management–related topics form a distinct stream of research in the second time period but not in the first. Furthermore, our results reveal that the academic agile discussion has been mainly unidirectional. This situation offers many opportunities for project management researchers to contribute to the agile discourse.

Agile Software

2014 ◽  
pp. 96-116
Author(s):  
Zaidoun Alzoabi
Keyword(s):  
Software Engineering ◽  
Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Changing Environment ◽  
Agile Methodology ◽  
Agile Software

The term Agile Method of software development was coined in the 2001.This approach is characterized with creativity, flexibility, adaptability, responsiveness, and human-centricity. Researchers have suggested that the complex, uncertain, and ever-changing environment is pushing developers to adopt agile methods rather than traditional software development. Agile methodologist claim that their Agile methods is the answer for the software engineering chaotic situation, in which projects are exceeding their time and budget limits, requirements are not fulfilled, and consequently ending up with unsatisfied customers. In this chapter we will explain agile methodology, its general characteristics, and quick description of the famous agile methods known in the industry and research.

A Framework for Analyzing Structural Mechanisms Deployed to Support Traditional and Agile Methods

2021 ◽  
pp. 205-227
Author(s):  
Michal Dolezel ◽  
Alena Buchalcevova
Keyword(s):  
Software Development ◽  
Classification Scheme ◽  
Organizational Structures ◽  
Agile Software Development ◽  
Agile Methods ◽  
Two Dimensional ◽  
Dimensional Classification ◽  
Agile Software ◽  
Structural Mechanisms ◽  
Development Methods

People rely on structures to make their worlds orderly. This chapter conceptually probes into the problem of the differences between organizational structures deployed in traditional and agile environments. The authors develop an argument that all common forms of organizational entities can be classified by involving a two-dimensional classification scheme. Specifically, they constructed a typology to examine the issues of formal vs. informal authority, and disciplinarity vs. cross-functionality in terms of their significance for traditional and agile software development workplaces. Some examples of concrete organizational forms—including traditional project team, independent test team, self-organizing agile team and developers' community of practice—are discussed. In sum, they argue that by employing this classification scheme, they can theorize the nature of the on-going structural shift observed in conjunction with deploying agile software development methods. They acknowledge that the structures have fundamentally changed, terming the move “democratization” in the software development workplace.

Extending Security in Agile Software Development Methods

2007 ◽  
pp. 143-159 ◽  
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
R. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Management Standards ◽  
Secure Information ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

Extending Security in Agile Software Development Methods

2008 ◽  
pp. 845-858
Author(s):  
M. Siponen ◽  
R. Baskerville ◽  
T. Kuivalainen
Keyword(s):  
Information Systems ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Agile Method ◽  
Management Standards ◽  
Secure Information ◽  
Agile Software ◽  
Development Methods ◽  
Software Development Methods

Software developers can use agile software development methods to build secure information systems. Current agile methods have few (if any) explicit security fea-tures. While several discrete security methods (such as checklists and management standards) can supplement agile methods, few of these integrate seamlessly into other software development methods. Because of the severe constraints imposed by agile methods, these discrete security techniques integrate very poorly into agile approaches. This chapter demonstrates how the security features can be integrated into an agile method called feature driven development.

scholarly journals Adopting to Agile Software Development

2014 ◽  
Vol 16 (1) ◽  
pp. 64-70 ◽  
Author(s):  
Gusts Linkevics
Keyword(s):  
Expert System ◽  
Reference Material ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Methods ◽  
Complex Process ◽  
Agile Software

Abstract Agile software development can be made successful, but there is no well-defined way how to achieve this. The problem is that the successful adoption of agile methods and practices is a complex process and this process should be customizable for a particular organization or a team. This research focuses on identification of agile methods and practices. Result of the research is the ranking of agile methods, practices and their usage trends. As some terms of agile software development are interpreted differently in different organizations and teams, terminology used is analyzed. Results of the research can be used as a reference material for those who are planning to adopt agile methods or are looking for the next agile practice to implement. Results will be used for the development of an expert system to support agile adoption.

scholarly journals Applications supporting utilization of agile methods in software development process

2020 ◽  
Vol 14 ◽  
pp. 8-13
Author(s):  
Tomasz Bławucki ◽  
Siarhei Ramanovich ◽  
Maria Skublewska-Paszkowska
Keyword(s):  
Software Development ◽  
Development Process ◽  
Agile Software Development ◽  
Agile Methods ◽  
Tabular Form ◽  
Software Development Process ◽  
Internet Applications ◽  
Technical Requirements ◽  
Development Processes ◽  
Agile Software

The article presents a comparison in terms of hardware requirements of applications that supports the agile software development processes. For research purposes, popular mobile and internet applications supporting agile software development were chosen. In order to determine the significance of individual technical requirements for end-users, a series of research experiments, based on scenarios of typical and boundary use was conducted. In addition to research, the application supporting agile software development process was implemented. The results of research were recorded by specialized monitoring and profiling tools. The results of performed work are presented in tabular form.

scholarly journals REACT-M: uma Abordagem Ágil para o Gerenciamento de Requisitos de Software

2020 ◽  
Author(s):  
Bleno Wilson Frankiin Vale da Silva ◽  
Aline Franciele dos Anjos Lima ◽  
Sandro Ronaldo Bezerra Oliveira ◽  
André Luiz Coelho Pinheiro
Keyword(s):  
Software Requirements ◽  
Agile Methods ◽  
Requirements Management ◽  
Quality Models ◽  
Agile Methodologies ◽  
Agile Practices ◽  
Literature Mapping ◽  
Agile Approach ◽  
Requirements Development

Agile methods provide support to software engineeringactivities, aiming to reduce some of problems of the traditionalapproaches. Quality products can be developed by agilemethodology in less time and budget. Requirements engineeringis a building block of software development. Therefore, thesearch for agile practices for the evolution of requirementsbecomes relevant. Although several researches have been carriedout on the role of requirements engineering in agilemethodologies, there is still a need for studies that seek to alignagile approaches to requirements development and managementprocesses that satisfy highly accepted quality models in themarket. This paper aims to establish an agile approach tosupport software requirements management, based on asystematic literature mapping that draws on existing approachesin agile methodologies that support requirements managementactivities.

scholarly journals Enhancing research informatics core user satisfaction through agile practices

JAMIA Open ◽  
2021 ◽  
Vol 4 (4) ◽  
Author(s):  
Andrew R Post ◽  
Jared Luther ◽  
J Maxwell Loveless ◽  
Melanie Ward ◽  
Shirleen Hewitt
Keyword(s):  
Best Practices ◽  
Software Development ◽  
User Satisfaction ◽  
Best Practice ◽  
Turnaround Time ◽  
Agile Software Development ◽  
User Engagement ◽  
Full Time ◽  
Agile Practices ◽  
Agile Software

Abstract Objective The Huntsman Cancer Institute Research Informatics Shared Resource (RISR), a software and database development core facility, sought to address a lack of published operational best practices for research informatics cores. It aimed to use those insights to enhance effectiveness after an increase in team size from 20 to 31 full-time equivalents coincided with a reduction in user satisfaction. Materials and Methods RISR migrated from a water-scrum-fall model of software development to agile software development practices, which emphasize iteration and collaboration. RISR’s agile implementation emphasizes the product owner role, which is responsible for user engagement and may be particularly valuable in software development that requires close engagement with users like in science. Results All RISR’s software development teams implemented agile practices in early 2020. All project teams are led by a product owner who serves as the voice of the user on the development team. Annual user survey scores for service quality and turnaround time recorded 9 months after implementation increased by 17% and 11%, respectively. Discussion RISR is illustrative of the increasing size of research informatics cores and the need to identify best practices for maintaining high effectiveness. Agile practices may address concerns about the fit of software engineering practices in science. The study had one time point after implementing agile practices and one site, limiting its generalizability. Conclusions Agile software development may substantially increase a research informatics core facility’s effectiveness and should be studied further as a potential best practice for how such cores are operated.

Sign in / Sign up

Export Citation Format

Share Document