Agile And Waterfall Life Cycle Model Essay

The articles I found in the Drexel library discuss two development methods: Agile and Waterfall life cycle models. The first article is titled Changing the Paradigm of Software Engineering (“Changing Paradigm”) and focuses on the positive shift from the old Waterfall method to the new Agile method of systems development. The second is Exploring Agile and discusses the Agile method’s shortcomings.

Compare

The two articles discuss popular methods for systems development. Both embrace the concept that the current popular development method-of-choice is Agile-based and that the Waterfall method is outdated. According to Changing Paradigm, “departure [from the Waterfall life cycle to iterative and agile processes] is fundamental and, in fact, it represents a new paradigm … change from an old paradigm to a new one takes place when the old paradigm is in crisis” (Rajlich 1).

Waterfall became the dominant paradigm through which software development was viewed in the 1960s when it was created in order to help scale up large systems (Rajlich 2). It required the developer to collect requirements prior to beginning

One change is the emphasis on collaboration. Office spaces have been updated to create more collaboration across teams. From tearing down cube walls and promoting teaming environments, modern-day workers want and expect to be involved, and that includes giving their input on systems development. Another change is that technology has expanded and become more available. As a result, system development no longer takes place in off-site locations until completion. Instead, development takes place on-site, with collaboration from customer stakeholders throughout the process, until the project is complete. Customers are more involved than ever; they want and expect to provide input and be looped in throughout the development