Project Methods: Agile vs. Waterfall
Demarcus R. Calhoun
November 2, 2013
When it comes to methods of project management, there is much debate about which method is best. The Waterfall vs. Agile issue has probably been one of the most debated topics in project management. In this paper I will attempt to discuss the pros and cons of both, and look to find out which one is truly the best method. Agile is more suited for smaller projects because you can mange projects in small burst or sprints. Also with agile you have a chance to gauge results much more quickly which gives a team the opportunity to make changes ...view middle of the document...
Each project sprint or iteration is typically scheduled to be completed within a few weeks. The main asset of agile project management is the ability to counter issues as they arise throughout the course of the project. Making a the right change to a project at the correct time can have a great impact on saving resources, and also help to have a successful project within budget and on time. The ability to make decisions quickly is paramount to agile management, and thusly is not really for those organizations that need to deliberate for long periods in order to make decisions.
The Waterfall method is a traditional and popular version of the systems development life cycle model especially for software engineering. Many consider this approach as the classic approach to system development, this method describes a development method that is sequential and linear. Distinct goals for each part of development is a mainstay of the waterfall method. In a true Waterfall development project, each of these represents a distinct stage of software development, and each stage generally finishes before the next one can begin. There is also typically a stage gate between each; for example, requirements must be reviewed and approved by the customer before design can begin.(Lotz 2013)
The traditional method of project management has been said to be uncompromising or unable to adapt to change. so success depends on a good initial brief. Because of that there is not much room for testing or making changes based on behavior or user experience. Agile is usually considered to be much more beneficial in software development and many creative industries, because it allows for continual adaption of the brief and response to client specifications. Agile too has its critics, lots of people believe that the agile model is not usually to scale, which is why many of the biggest software development projects are still being conducted in Waterfall. Also, while agile is supposed to control scope creep, there are reports that the iterative design process can lead to users demanding a multitude of changes at each iteration - making it difficult for developers to deliver. (Heath 2012). While it is a useful approach to projects which are likely to have multiple changes, it is seen as offering no advantages over large projects where detailed requirements are known and changes are unusual or prohibitively expensive.
The objective of this paper is to discover the and show the pros and cons of both Agile and Waterfall methods of project management. Many people are dead set on one methodology being better than the other when it comes to Agile vs. Waterfall, but I will attempt to show that both can be appropriate, depending on what type of project you are pursuing. This paper will also take a closer look on the best approaches to different types of projects.
The Waterfall Methodology
The waterfall approach to software development is...