Agile Methodology's Impact on Software Development

Desklib offers solved assignments and past papers to help students succeed.

Impact of Agile Methodology on Software Development Process

Contents
Impact of Agile Methodology on Software Development Process............................................1
Introduction............................................................................................................................3
Background............................................................................................................................4
Popular agile methodologies..................................................................................................4
Extreme programming...........................................................................................................4
Planning:................................................................................................................................4
Managing:..............................................................................................................................4
Coding:...................................................................................................................................4
Designing:..............................................................................................................................5
Testing:...................................................................................................................................5
Scrum.....................................................................................................................................5
Feature Driven Development.................................................................................................5
Crystal method.......................................................................................................................6
Control changes in requirement.............................................................................................7
Error detection........................................................................................................................7
Improve performance.............................................................................................................7
Clear and secure delivery.......................................................................................................8
Quality improvement.............................................................................................................8
Fewer probability...................................................................................................................8
More phase and guarantee......................................................................................................8
Larger request on developers and customer...........................................................................9
Lack of necessary documentation..........................................................................................9
Project easily falls off track....................................................................................................9
Conclusion............................................................................................................................10
Reference..............................................................................................................................11

Introduction
Agile methodology is a process or a method of developing a software. Agile methodology is
a group process of developing software. The agile methodology is basically working on
incremental development and interactive development. This methodology is basically
working on four characteristics: rapid & flexible, adaptive planning, iteractive & evolutionary
development. With The help of these characteristics are it promote and change
communication. The development of a software is very easy with the help of agile
methodology just because it is also known as lightweight process. In agile methodology
development of a small software is more suitable than other methodology. The stage of
production is never increment before all the requirements like coding, testing, design will
refine. With the help of this process the software requirement is accurate and also useful at
the time of final software.
Table 1 anticipated benefits
Anticipated Benefits % Respondents Anticipating Benefit
Improved Visibility 88.7%
manage priorities 97.6%
Improved productivity 97.7%
Accelerated time 96.3%
improve software quality 94.5%
control risk 93.5%
control cost 85.3%
Best management of distributed developers 54.2%
Simplified development process 89.6%
Increase the alignment of IT and Business Objectives 88.6%
Increase Discipline of engineering 84.9%
Software Maintainability 87.4%
Increase Team Morale 85.1%

Background
The development by agile methodology is known as subcategory of interactive methodology.
This methodologies working on shorter time period just for delivery. This methodology has
feature of rapidly answer to change. They force to focus on good coder, good coding, good
techniques. They also focus on the set of broad which helps to manage team norms,
production of work, boundary management of team, and in the end interaction. In 1996
Schwaber told the motive of choosing agile methodology is that developing a software is
uncertain process and in the development of software changes can’t be avoided.
Table 2 significant proponent and agile methodology
Methodology Proponent Agile Manifesto Author(s)
Feature Driven Development Jon Kern
Extreme Programming Kent Beck, Martin Fowler, Ward Cunningham, Robert Martin
Adaptive Software Development James Highsmith
Scrum Mike Beedle, Ken Schwaber, Jeff Sutherland
DSDM Arie van Bennekum
Crystal Alistair Cockburn
Popular agile methodologies
According to a business view, this methodology has the feature of make changes at the time
of development according to environment. In this methodology customer send feedback and
after that they work on that feedback.
Extreme programming
The extreme programming is basically working to improve the quality of software. It is
also responsive for changing in the requirement which are send by the customer. This
improves development of software in 5 ways:
1. Planning
2. Managing
3. Coding
4. Designing
5. Testing
Planning:
In planning development of software in divided into iteration like start planning, write
user stories, planning of releasing.
Managing:
In managing team is manage the work of develop like meeting on daily basis regarding
the problem or any changes in development.
Coding:
In coding the team is working on the coding of software and in one day only on part of
coding is done.

Designing:
In this process team choose a metaphor, before this no functionality is added.
Testing:
In the testing the code of software or the work of software is checking before releasing
software. They check that either the software working properly or there are any problem,
if there is any problem is occurred at the time of testing then testing team send feedback
to the developer team.
Scrum:
It is process of agile methodology which is used to develop a software. It a framework
which is generally use for project management and software. This process is applicable
for any project those have aggressive deadline and also have some complex requirements.
Figure 1 scrum process
(Source: Scrum.org 2019)
In scrum, sprint is a process in which process of a project in done via iteration series. In this
process sprints are basically 2-4 weeks longer. In a process of a scrum there is only 5-9
members are available in a team. The main stakeholder of the project is product owner. He
represent customer, users, and other.
Feature Driven Development
Feature Driven Development is process in which architecture-centric, client-centric and
pragmatic process are available. There are basically five type of activities are in FDD.
First it develop an overall model which have an initial result those are high-level model
and notes object. Before starting a project the main motive is to identified and understand
the basic things of domain which is addressing the system. Secondly, a list develop of all
data and then separate them with related data. In the third step they identify class owner,

and also identified the set owner. In the fourth step the detail of modelling include. In the
fifth step all the testing are check.
Figure 2 FDD life cycle
(Source: Ambler 2005-2018)
Crystal method
Alistair Cockburn is the developer of the crystal methods. In this method he told about
focusing on the software development more than tools and processes. It is methodology I
which is also known as toolkit for individual projects. Crystal method is basically
working on small projects.

Figure 3 crystal method
(Source: New line technologies 2009-2019)
Advantages of agile in software development
Control changes in requirement
Increasing planning phase is very dramatic because in the process of development
customers are directly connected. Customer has the right to control processes.
Error detection
In agile methodology testing is performed on each iteration and by the help of this errors
are detected earlier, and then it is easy to fix them. Also, continue feedback are coming
just because o continue testing.
Improve performance
Easy design and easy stories help in the teamwork. It encourages the team member. The
sharing of ideas and knowledge is increase with the help of better communication. It also
helps in team morale, increase trust in employee. With the help of this team productivity
is increased and it gives a better performance.

Figure 4 benefits of agile methodologies
(Source: Andolasoft, Inc 2019)
Clear and secure delivery
Project is basically divided into some small parts. The reason of this it manage risks.
These small are deliver according to schedule which is between 1-4 weeks.
Quality improvement
In agile method development of test-driven and refactoring is used. Refactoring is related
to better quality and reuse of higher code. All the features of the software are flexible and
improved.
Disadvantage of agile methodology
Fewer probability
Sometime developers and deliverables are not able to count full range of required
exertions. This is particularly happen in the starting of the development life. This fright
efforts poor practice, blocking, poor decision.
More phase and guarantee
It is very important that customer, developers, tester, must interact continue each other.
This includes many face-to-face discussions. For rapid testing daily user have to be
available and mark off on individually stage so after that developers can spot it rotten.

Figure 5 disadvantages of agile method
Larger request on developers and customer
These principal needs near teamwork and wide participation. It is an attractive and
satisfying system, it request a big assurance for the total of the development to confirm
achievement. Customers must go done training to help in product improvement.
Lack of necessary documentation
Requirements for product are explained just in period for development, documentation is
less exhaustive. It mean when new members link with team, they don’t know the all
feature and also that how they perform.
Project easily falls off track
To start this it required very little planning, accepts the consumer’s essential are ever
fluctuating .if a feedback which is send by the customer is not clear then it means a
developer is focusing on wrong area of development.

Conclusion
Agile software development pressures in- developing requirement skilled by direct user
connection in the process of developing. The enhancements in software improvement process
contain more constant requirement , earlier error detection, fewer lead periods for testing ,
increased communication.

Reference
1. O’Connor, R., Elger, P. and Clarke, P.M., 2016, May. Exploring the Impact of Situational Context
—A Case Study of a Software Development Process for a Microservices Architecture. In 2016
IEEE/ACM International Conference on Software and System Processes (ICSSP) (pp. 6-10).
IEEE.
2. Akbar, M.A., Sang, J., Khan, A.A., Amin, F.E., Hussain, S., Sohail, M.K., Xiang, H. and Cai, B.,
2018. Statistical analysis of the effects of heavyweight and lightweight methodologies on the six-
pointed star model. IEEE Access, 6, pp.8066-8079.
3. Elamin, R. and Osman, R., 2017, July. Towards Requirements Reuse by Implementing
Traceability in Agile Development. In 2017 IEEE 41st Annual Computer Software and
Applications Conference (COMPSAC) (Vol. 2, pp. 431-436). IEEE.
4. Stol, K.J., Ralph, P. and Fitzgerald, B., 2016, May. Grounded theory in software engineering
research: a critical review and guidelines. In 2016 IEEE/ACM 38th International Conference on
Software Engineering (ICSE) (pp. 120-131). IEEE.