Assignment Topic

______________________________________________________________________________

Program: ________________________________ Semester: ____________________

Course: __________________________________ Section: ______________________

Assignment No: ___________________________ Assigning Date: ________________

Due Date: ________________________________ Submission Date: _______________

Group Name: __________________________________________________________________

Group Leader Name: _________________________________ SAP-ID: _________________

Group Member Name: ________________________________ SAP-ID: _________________

Group Member Name: ________________________________ SAP-ID: _________________

Group Member Name: ________________________________ SAP-ID: _________________

Group Member Name: ________________________________ SAP-ID: _________________

Remarks:
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________
______________________________________________________________________________

____________________ Marks: / 10
Instructor’s Signature
Explain agile and waterfall project management approaches
Agile and waterfall are two well-known project management methodologies. Each of them area
unit widespread in package development however every is best fitted to differing kinds of comes.
the most distinction is that body of water could be a linear system of operating that needs the
team to finish every project part before moving on to consecutive one whereas Agile encourages
the team to figure at the same time on totally different phases of the project.

Agile Methodology Approach:

Frequent neutral interaction
Flexibility: High
Requires: Team initiative and short-run deadlines
Agile methodology was developed as a response to Waterfall’s a lot of rigid structure. As a
result, it’s a far a lot of fluid style of project management. A package development project will
take years to finish, and technology will amendment considerably throughout that point. Agile
was developed as a versatile methodology that welcomes incorporating changes of direction even
late within the method, in addition as accounting for stakeholders’ feedback throughout the
method.
In Agile, the team can work on phases of the project at the same time, usually with short-run
deadlines. in addition, the team, instead of a project manager, drives the project’s direction.
this will empower the team to be impelled and a lot of productive, however additionally needs a
a lot of autonomous team.

Agile development methodology and testing practices have worked wonders for several
organizations with positive aspects. The positive aspects of agile are not hidden. They are very
much visible in organizations. There are some of the important points related to the agile model
listed as follows -

o Agile focuses on customer feedback, collaboration, small and rapid releases.

o Its purpose is to manage complex projects.
o The Agile produces better application suites with the desired requirements. Moreover, it
can quickly adapt according to the changes made on time during the project life.
o It has a small team size. Therefore, fewer people work on it so that they can move faster.
 o The agile model is not a suitable model for small projects. The expenses of developing
the small projects using agile are more than compared to other models.
o In agile methodology, the interaction of customers is very high, as after each iteration an
incremental model is deployed to customers.

CONs
 Because team members area unit acting on multiple phases at a time, there's potential for
overlap or unneeded effort spent on later stages if an early part has to be changed
 Deliverables aren't a demand to get to the subsequent part. It may be more durable to
confirm the whole team is on a similar page—especially if it’s an oversized team with
totally different departments. It additionally means work will stray or miscommunicated
between team members, particularly once folks leave and join the team within the middle
of the comes.
 The project timeline is tougher to work out from the beginning, and it's additionally a lot
of prone to amendment

Pros
 Short-term deadlines encourage productivity and potency
  There is plenty of flexibility to vary project direction and experiment with new
directions
 The methodology is client-facing, which suggests that the team shares progress
and incorporates feedback into the method

Waterfall Methodology Approach:

Hands-off; goals and outcome established from the start
Flexibility: Low
Requires: finishing deliverables to get to consecutive part
Waterfall methodology could be a linear style of project management ideal for comes wherever
the tip result's clearly established from the start of the project. The expectations for the project
and therefore the deliverables of every stage area unit clear and area unit needed so as to get to
consecutive part.
o Waterfall model is not an ideal model to develop a large scale project size.
o The requirements in the waterfall model should be clear cut at the beginning time;
otherwise, it may lead to a less effective method.
o In the waterfall model, it is hard to move back in order to make changes in the previous
phase.
o The testing process in the waterfall model starts after the completion of development. So,
there is a high chance of bugs to be found later in the project development.
CONs
 Because every project part has to be completed before going to consecutive stage, the
method will take longer
 You might not understand a difficulty with a part till you have got already progressed to
consecutive one. this may mean going back through every part and checking wherever
the error or error occurred, which may be a timely method.
 The body of water methodology needs that you just define the project from begin to
complete before you start. this does not yield plenty of flexibility or amendment. in
addition, it will become problematic if the stakeholders disagree on the project’s vision
and don’t verify till it's dead or during a later part.
Pros
 Provides a concrete set up of the project from begin to complete
 The team establishes project needs ahead of time, which may save time
 Each part of the project needs a deliverable to get to consecutive part, creating the work
flow a lot of structured
Limitations of body of water Model:
 It is not a perfect model for an oversized size project If the need isn't clear at the start, it's
a less effective methodology.
 Very tough to maneuver back to makes changes within the previous phases.
 The testing method starts once development is over. Hence, it's high probabilities of bugs
to be found later in development wherever they're pricy to repair.
Limitations of Agile Model
 It is not helpful methodology for little development comes.
 It needs an knowledgeable to require necessary selections within the meeting.
 Cost of implementing an agile methodology is no a lot of compared to alternative
development methodologies.
 The project will simply explode track if the project manager isn't clear what outcome
he/she desires.

Agile model v/s Waterfall model

 The comparison between both models is tabulated as follows -

S.no. Purpose Agile model Waterfall model

1. Definition Agile model follows the incremental Waterfall model follows a sequential
approach, where each incremental design process.
part is developed through iteration
after every timebox.

2. Progress In the agile model, the measurement In the waterfall model, generally the
of progress is in terms of developed measurement of success is in terms of
and delivered functionalities. completed and reviewed artifacts.

3. Nature Agile model is flexible as there is a On the other hand, the waterfall
possibility of changing the model is rigid as it does not allow to
requirements even after starting the modify the requirements once the
development process. development process starts.

4. Customer In Agile model, there is a high Customer interaction in waterfall

interaction customer interaction. It is because, model is very less. It is because, in a
after every iteration, an incremental waterfall model, the product is
version is deployed to the customer. delivered to the customer after overall
development.

5. Team size It has a small team size. As smaller is In the waterfall model, the team may
the team, the fewer people work on it consist more members.
so that they can move faster.

6. Suitability Agile model is not a suitable model Waterfall model works well in smaller
for small projects. The expenses of size projects where requirements are
easily understandable. But waterfall
developing the small projects using
model is not suitable for developing the
agile is more than compared to other large projects.
models.

7. Test plan The test plan is reviewed after each Test plan is reviewed after complete
sprint. development.

8. Testing Testing team can take part in the It is difficult for the testing team to
requirements change phase without initiate any change in needs
problems.