Benefits and Drawbacks of Agile Software Development

Running head: PROJECT MANAGEMENT
PROJECT MANAGEMENT
Name of the Student
Name of the University
Author Note:

1PROJECT MANAGEMENT
Executive Summary
Agile can be defined as time-bound iterative approach in the software delivery that helps in
software increment right from beginning of the project. Agile comes up with ability to easily
create and respond to required changes. It can be stated the method of dealing and succeeding in
the uncertain and present environment. Agile software development is considered to be more
than a framework like Scrum, Extreme Programming (XP). Agile software development is
considered to be more than practices like pair programming, test driven, start-up and planning
session. Agile software development can be stated as the development umbrella that comes up
with set of frameworks. It is completely based on values and principles that has 12 principles
behind it. In the coming pages of the report, both benefits and drawbacks of Agile software
development have been discussed in details. Various success and failure stories of industry use
and its application have been provided.

2PROJECT MANAGEMENT
Table of Contents
Introduction......................................................................................................................................3
History.............................................................................................................................................3
Advantages......................................................................................................................................4
Disadvantages..................................................................................................................................6
Comparison of Project Management Methodology with other Project Methodologies..................7
Comparison between Agile and Waterfall...................................................................................7
Comparison between Agile and Prince2......................................................................................8
Success Adaptation of Agile at British Telecomm..........................................................................9
Failure of Webinar Agile Failure Pattern 2.0................................................................................10
Conclusion.....................................................................................................................................10
References......................................................................................................................................12

3PROJECT MANAGEMENT
Introduction
Agile can be defined as an iterative way in project management and development of
software. It merely helps the team in delivering team the required value to its customers in fast
that has few headaches. In the present era, technology is developing at a much faster rate than
ever (Abrahamsson et al., 2017). It is mainly enforcing various global software based firms so
that they can work in this fast-changing environment. It has now become possible so that they
can collect huge amount of software requirements. In the absence of the requirements, it mainly
becomes very much tough for any of the software model to work. Some of the conventional
software development is needed for rescue (Brhel et al., 2015). It is mainly needed for design for
the proper needs that are changing at a rapid rate. There has been huge amount of increments of
software that is needed for developing some of the best products. Agile mainly breaks down the
given larger project is smaller one, which is known as manageable chunks which are defined as
iterations. At the end of every iteration there is some product that is produced (Silva et al., 2015).
The products that are produced mainly tends to work at the end of every iteration that needs to be
valued. It is mainly needed for gaining proper feedback from various user and stakeholders.
In the coming pages of the report, an idea has provided concerning both benefits and
drawbacks of Agile model. A list of comparison has been made concerning other project
management methodologies. Both success and failure story along with industry use of Agile has
been discussed in brief.
History
It is very much important to understand the fact that Agile is not a methodology but can
be stated as a way that makes use of variety of methodologies (Hoda et al., 2017). Agile