Architecture-Centric Methods and Agile Approaches

Software Development Methodologies Evolutionary Trends from Waterfall to DevOps

Agile and DevOps are currently the most popular software development techniques. Software methodologies started with the application of the Waterfall model and other models of Software development. It provides a general overview of the approaches and their integration throughout the Software Development Life Cycle (SDLC). SDLC phases are described and different SDLC methodologies are discussed with respect to their impact on motivation, productivity and quality. A comparison of the traditional Waterfall and newer iterative/incremental/agile is identified, as are the reasons behind this change, such as customer participation, timely feedback, and quality improvement. The following issues are common to all methodologies: architecture limitations, scalability and organizational restrictions. It was identified that the industry tends to follow a hybrid Agile-DevOps practice with more emphasis on automation, continuous integration and collaboration to achieve quick and competitive software 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

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.

Beyond Traditional Metrics: Toward a Multifactorial Model for Measuring Productivity in Agile Software Teams

Measuring productivity in software development teams is a key process for evaluating their performance in agile environments, which are characterized by value creation, continuous adaptation, and incremental improvement. However, in the field of software engineering, although there are approaches focused on individual metrics, there remains a gap in the development of multifactorial models that integrate the various dimensions influencing team productivity. In response to this issue, this study proposes a multifactorial conceptual model designed to support the process of measuring productivity in agile teams. The development of the model was based on the measurement protocol proposed by Fenton and Bieman and included two main stages: design and validation. During the design phase, productivity factors were identified, and entities, properties, and empirical relationships were defined; these were represented using a Unified Modeling Language (UML) class diagram. The model was validated through expert judgment and an exploratory empirical application in higher education settings. The results demonstrate a high level of acceptance by experts, as well as the model’s viability for application in real-world scenarios, enabling the operationalization of the productivity construct in Scrum teams. In conclusion, the proposed model constitutes a significant advance in measuring productivity in agile teams by integrating multiple dimensions of performance, offering a structured, validated, and applicable framework that overcomes the limitations of traditional approaches and contributes to both the academic realm and professional practice.

Development Activities: Perspectives of Agile Practitioners