Exploring Software Development Methodologies: From Waterfall to Agile

Software methodology development processes developed to streamline associated software development process, with the Waterfall methodology being the first such process in 1970. After the said such time, many new development methodologies such as Agile and Spiral methodologies developed to facilitate the shortcomings of Waterfall. As the Spiral methodology is an iterative development module, where methodology continuously cycles through phases. The Agile Method is an incremental development methodology focused on providing flexibility, through an incremental development. The software development methodologies each serving unique purposes for risk analysis based projects, large-scale, small scale, well-define, and customer-driven projects. Consequentially,

Consequentially, the Waterfall consists of seven procedural steps followed in linear order, but possess small gates where information, specifications, and designs are reviewed. The seven procedural steps performed by software companies, according to Lotz (2013): “1. Gather and document requirements, 2. Design, 3. Code and unit test, 4. Perform system testing, perform user acceptance testing (UAT), 6. Fix any issues, and 7. Deliver the finished product.” However, the Waterfall methodology clear and defined linear plan provides development teams distinct guidelines for each phase of development, but the methodology still possesses pros and cons for usage. The advantages of the methodology are discipline provided by the procedural phase structure, current phase of the development team easily identifiable by vendor and client, and provides efficient knowledge transfer between team members. (Melonfire, 2008) Furthermore, the associated disadvantages of the methodology are the phases are not flexible to change, developers cannot return to a previous phase, and originally develop designs are not feasible. Finally, the trait of not being flexible deems Waterfall appropriate for well-defined projects, and projects with a fixed-price, a fixed-timeline, and a none adjustable scope. (Base36,