Pros & Cons of Agile And Waterfall Methodology - PowerPoint PPT Presentation

About This Presentation
Title:

Pros & Cons of Agile And Waterfall Methodology

Description:

Agile and Waterfall are the two most widely used methods to develop software and have confusion which one is better. Hence, We have listed a clear overview of these methodologies along with their pros and cons that will help you choose between the two. – PowerPoint PPT presentation

Number of Views:1756
Slides: 14
Provided by: oliviacote
Tags:

less

Transcript and Presenter's Notes

Title: Pros & Cons of Agile And Waterfall Methodology


1
Agile And Waterfall Methodology
  • Strengths Weaknesses of

2
Who We Are
  • Canada based, Leankor provides the best
    solutions for project management. With Leankor
    Visual Project Management App, fetch the huge
    returns on investment
  • Visually working in Agile or Waterfall mode,
    you will now be able to manage resources,
    portfolios, time tables, finances and risks at
    one place. Skilled at resource management,
    Leankor will help you manage your project
    conveyance with effective time visibility.

3
Introduction
  • Agile and Waterfall are the two most
    prominent methods to develop software and a
    debate rages about which one is better. Well,
    heres a breaker. We have listed a clear
    description of these methodologies along with
    their strengths and weaknesses that will help you
    choose between the two.

4
Understanding Agile
  • Agile is often seen as a solution to the
    drawbacks of the waterfall methodology. Rather
    than a sequential design process, the Agile
    methodology works on an incremental approach.
  • Developers begin with a basic project design,
    and then work on small units. The work on these
    units is done on a weekly or monthly basis, and
    at the end of each week or month, project
    priorities are assessed and tests are done. These
    units allow for errors to be found, and customer
    feedback to be combined into the design before
    the next unit is run. 

5
(No Transcript)
6
Strengths of Agile Methodology
  • The Agile methodology allows you to make changes
    even after the initial planning. Re-writes to the
    program can be made whenever the client decides
    to make changes.
  • It also allows you to add features that keep you
    updated with the advances in your industry.
  • It also allows clients to give their feedback and
    makes sure that they get the product they
    desire. 

7
Weaknesses of Agile Methodology
  • If you use a less successful project manager, the
    project is likely to come in late and over
    budget.
  • As the initial project lacks a stable plan, the
    final product can turn out to be different than
    what was intended.

8
Understanding Waterfall
  • Waterfall methodology is a sequential design
    process. This means that everything is done step
    by step. The eight steps- outset, initiation,
    breakdown, design, construction, testing,
    implementation, and maintenance have to be
    completed one after another. Once a step has been
    completed, developers cant go back to a previous
    step without discarding the entire project and
    starting from the scratch.

9
(No Transcript)
10
Strengths of Waterfall Methodology
  • The waterfall methodology allows for the ability
    to progress upon the existing program in the
    future as it stresses careful record keeping.
  • The clients will have knowledge of the size,
    cost, and timeline for the project. They will
    have a clear idea of what their program will do
    in the end and theres no room for uncertainty.
  • Its strong documentation allows for minimal
    project impacting the case of employee turnover.

11
Weaknesses of Waterfall Methodology
  • Developers cant move back to a previous stage
    and make changes once a step has been completed.
  • If initial requirements are faulty in any manner,
    the entire project is ruined as this methodology
    relies heavily on requirements.
  • If a change is needed or a requirement error is
    found, the project has to be started from scratch
    with all new code.

12
Conclusion
  • Both Agile and waterfall methodology have
    their respective strengths and weaknesses. The
    decision of choosing between the two relies on
    the context of the project. Will your project
    need frequent changes? If yes, go for Agile. And
    if you know exactly what you need, maybe
    waterfall is the better choice. If youre
    uncertain and confused, merging the aspects of
    both agile waterfall methodology is an effective
    way to develop the best possible software process
    for your project.

13
Useful Resources
  • Use Kanban Board In Three Steps
  • How To Make Any Project A Success With Project
    Management Tools
  • Portfolio Management - Road To FulFill Client's
    Goal
Write a Comment
User Comments (0)
About PowerShow.com