Water VS SCRUM Iterative Model · Using

Water
Fall Model  VS  Extreme Programming (XP)

 

Water
Fall Model

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

·       
In water
fall model we gather the requirements from the Costumer.

·       
Water fall
model is simple and obedient to use.

·       
In water
fall model the requirements are read and then develop.

·       
Feedback
is needed from costumer for accept a phase.

·       
After
checking the Software published.

Extreme Programming (XP

·       
In XP we
collect requirements from the costumer as Sorties.

·       
In XP use
KIS (Keep It Simple).

·       
In XP the
project is divided into iterations.

·       
The Costumer
always available.

·       
All code test.
After pass all tests it is published.

 

 

 

Iterative Model 
VS  SCRUM

Iterative
Model

·       
Using this
model we can develop effective project.

·       
Using this
model we can build and develop project progressive.

·       
User Feedback
is compulsory how project will play task.

·       
Using this
model short time for document creating and more time for developing.

·       
We can
setup rough design and in emphasis we can better our project.

Scrum

·       
Using
scrum we can design high-level design because meeting are held daily. For
Problem Desiccation.

·       
Worker Group
decides what they can do to delivering about project.

·       
Team
Master befriend with the project owner.

·       
Time for
ready of documents is 1 hour and meeting is 4 hours.

·       
Daily
Meeting is 15 minutes what we do today? Any Problem in Project?

 

 Incremental model  VS 
Feature-Driven Development

 

Incremental Model

Uncomplicated to test in every condition and debug
during a smaller step. In this model customer can see and behave to each built.

·       
Starting with
small, work subsystem, later releases add new performance.

·       
This model
is soft and limited costly to change capacity and problems are easy to change.

·       
Do working
rapidly and fresh as the same time as the program life cycle.

Feature-Driven Development

·       
Five basic
activities, an all model, the building of a factor list, the planning by
factor, the designing by factor, and the building by factor.

·       
Feature
driven development was also built as domain object modeling, developing by
factor and code ownership.

·       
If it will
take two or more than two weeks, then it will have to be broken down into
smaller factors and working on it.

·       
Feature
driven development main plan is to pass physical, working software many times
in a timely way.

x

Hi!
I'm Dana!

Would you like to get a custom essay? How about receiving a customized one?

Check it out