Name: Vaibhav Gedigeri
Ricardo A. Collado
AGILE vs. WATERFALL
Agile and Waterfall are two sdistinct methods of software development. The Waterfall model can really be described as a linear model of software design. Like its name suggests, waterfall employs a sequential design process. Development essentially flows, sequentially from start point to end point, along several different stages: Conception, Initiation, Analysis, Design, Construction, Testing, Implementation, and Maintenance.
In contrast, the agile method proposes an incremental and iterative approach to software design. It was essentially developed in response to the limitations of Waterfall methodology, as a way ...view middle of the document...
4) Waterfall model works well for smaller projects where requirements are very well understood.
Pros of Agile model
1) Agile can be especially beneficial in situations where the end-goals of projects are not clearly defined. For example, if one is working with a client whose needs and goals are a bit hazy, it is probably worthwhile to employ the agile method. The client’s requirements will likely gradually clarify as the project progresses, and development can easily be adapted to meet these new, evolving requirements. Agile is also an excellent option for experimental software design.
2) Agile offers an incredibly flexible design model, promoting adaptive planning and evolutionary development. Customer feedback occurs simultaneously with development, as does software testing. This has a number of advantages, especially in project environments where development needs to be able to respond to changes in requirements rapidly and effectively.
3) The testing at the end of each sprint ensures that the bugs are caught and taken care of in the development cycle. They won’t be found at the end.
4) Because the products are tested so thoroughly with Agile, the product could be launched at the end of any cycle. As a result, it’s more likely to reach its launch date.
Cons of Waterfall model
1) The Waterfall method is incredibly rigid and inflexible. Altering the project design at any stage in the project can be a total nightmare and once a stage has been completed, it is nearly impossible to make changes to it.
2) The whole product is only tested at the end. If bugs are written in initial stages, but discovered late, their existence may have affected how other code was written.
3) If a requirement error is found, alterations needs to be made, the project has to start from the beginning with a new code.
4) Waterfall methodology relies substantially on initial requirements. However, if these requirements are faulty by any means, the project fails.
5) The plan doesn’t take into account a client’s ever evolving needs. If the client realizes that they need more than they initially thought, and demand change, the project will come in late and impact factors one being budget.
Cons of Agile Model
1) Though highly flexible, Agile simply doesn’t have the structure that the Waterfall method has and this does present some drawbacks. Agile projects tend to be hard to predict, from timelines to budgets. Without a concrete plan, everything remains a bit vague and unclear.
2) With a less successful project manager, the project can become a series of code sprints. If this happens, the project is likely to come in late and over budget.
3) As the initial project doesn’t have a definitive plan, the final product can be grossly different than what was initially intended.
Types of project suited for Waterfall Model.
1) When there is a clear picture of what the final product should be.
If we have a definite...