scholarly journals Agile Practices in Indian Organizations

2017 ◽  
Vol 10 (2) ◽  
pp. 422-428
Author(s):  
Uma Kumari
Keyword(s):  
Software Development ◽  
Web Based ◽  
Total Percentage ◽  
Software Production ◽  
Stakeholder Requirement ◽  
Agile Practices ◽  
Interview Survey ◽  
Agile Software ◽  
One Way Anova ◽  
Online Web

Agile software development is a conceptual framework that promotes development using iterations throughout the project development. In software development Agile means quick moving. For the satisfaction of customer and to cope up customer frequent changed requirements, heavyweight methodology is being kicked. Two major challenges in software development are high quality software production and stakeholder requirement meeting. An independent online web based survey; interview survey and questionnaire survey were conducted. Motive was to find the total percentage of users in India, who are using Agile and it was tried to find out “does it increase the productivity, quality and cost of software?” Hypothesis has been proved using statistical one way ANOVA method. Different Hypothesis that are designed

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.

Agile Software Engineering

2010 ◽  
pp. 28-37
Author(s):  
Ernest Mnkandla
Keyword(s):  
Software Development ◽  
Production Process ◽  
Software Products ◽  
Agile Methodologies ◽  
Software Productivity ◽  
Software Production ◽  
Agile Software Engineering ◽  
Development Approach ◽  
Agile Software ◽  
Traditional Approaches

This chapter aims to reveal agile techniques that have been applied to software development and have resulted in meaningful improvements in software productivity. Available literature generally state some claims on the gains associated with the use of particular agile methodologies in software development. What lacks however, is a comprehensive analysis of how the application of agile techniques as a family will lead to improvement in software productivity. This chapter therefore provides such details. Software productivity techniques provide ways of measuring three things in order to determine the productivity of software; software products, software production processes and structures, and software production setting. Agile methodologies improve software productivity by focusing on the software production process and structures. The fundamental concern of this chapter is to show that agile methodologies measure the production process activities in a different but effective way from the more traditional approaches. For example, time-to-market is reduced by use of an iterative incremental development approach.

scholarly journals Modelling the critical success factors of agile software development projects in South Africa

2017 ◽  
Vol 19 (1) ◽  
Author(s):  
Tawanda B. Chiyangwa ◽  
Ernest Mnkandla
Keyword(s):  
South Africa ◽  
Software Development ◽  
Critical Success Factors ◽  
Success Factors ◽  
Great Influence ◽  
Development Projects ◽  
Web Based ◽  
Critical Success ◽  
Agile Software ◽  
Organisational Factors

Background: The continued in failure of agile and traditional software development projects have led to the consideration, attention and dispute to critical success factors that are the aspects which are most vital to make a software engineering methodology fruitful. Although there is an increasing variety of critical success factors and methodologies, the conceptual frameworks which have causal relationship are limited.Objective: The objective of this study was to identify and provide insights into the critical success factors that influence the success of software development projects using agile methodologies in South Africa.Method: Quantitative method of collecting data was used. Data were collected in South Africa through a Web-based survey using structured questionnaires.Results: These results show that organisational factors have a great influence on performance expectancy characteristics.Conclusion: The results of this study discovered a comprehensive model that could provide guidelines to the agile community and to the agile professionals.

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.

Quality Assurance in Agile Software Development

2014 ◽  
pp. 155-176 ◽  
Author(s):  
Iwona Dubielewicz ◽  
Bogumila Hnatkowska ◽  
Zbigniew Huzar ◽  
Lech Tuzinkiewicz
Keyword(s):  
Quality Assurance ◽  
Life Cycle ◽  
Best Practices ◽  
Software Development ◽  
Software Quality ◽  
Agile Software Development ◽  
Software Life Cycle ◽  
Agile Methodologies ◽  
Agile Practices ◽  
Agile Software

Agile methodologies have become very popular. They are defined in terms of best practices, which aim at developing good quality software faster and cheaper. Unfortunately, agile methodologies do not refer explicitly to quality assurance, which is understood as a planned set of activities performed to provide adequate confidence that a product conforms to established requirements, and which is performed to evaluate the process by which products are developed. The chapter considers the relations of agile practices with software life cycle processes, especially those connected to quality assurance, and tries to answer the question of which agile practices ensure software quality. Next, agile practices associated with quality assurance are assessed from different perspectives and some recommendations for their usage are given. It is observed that modeling has a particular impact on quality assurance.

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.

Under Pressure

2018 ◽  
Vol 49 (6) ◽  
pp. 78-102 ◽  
Author(s):  
Kim E. van Oorschot ◽  
Kishore Sengupta ◽  
Luk N. Van Wassenhove
Keyword(s):  
Software Development ◽  
System Dynamics ◽  
Poor Performance ◽  
Agile Software Development ◽  
Project Teams ◽  
Dynamics Simulation ◽  
Software Projects ◽  
Sequential Development ◽  
Agile Practices ◽  
Agile Software

The iterative cycles used in agile software development create a series of deadlines for project teams. We investigate the optimal iteration length under behavioral conditions for agile software projects. Based on system dynamics simulation, we argue that both very long (as in sequential development) and very short (monthly) iterative cycles create huge and disruptive fluctuations in schedule pressure experienced by the team. These lead to poor performance in terms of quality, as well as costs and time compared with optimal iterative cycles of two to three months. The monthly cycles used in many agile practices might be too short to ensure optimal performance.

SaaS Requirements Engineering for Agile Development

2013 ◽  
pp. 64-93 ◽  
Author(s):  
Asif Qumer Gill ◽  
Deborah Bunker
Keyword(s):  
Software Development ◽  
Requirements Engineering ◽  
Business Process ◽  
Development Process ◽  
Business Processes ◽  
Software As A Service ◽  
Agile Development ◽  
Agile Practices ◽  
Development Processes ◽  
Agile Software

The emergence of Software as a Service (SaaS) has made it possible to develop dynamic and complex business processes as eServices. The development of business processes as eServices (SaaS) can be assisted by the means of adaptive or agile development processes. The development of business processes in terms of SaaS require to perform SaaS requirements engineering (RE), which is an important phase of a software development process for the success of any project. The challenge here is how best to do SaaS RE (e.g. mapping business process to eServices) and select agile development practices for developing business processes in terms of SaaS. In order to address this challenge, an integrated agile RE model for SaaS project development environments is outlined within this chapter. The purpose of the proposed RE model is to aid in iteratively determining SaaS requirements in short iterations as opposed to the “only first and onetime upfront” phase of a development process. Each identified SaaS requirement or a set of requirements for a given iteration is linked to a single or set of specific agile practices for implementation in short iterations. This model can be used as a guideline by organisations wishing to understand the challenging task of mapping business processes to SaaS and its implementation by using agile software development processes or practices.

Cuspe: propuesta ágil para la construcción de software basada en TSP [Cuspe: Agile approach for software development based on TSP]

2014 ◽  
Author(s):  
Giovanni Hernández ◽  
Álvaro Martínez
Keyword(s):  
Software Development ◽  
Analytical Approach ◽  
Work Teams ◽  
Software Process ◽  
Software Production ◽  
Palabras Clave ◽  
Agile Approach ◽  
Team Software Process ◽  
Agile Software ◽  
Progress Measurement

Resumen El objetivo principal de este artículo es aportar a la forma de trabajo de las empresas de la industria de software en Nariño mediante una propuesta metodológica ágil basada en Team Software Process (TSP). Este trabajo se desarrolló bajo el paradigma cuantitativo, con un enfoque empírico-analítico de tipo descriptivo-propositivo. La población objeto de estudio fueron las metodologías para construir software basada en equipos de trabajo, de las que se seleccionó de manera intencional TSP. Como resultado, se estableció que el nivel de agilidad que posee TSP corresponde al 79.25%. Así mismo, se diseñó Cuspe, como una propuesta para intervenir los principios del manifiesto ágil que presentan el menor nivel de cumplimiento en TSP. El trabajo permite concluir que la propuesta Cuspe basada en TSP logra incrementar el nivel de agilidad de la metodología y busca la entrega temprana y frecuente de software con valor, a través del trabajo y compromiso de personas motivadas; y consigue medir el progreso. Palabras Clave: Construcción de software, Manifiesto por el Desarrollo Ágil de Software, Team Software Process   Abstract The main goal of this article is to support Nariño’s’ Software industry’s way of work through a methodological proposal based on Team Software Process (TSP). This work was carried out under a quantitative paradigm and a descriptive-propositional-based empirical-analytical approach. The object populations were the methodologies for building software based on work teams, in which TSP was intentionally chosen. As a result, it was set that TSP’s level of agility reached 71.25%. Furthermore , It was designed Cuspe as an proposal in order to intervene the principles of the Agile Manifesto which shows the lowest level of accomplishment regarding TSP. This work allows concluding that the Cuspe proposal based on TSP increases the level of methodology’s agility and leads to an early and frequent valuable software production through the work and compromise of motivated people, and also progress measurement. Keywords: Manifest for Agile Software Development, Software Development, Team Software Process.

Sign in / Sign up

Export Citation Format

Share Document