Plan-Driven Methodologies

Model
Waterfall Incremental Development Incremental Delivery Spiral Model
Criteria
Graph

The waterfall model is mostly  The cost of accommodating o Customer value can be delivered with
used for large systems changing customer each increment so system
engineering projects where a requirements is reduced. functionality is available earlier.
system is developed at several  It is easier to get customer
Advantages

o Early increments act as a prototype to

sites. feedback on the development help elicit requirements for later
work that has been done. increments.
 More rapid delivery and o Lower risk of overall project failure.
deployment of useful
o The highest priority system services
software to the customer is
tend to receive the most testing
possible.
- The main drawback of the - The process is not visible. o Most systems require a set of basic o If the implementation of risk
waterfall model is the difficulty - System structure tends to facilities that are used by different analysis will greatly affect the
of accommodating change after degrade as new increments parts of the system. profits of the project, the spiral
the process is underway. In are added. o The essence of iterative processes is model should not be used.
Disadvantages

principle, a phase has to be that the specification is developed in o Software developers have to
complete before moving onto conjunction with the software. actively look for possible risks, and
the next phase.
analyze it accurately for the spiral
- Inflexible partitioning of the
model to work.
project into distinct stages
makes it difficult to respond to
changing customer
requirements.
AGILE Methodologies
 Model
Extreme Programming Feature Driven Dynamic System Lean Development Kanban Development
SCRUM
Criteria
Graph XP Development FDD Development Model DSDM

lower the cost of used for speedy development Ensure : Deliver software systems on Focuses on the creation helps make your
change in software of software which includes a  Scalability time and on the budget. of easily changeable work visible so you
requirements. series of iterations to create  Repeatability software. can show it to others
Goal

required software.  Encourage and keep everyone

creativity and on the same page.
innovation
creating software within Suited for development Is good for organizations
a very unstable projects that are rapidly that are transitioning
Usage

environment changing or highly emergent from a phase-based

requirements. approach to an iterative
approach
• Interaction between • prioritizing work to be done. • Features are to be “small” • Based on the Rapid is to build software with • "Kanban" is the
developers and • Completion of a largely fixed set in the sense they will take Application Development  One-third the human Japanese word for
customers is good. of backlog items in a series of no more than two weeks methodology. effort "visual signal."
short iterations or sprints.
• learning is good. to complete • This is an iterative and  One-third the
• A brief daily meeting (scrum), at
• Simple code is more • Features that appear to incremental approach that development hours • Elements
which progress , upcoming work is
likely to work. take longer are to be emphasizes continuous user  One-third the investment • Visual Signals
Characteristics

described and obstacles are

• If simple code is good, raised. broken up into a set of involvement. • Columns
re-write code when it • planning session to define the smaller features • Work In Progress WIP
becomes complex. backlog items for sprint • Note: Two weeks is the • Commitment points
• Code reviews are good. • retrospective as team members maximum, most features • Delivery point
• Testing code is good. reflect about the past sprint. take far less time (1 - 5
• Enables the creation of self- days) • Types
organizing teams • Physical
• Accepting that the problem • Digital
cannot be fully understood or
defined
 Model

Extreme Programming Feature Driven Dynamic System

SCRUM Lean Development Kanban Development
XP Development FDD Development Model DSDM
Criteria

• Emphasis on • Decision-making is entirely • Help to move larger • Users are highly involved • helps to speeds up the
customer in the hands of the teams size projects and obtain in the development of the process of entire
involvement • Enables project’s where the repeatable success system so, they are more software development
• Help to establish business requirements • The simple five likely to get a grip on the • reduces the cost of the
rational plans and documentation is not processes help to bring software development project
schedules considered very significant work done in a short project. • Delivering the product
• Consistent with most for the successful time and easiest • Basic functionality is early
Advantages

modern development development manner delivered quickly. • Empowerment of the

methods • It is a lightly controlled • Built on set standards • Provides an easy access development team
 Help developers to method which totally for software by developers to end- • helps in developing the
produce quality empathizes on frequent development industry, users. decision-making ability
software updating of the progress, so it helps easy • Projects are delivered on of the team members
therefore, project development and time and within a specific • create more motivation
development steps is visible industry recognized budget among team members
in this method
best practices
• Improve the productivity of
each of the team members
• This methodology is • It is suffered if the • Not an ideal • Is costly to implement, as • The role of a business
only as effective as the estimating project costs and methodology for it requires users and analyst is vital to ensure
people involved time will not be accurate smaller projects developers both to be the business
• Require meetings at • It is good for small, fast (individual software trained to employ it requirements
frequent intervals at
moving projects but not developer ) effectively. documentation is
enormous expense to
customers
suitable for large size • High dependency on • It may not be suitable for understood properly.
• Require too much projects the main developer small organizations or • Development team may
development changes • Needs experienced team means the person one-time projects. lost focus on its original
Disadvantages

which are really very members only. With novices should be fully • It is not very common and objectives because
difficult to adopt every team members, the project equipped for an act as easy to understand great flexibility
time for the software cannot be completed within coordinator, lead
developer exact time frame designer, and mentor
• It tends to impossible to • No written
be known exact documentation
estimates of work effort
provided to clients in
needed to provide a
quote
this methodology;
• At the starting of the
project nobody aware
about the entire scope
and requirements of the
project