The Waterfall Approach For Software Development Projects

1578 Words7 Pages
The waterfall approach to software development projects is a linear model, which focuses on individual stages of development including, requirement identification, analysis, design, coding, testing and operations. While this model has been around for decades, there are many drawbacks. This method heavily focuses on extensive documentation and front loaded requirements gathering; thus inviting the opportunity for significant and costly failures. As the landscape of information technology in the business world has evolved, we have seen a major shift from complex back end systems that didn’t include input from stakeholders and only programmers could understand, to computer programs that are customized to the front end users and other…show more content…
This method utilizes smaller cross functional groups of people that work together on complex issues in a creative self-organized team environment. These teams should be comprised of all the right people needed to complete assignments and can include business analysts, developers, testers and the end users. Collaboration, teamwork and change are embraced rather than focusing on processes, extensive documentation and sticking to a precise plan. Incremental phases under agile allow for changes and product releases are delivered after each iteration. The most common agile method is scrum, in which a relatively small group of dedicated resources are solely responsible for every aspect of the work and are self-sufficient. Additional popular agile methods include rapid application development, lean software development, Kanban, extreme programming and scrumban. In the agile manifesto, developed in 2001, some of the key principles are to deliver frequent improvements that add value, to welcome change that adds competitive advantage, to continually work together through motivated individuals and focus on simplicity and maximizing the amount of work not done. Article Analysis In the article, The Waterfall That Won’t Go Away,1 Chatterjee describes how the waterfall method is still heavily relied upon in businesses and how it will continue to remain an approach to software development projects. Specifically, Chatterjee, a software developer, was
Get Access