Waterfall VS Agile Software Development Methodologies - PowerPoint PPT Presentation

About This Presentation
Title:

Waterfall VS Agile Software Development Methodologies

Description:

What's the difference between Agile vs Waterfall? Here's everything you need to know about these project management methodologies. Know the Biggest difference between Agile vs Waterfall. – PowerPoint PPT presentation

Number of Views:2216
Slides: 14
Provided by: imranansari7
Category:

less

Transcript and Presenter's Notes

Title: Waterfall VS Agile Software Development Methodologies


1
Differences Between Waterfall Vs Agile
Methodologies
  • By Imran Ansari

2
  • Todays software development utilizes many
    methodologies to facilitate building applications
    and software solutions. we've Waterfall, Agile,
    Design Thinking, or Lean Startup also as their
    combinations and variations. What are the
    principles of those methodologies? How do they
    support software development? Lets explore the
    differences between the Waterfall methodology and
    a combined approach that has Design Thinking,
    Lean Startup, and Agile.

3
  • Waterfall
  • The Waterfall approach to software development
    describes a sequential process for building
    softwarei.e., one step has got to be completed
    before subsequent can begin.
  • In the Waterfall methodology, the project scope,
    outcome, and requirements are documented fully
    before any development begins.

4
  • Waterfall Project structure Phases
  • Design Agree on a programming language, specific
    design elements, system design. Documents
    produced during this phase are going to be the
    framework for the implementation (coding) phase.
  • Implementation Turn client requirements and
    style documents into the software.
  • Testing Test the software for bugs and check if
    the goals from the wants document are met.
  • Deployment Release the software to the client.
  • Maintenance Fix any problems found once the
    software has been released to the purchasers.

5
(No Transcript)
6
  • Benefits
  • Better manageability. Because each step is
    documented and deliverables outlined upfront,
    its easier to manage the project.
  • Fixed price and deadline. The value and delivery
    date are often determined with a high degree of
    accuracy.
  • Clear instructions. Developers and designers
    involved in the project know exactly what to try
    and when to try to do it. With detailed
    documentation available, the project is often
    completed by different teams.

7
  • Drawbacks
  • Once the event begins, its difficult to adapt
    the project to any changes in requirements or new
    market insights. Whenever significant changes are
    needed, the project has got to undergo the need
    and style phases.
  • Requirements dont always reflect real user
    needs.
  • Projects counting on technologies that have
    frequent release-cycles got to be updated often
    to reflect the changes. As a result, the
    estimations in the documentation are going to be
    less accurate.

8
  • Agile Software Development
  • Agile development describes the process of
    developing software. The Agile methodology was
    created to form software development more
    efficient and versatile compared to the normal
    Waterfall methodology.
  • In the Agile approach, the software is built-in
    parts (fully working pieces with a database, user
    interface, business logic). Testing and
    development happen concurrently as against the
    linear approach in Waterfall. The core assumption
    is to release new products faster and introduce
    modifications counting on user feedback.

9
(No Transcript)
10
  • Assumptions of Agile development
  • Communication Agile teams discuss daily to align
    on goals and reflect on past tasks to hunt
    improvement.
  • Adaptive approach Unexpected changes within the
    project are introduced swiftly, helping gear the
    merchandise toward end-users.
  • Collaboration Frequent collaboration with
    customers to seek out areas for improvement
    within the product.
  • Priority Deliver a working version of the
    software early and
  • Cross-platform developers Teams have all the
    required skills to create software products that
    deliver customer value.

11
  • Benefits
  • Faster time-to-market.
  • Quick implementation of the latest project
    requirements.
  • High-quality software. Bugs and errors are caught
    early because applications are built iteratively
    and each iteration is tested.
  • Increased productivity through stress on
    collaboration and communication.
  • Smaller documentation. The main target is on
    building working software.

12
  • Drawbacks
  • Projects can become chaotic if teams and project
    managers arent skilled in Agile development.
  • It is often difficult to estimate delivery dates
    because the project can change during
    development.
  • In the combined approach, the Agile methodology
    is employed to make a minimum viable product
    (MVP)a fully working version of an application
    with minimum features built to gather insight and
    refine future iterations.

13
Thank You
Write a Comment
User Comments (0)
About PowerShow.com