Author Topic: Agile Vs Waterfall Method  (Read 2096 times)

12215203601

  • Global Moderator
  • Newbie
  • *****
  • Posts: 20
Re: Agile Vs Waterfall Method
« Reply #30 on: May 16, 2022, 06:52:17 pm »
Waterfall Model:
Waterfall Model is the software development process used to design and develop the simple software. It is basically used when the security and many other factors of the software are not much important. It is used by freshers in order to develop the software.

It consists of five phases:
1.    Requirements analysis
2.    Design
3.    Implementation
4.    Coding and Testing
5.    Maintenance

Agile Software Development:

Agile software development is the software development process used to design complicated software. It is basically used when the software is quite sensitive and complicated. It is used when security is much important. It is used by professionals in order to develop the software.

It consists of three phases:
1.   Project initiation
2.   Sprint planning
3.   Demos

12103112907

  • Global Moderator
  • Newbie
  • *****
  • Posts: 21
Re: Agile Vs Waterfall Method
« Reply #31 on: May 17, 2022, 08:32:53 pm »
Agile Model
1. Agile methodologies propose incremental and iterative approach to software design
2. Agile process is broken into individual models that designers work on
3. customer has early and frequent opportunities to look at the product and make decision and changes to the project
4. Testers and developers work together
5. At the end of every sprint, user acceptance is performed
6. It requires close communication with developers and together analyze requirements and planning
7. Documentation attends less priority than software development.
8. the project is executed in short (2-4) weeks iterations. Planning is very less.

Waterfall Model
1. Waterfall Model Development sequentially from start point to end point.
2. The design process is not broken into an individual models
3. The customer can only see the product at the end of the project
4. Testers work separately from developers
5. User acceptance is performed at the end of the project.
6. Developer does not involve in requirement and planning process.
7. Documentation is a top priority and can even use for training staff and upgrade the software with another team
8. The phase is much bigger than iteration. Every phase end with the detailed description of the next phase.



12212216902

  • Global Moderator
  • Newbie
  • *****
  • Posts: 20
Re: Agile Vs Waterfall Method
« Reply #32 on: August 03, 2022, 03:14:31 pm »
The main difference is that Waterfall is a linear system of working that requires the team to complete each project phase before moving on to the next one while Agile encourages the team to work simultaneously on different phases of the project.

12217235602

  • Global Moderator
  • Newbie
  • *****
  • Posts: 21
  • Shital Borate
Re: Agile Vs Waterfall Method
« Reply #33 on: August 06, 2022, 10:35:40 am »
Traditional Development Model                                              Agile Development Model
Clear Initial requirements                                                        Unclear, creative, innovative requirements
Users are not involved.                                                      Close and frequent collaboration of users
Formal Documentation required                                                    Unspoken knowledge required
Use existing process                                                                         Prepared to embrace an agile approach
Fluctuation expected, distributed team   Collocated,                                smaller team
System failure consequences are serious                                        Less critical system
Project plans are linear                                                                 Project plans are iterative
Software Development is process-oriented                                          Software Development is people-oriented
Project Lifecycle based on tasks or activities                                    Project Lifecycle based on Software product features.
Process Models are: waterfall, Spiral                                                Evolutionary Approach
Team role assignment is based on the skill level
 of individual team members.                                                       Self-Organized Teams
Project Management Style: Command and Control.   Project Management Style: Leadership and Collaboration
Shital B.Borate

12202253104

  • Global Moderator
  • Newbie
  • *****
  • Posts: 20
Re: Agile Vs Waterfall Method
« Reply #34 on: August 06, 2022, 01:54:31 pm »
S.no.   Purpose   Agile model   Waterfall model
1.   Definition   Agile model follows the incremental approach, where each incremental part is developed through iteration after every timebox.   Waterfall model follows a sequential design process.
2.   Progress   In the agile model, the measurement of progress is in terms of developed and delivered functionalities.   In the waterfall model, generally the measurement of success is in terms of completed and reviewed artifacts.
3.   Nature   Agile model is flexible as there is a possibility of changing the requirements even after starting the development process.   On the other hand, the waterfall model is rigid as it does not allow to modify the requirements once the development process starts.
4.   Customer interaction   In Agile model, there is a high customer interaction. It is because, after every iteration, an incremental version is deployed to the customer.   Customer interaction in waterfall model is very less. It is because, in a waterfall model, the product is delivered to the customer after overall development.
5.   Team size   It has a small team size. As smaller is the team, the fewer people work on it so that they can move faster.   In the waterfall model, the team may consist more members.
6.   Suitability   Agile model is not a suitable model for small projects. The expenses of developing the small projects using agile is more than compared to other models.   Waterfall model works well in smaller size projects where requirements are easily understandable. But waterfall model is not suitable for developing the large projects.
7.   Test plan   The test plan is reviewed after each sprint.   Test plan is reviewed after complete development.
8.   Testing   Testing team can take part in the requirements change phase without problems.   It is difficult for the testing team to initiate any change in needs.

12230256704

  • Global Moderator
  • Newbie
  • *****
  • Posts: 21
Re: Agile Vs Waterfall Method
« Reply #35 on: August 06, 2022, 04:13:55 pm »
Agile Model
The Agile methodology promotes the continuous interaction of the development and testing during the SDLC process of any project. Unlike the waterfall model, the development and testing activities in the agile model are simultaneous. Agile methodology allows much communication between the customers, developers, testers, and managers.

In the Agile method, the entire project is divided into small incremental builds. All of these builds are provided in iterations, and each iteration lasts from one to three weeks.

Waterfall model

It is one of the easiest and most traditional models to manage. Because of its traditional development nature, each phase has specific deliverables and a review process. The waterfall model works well in smaller size projects where requirements are easily understandable.


12228258603

  • Global Moderator
  • Newbie
  • *****
  • Posts: 20
Re: Agile Vs Waterfall Method
« Reply #36 on: August 10, 2022, 11:18:31 am »
Waterfall Model methodology which is also known as Liner Sequential Life Cycle Model. Waterfall Model followed in the sequential order, and so project development team only moves to next phase of development or testing if the previous step completed successfully.

Agile methodology is a practice that helps continuous iteration of development and testing in the software development process. In this model, development and testing activities are concurrent, unlike the Waterfall model. This process allows more communication between customers, developers, managers, and testers.

Harshal Dagaji Patil

  • Global Moderator
  • Newbie
  • *****
  • Posts: 26
Re: Agile Vs Waterfall Method
« Reply #37 on: August 10, 2022, 09:19:43 pm »
define the waterfall and scrum framework?

12221277305

  • Global Moderator
  • Newbie
  • *****
  • Posts: 20
Re: Agile Vs Waterfall Method
« Reply #38 on: August 11, 2022, 01:20:53 pm »
The main difference is that Waterfall is a linear system of working that requires the team to complete each project phase before moving on to the next one while Agile encourages the team to work simultaneously on different phases of the project.

Which is better Agile or Waterfall?
If the project timeline is fixed and cannot be moved, Waterfall will offer a more predictable outcome. If you need to get the project delivered in a short amount of time, Agile is the appropriate choice here where action and getting things built is more important than documentation and process.