AGILE AND TRADITIONAL METHODOLOGIES IN THE SOFTWARE LIFE CYCLE

Abstract

This paper compares agile and traditional methodologies applied to the software life cycle, considering their characteristics, applications, limitations and contributions to the development of computer systems. The main objective was to analyze how these methodologies influence efficiency, flexibility and quality in the software production process, considering contemporary market demands. The research adopted a qualitative, bibliographical approach, based on authors such as Pressman (2001), Sommerville (2003), Beck (1999), Royce (1970) and data from the Standish Group (1995). The study found that traditional methodologies, represented by the classic or waterfall model, are still useful in contexts with well-defined requirements and the need for rigorous documentation. However, they present difficulties in projects subject to frequent changes, due to their rigidity and sequential structure. On the other hand, agile methodologies, such as Extreme Programming and Scrum, offer greater adaptability, promote direct communication between teams and clients, favor fast and continuous delivery and reduce failures throughout the project. The results indicate that the methodological choice must take into account the organizational context, the type of project and the degree of instability of the requirements. The conclusion is that, although there is no universally superior methodology, agile approaches have proven to be more effective in dynamic, collaborative environments geared towards the continuous delivery of value to the client.