Agile Processes in Software Engineering and Extreme Programming, 9th International Conference, XP 2008, Limerick, Ireland, June 10-14, 2008. Proceedings

Programming Methodologies: Agile, Scrum, and Devops in Practice

Modern software development requires flexible, efficient, and collaborative methodologies to cope with rapidly changing requirements and complex systems. This article explores three widely adopted programming and software development methodologies: Agile, Scrum, and DevOps. Agile focuses on iterative development, customer collaboration, and continuous improvement. Scrum, as an Agile framework, provides structured roles, events, and artifacts to enhance team productivity and project transparency. DevOps extends Agile principles by integrating development and operations, enabling continuous integration, continuous delivery, and faster deployment cycles. Through practical analysis and real-world examples, this study highlights how these methodologies complement each other in practice, improve software quality, reduce time-to-market, and enhance collaboration among stakeholders. The article concludes by discussing best practices and challenges in adopting Agile, Scrum, and DevOps in modern software engineering environments.

A Comprehensive Systematic Literature Review of Agile Methodology

Agile methodology, which offers collaborative, adaptable, and iterative alternatives to conventional plan-driven procedures, has become a revolutionary paradigm in project management since it was codified in the Agile Manifesto. Agile was first used in software development, but it has now spread across many different industries, demonstrating its increasing applicability in dealing with complexity, ambiguity, and quick environmental change. Given this expansion, a comprehensive synthesis of the existing body of knowledge is necessary to understand the trajectory of Agile’s development, its practical applications, and its theoretical foundations. The literature demonstrates enduring issues, such as organizational resistance, misalignment with current governance structures, and the shortcomings of traditional performance measuring tools, despite widespread implementation. As a result, hybrid models that combine Agile and conventional methods have drawn more academic and real-world interest. This paper aims to present a literature review of Agile methodologies from 2001 to 2025, systematically examining their evolution, cross-sectoral diffusion, and key adaptations. It further identifies critical gaps in the literature and outlines future research directions, particularly in relation to sustainability, emerging market contexts, and the advancement of hybrid frameworks. Through this analysis, the study aims to provide a coherent and integrated understanding of Agile’s role in managing complexity and enhancing value delivery in contemporary organizational environments.

Order and chaos in agile software development: a comparison of two software development teams in a major IT company

Agile Software Development Challenges: Identification, Validation, and Prioritization Using the Analytic Hierarchy Process

Context: The Agile methodology has been prevalent in the software industry for more than two decades, marking a shift from plan-driven to market-driven approaches and introducing various challenges. While the literature identifies numerous challenges in Agile development, little attention has been given to their ranking and prioritization, which are critical for effective project management and decision making. This study fills this gap by combining empirical evidence from the literature and practitioners. Objectives: This study aims to identify and hierarchically prioritize the most recent challenges faced by Agile practitioners during product development. To achieve this, a Systematic Literature Review (SLR) was conducted using 115 published studies between 2010 and 2025 followed by empirical data collection from 30 Agile experts through semi-structured interviews conducted with practitioners from Agile companies and an online survey. This study applies Cumulative Voting (100-Dollar Test) and Multi-Criteria Decision Making (MCDM) techniques to rank and prioritize these challenges. Results: The SLR identifies several recurring Agile challenges; however, limited research has focused on their ranking and prioritization. The present study reveals new challenges, such as user interface complexities, lack of pre-development and pre-operational cost information, and lack of cost scalability at the module and feature levels. The current study identifies Inadequate Architecture (22%), Lack of Standardized Framework (18%), Communication and Coordination (16%), Poor Requirement Verification (13%), and Minimum Documentation (8%) as the most significant challenges. Conclusions: This study provides valuable insight for Agile practitioners and organizations, enabling more informed project planning, resource allocation, and strategic decision making. By focusing on the most critical challenges, teams can enhance software quality, streamline processes, and improve overall productivity in Agile environments.

AGILE SOFTWARE DEVELOPMENT RISK ASSESSMENT: A MONTE CARLO-BASED SIMULATION METHOD USING JIRA SCRUM AND KANBAN DATASETS

Agile Software Development (ASD) has turned out to be the foundation of the present-day software development practices with the provision of iterative processes, such as Scrum or Kanban, that emulate focus on flexibility, cooperation, and continuous deployment. Nonetheless, it is always a cumulative issue to deliver on schedule when uncertainty strikes because the teams have changing loads, backlogs, and lack visibility on potential risks. Common planning methods, like average-based velocity or fixed sprint length, are unable to reflect real variation of the world and thus are subject to poor forecasts and lack of confidence by the stakeholders. To overcome this, the paper has suggested simulation-based risk analysis model which will rely on Monte Carlo Simulation (MCS) and will use the real empirical data of three practical software projects including GFG (Scrum), and User grid and Aurora (using Kanban). The time a particular historical issue was resolved and data on sprint performance were processed in order to calculate a velocity distribution which was in turn applied to predict the backlog completion timeline over 10,000 MCS iterations. Further improvement of simulations with SimPy further decreased the variability of the forecast and produced single estimate of project completion with a median (P50) of 3.45 sprints with a narrow 95% confidence interval of 3.45 to 4.60 sprints as opposed to the broader estimate of 16.67 sprints of the baseline MCS. Histograms, burn-up charts, and cumulative distribution graphs along with other visual solutions, ensured smooth intuitive performance of risk communication and comparisons between Scrum and Kanban. The framework also enables probabilistic planning (versus a static one) in as far as uncertainty is measured in the form of percentile-based estimates (as P10, P50, P90). The use of accessible technologies like Python and Jira REST APIs ensures the framework remains cost-effective and practical for Agile teams. This research advances Agile risk assessment by integrating statistical modeling with real project data, improving forecasting accuracy, stakeholder alignment, and delivery confidence—ultimately providing a scalable solution for managing delivery uncertainty in dynamic Agile environments. 

MEASURING THE IMPACT OF GENERATIVE AI ON SOFTWARE TEAM PRODUCTIVITY AND OUTPUT QUALITY IN AGILE ENVIRONMENTS

Generative artificial intelligence (GAI) is becoming more incorporated into software engineering functions like code creation, debugging, requirement analysis, testing, and sharing knowledge. This research looks at how GAI affects software teams in terms of productivity and quality of the output in Agile environments. The research design used is quantitative, cross-sectional survey type using a questionnaire prepared for this research. The data used consists of 35 responses, with 34 usable cases in analyzing 30 Likert items. The measuring instrument consists of six concepts: use of GAI, efficiency of the software team, quality of the software output, GAI in Agile, team collaboration, and communication, and overall impact perceived. The descriptive results show positive feelings about the six concepts. The values on the mean for the different concepts varied from 3.54 to 3.78 on a scale of five, with GAI being the concept that received the highest mean (M = 3.78, SD = 0.47) while productivity was the one that received the lowest (M = 3.54, SD = 0.69). The instrument has a high level of internal consistency with α = 0.799 for the entire scale of 30 items. In terms of specific items, productivity, quality, and team collaboration had acceptable reliability, whereas GAI had low internal consistency and Agile and general have the upper limit of reliability therefore, construct-level findings should be interpreted cautiously. Pearson correlation analysis showed statistically significant positive associations between overall perceived impact and software output quality (r = 0.365, p = 0.034) and team collaboration and communication (r = 0.371, p = 0.031). Productivity was positively associated with overall impact but did not reach the conventional 0.05 significance level (r = 0.312, p = 0.073). In a multiple regression model, the five dimensions explained 23.5% of the variance in overall perceived impact (R² = 0.235); however, the overall model was not statistically significant (F(5, 28) = 1.719, p = 0.163). These findings support a cautious interpretation: respondents generally perceive GAI positively, but the present small sample does not provide strong evidence for broad causal claims.