Agile Methodology is Adaptive Not Predictive

This article discusses why Agile methodology is adaptive and not predictive. It explains the Software Development Life Cycle (SDLC) and the two distinct approaches, Adaptive and Predictive methodologies. It also compares Agile adaptive with predictive Waterfall Model and highlights the merits of the adaptive approach over the predictive approach. The article concludes by discussing the benefits of the adaptive approach, including early delivery, transparency, user focus, and high-quality software.

Running head: AGILE METHODOLOGY IS ADAPTIVE NOT PREDICTIVE
Agile Method is Adaptive Not Predictive
Name
Institution

AGILE METHODOLOGY IS ADAPTIVE NOT PREDICTIVE
Abstract
Software development Life cycle (SDLC) is considered as the procedure that must be
trailed by a given software industry in designing, developing and testing the quality of a given
software. The main aim for the SDLC approach is to help in designing of the software, its
development, Test which will result in the production of high-quality software that will be within
the budget and in the estimated timelines. Software development Life cycle has to define each
and every task in each phase of the software development, from the initialization stage all the
way to the deployment phase. The two well-known distinct Software development Life cycle
approaches are Adaptive and Predictive methodologies respectively. The adaptive methodology
is put in to place when the software that is at hand is involved in unknown or maybe outcomes
which are unspecified. This may involve dividing the entire project into various modules over a
timeline which is not determined so that it can allow flexibility when it comes to path direction
and project course (Jain, 2017). In this case, Agile is one of the best-known examples of an Agile
Software development approach.
On the other hand, the Software development Life cycle which is predictive is usually
developed in a software project and their results must be specified well and much more known.
Predictive Software development Life cycle must lay down a linear and much more a specific
software development plan which must be structured around all results which are predefined
and within a given timeline (Nawar, 2016). A good example of predictive Software development
Life cycle approach is the Waterfall model in which one cannot get the next phase before the
previous phase has been completed successfully. This paper seeks to discuss on why Agile is
adaptive and not predictive.
1.0 Why Agile Methodology is Adaptive and not Predictive
Agile methodology is one of the wide known approach applied in project management,
typically applied in the development of software. Agile methodology is referred to as a group of
approaches in software development which is based on iterative development (Matharu, 2015).
The requirement and solutions of Agile methodology evolve through the cooperation between
cross-functional teams which are self-organized without being concerned on the hierarchy. This
approach is clearly known for promoting teamwork, enhancing collaboration and supporting

AGILE METHODOLOGY IS ADAPTIVE NOT PREDICTIVE
adaptability processes throughout the software development life cycle. This approach has also
enhanced an increment in face to face communication and thus able to reduce the content in
the documentation.
Agile approach breaks the task into smaller increments divisions with no long-term plan.
Each and every aspect of development will have to be continually revisited throughout the
software development life cycle through iterations which are known as sprints. Iterations may
be termed as short time frames which may be developed in within one to four weeks
maximum. The concept of inspecting and adapt approach will indeed reduce both the cost of
development and the time needed for marketing. The following is the SDLC for each sprint.
• Plan
• Analysis of the requirements
• Designing
• Construction (Coding)
• Testing (Which is Unit followed by Acceptance testing)
The above steps in this approach will help in minimizing the overall risk and thus making
the handlers to have quicker software adaptability. The aim of iteration is being ready to be
released in the market with very minimal bugs at each of a given sprint.
The team size of an agile SDLC approach is about 5 to 9 people enabling them to easily
communicate and collaborate. This approach usually needs multiple teams to ensure that
larger developments are put in place in ensuring that there is priorities coordination across all
the team. Agile methodology emphasized a lot in one-on-one communication than it is in case
for documentations especially when the multiple team are working in the same place. Though,
in a situation when a team is working in locations which are different, they can maintain
contacts through use emails and video conferencing.
Software development is initially on the basis of coding and fixing of bugs. That works
well when dealing with smaller software, though the size and complexities of software may
grow and thus needing a proper process when one want to debug and test making such
software to become very difficult. This led to Engineering methodologies being born.

AGILE METHODOLOGY IS ADAPTIVE NOT PREDICTIVE
In 1995, there evolved some of the most popular agile approaches such as SCRUM,
Extreme Programming (XP), ASD (Adaptive Software Development), Feature Driven
Development and Dynamic Systems Development Method (DSDM). In the year 2001, there was
a group of seventeen forerunners in the Agile Software development who devised the term
“Agile Software development” and all the “Agile approaches”. There was a declaration of an
Agile Manifesto whose idea was stared as a set of recognized rules for Agile Software
development approaches and all the associated principles. In the same way, some of the
members led to the formation of the “Agile Alliance” which was a non-profit organization
meant for promotion of agile development.
Extreme Programming. This type of agile adaptive SDLC which is very popular in that it
stresses much on satisfying customers (Erturk, 2015). The major aim is improving the software
project by putting all focus on how they communicate with client, response, how simple,
courage, and much more respect. In most cases when developing teams are empowered, this
has ensured that the speed will respond to the customer requirements changing. Collaboration
and teamwork are some of the integral parts of XP which are used for improving the efficiency
and productivity in the approach to solve the problem.
2.0 Comparison of Agile adaptive with predictive Waterfall Model
In understanding that Agile is adaptive and not predictive, there will need to compare
and contrast agile methodology with waterfall methodology under the following sections.
2.2 Sequential Versus adaptive
One of the most widely known classic examples of a predictive Software development
lifecycle is the waterfall methodology. Waterfall methodology is a set of sequence of phases
that flows as steps which are definable. This in most cases is usually presented in the following.

AGILE METHODOLOGY IS ADAPTIVE NOT PREDICTIVE
Figure 1 Waterfall Model Diagram
The cycle of Waterfall model initiates at capturing of all the requirements, designing
them, construction, integration, test and debug all errors, Installation, and maintenance as
described in the figure above. In the waterfall model, each and every stage must be completed
before one begins in the next phase. All the methodologies which are derived from waterfall
model in most cases have a very clear set of gates which are used in defining when each stage
or phase may begin and also determining if the previous phase has completed. These predictive
models are considered fit for the following:
• Firms that may contain a very high percentage of developers who are beginners
• Firms that may have a very large number of developers
• Organizations that may have a high demand of orders
• Mission critical functionality.
Waterfall approach is a sequential procedure which is so much the same way as a
normal waterfall. A good amount of time is usually consumed in each and every phase of
development until all the requirements of the system have been met. In comparison to the
agile methods, Agile focuses on adaptability and much more on agility during the
implementation process. Notably, as an alternative waterfall having a development schedule

AGILE METHODOLOGY IS ADAPTIVE NOT PREDICTIVE
which is very rigid, the agile method involves construction schedules which are iterative. There
exists a team which is closely-knit and much more self-organized.
2.2 Substantial Versus Minimal:
When the emphasis is put more on documentation in each and every phase during the
development of the software in the waterfall model, in the agile approach emphasizes is
increased in enhancing the face to face communication and thus reducing the documentation.
2.3 Predictive Versus Adaptive
In the waterfall approach, it is known for its suitability in development of the programs
which are stable while in the case of agile approach is suited best for applications which are
web-based for the reason of it being iterative in nature and thus helping in incorporation and
correction of bugs which may arise with time. There have been several heated debates with
regards to the merits of the adaptive approach versus thus of predictive approach for some
years now. Both sides have got opponents, but in my own opinion, each methodology has got
its own merits if it was to be implemented appropriately. Additionally, there may be no reason
in not to pull out all the best aspects from both in harvesting the maximum returns from the
development investment. A good example is when one may need to maintain an all-inclusive
view of the application landscape and thus in need for deployment velocity, then leading them
to pull from both facets in order to determine if the needs have been met. One can use the
requirement management practices which may be associated with predictive methodologies in
maintaining one holistic view while at the same time adopting the adaptive approach in gaining
the appropriate deployment velocity.
Notably, having discussed that and understanding the two aspects or approaches in
terms of pure development velocity, it is true that an adaptive approach tends to be faster. This
has been so, because adaptive approach exists or maybe due to extra buy-ins from the major
business thus seeing unremitting progress in smaller and perceivable iterates to be really beside
and thus making the software to be very fast. Due to increment and much user input, one will
probably construct and deploy all the solutions which are appropriate by use of Agile adaptive
methodology.

AGILE METHODOLOGY IS ADAPTIVE NOT PREDICTIVE
2.4 Process-oriented Vs People-oriented:
In the waterfall model, the focus is on planning before of all the processes which are
known in details and subsequently to coming up with the overall process which is defined and
thus used by whoever will use it. The agile approach is termed to be adaptive and not predictive
in that they believe in the process definition to be not an independent thing and thus the
software of the will have to rely deeply on the developer skills other than on the processes
which are pre-defined. The agile approach will only use process in supporting the developers in
doing their work more effectively and efficiently. The procedure never takes a lead in agile
methodologies.
3.0 Merits of Adaptive Approach over Predictive approach.
Notably, the use of adaptive methodology will give a chance for all the widespread
stakeholders to engage before the project has begun, in the process and after every phase of
the software lifecycle development cycle (Pradeep, 2017). Through the engagement, the
adaptive approach has offered the provision of a high degree of all client’s collaborating with
the developers due to its involvement in extensive interactions between the developers and
the client during each phase (BANERJEE, 2018). Through communication, the clients can be
able to have an understanding of the the project phase by phase and thus allowing them to be
able to share their ideas and views and thus helping the developers when need arises such as
adding requirements. The client interactions may help the developers in completely
understanding some visions of the clients. When the project is delivered early to the customer,
this will create some trust between the client and developers and thus encouraging them to
collaborate and involving deeper in the lifecycle of the project.
The adaptive approach also allows for transparency. Developers and client, in this case,
work together in each stage. The developer has to explain the status of the project to the
customer before, during and after every phase and thus allowing them to have an intellectual
view of what they may expect and which will indeed give them a chance to share their own
their own sentiments with the developers.
Another merit of the adaptive approach is that it can allow for early delivery. This is
because to its being involved with the client before the software has been initiated, during

AGILE METHODOLOGY IS ADAPTIVE NOT PREDICTIVE
development and after every step in the development of the software, this indeed will speed up
the development which may usher in the early delivery of such software. The adaptive SDLC put
more focus on the values of the corporate, and when they realize a significant value which
satisfies the client significantly, the software deliverables in such situations will be submitted
earlier than it was planned.
Another situation is that an adaptive approach is much focused on the users of such
software. When the clients are involved and much more contributing to the development
process by giving feedback to the development team this in many cases translates in to value
addition to the software being developed. Involvement of the user will ensure that the
requirements to be met will be catered effectively and thus leading to total user satisfaction
being availed in the final product.
Adaptive methodology leads to generation of very high-quality software. This is
achieved by the projects being broken down into modules, concentration is on development of
high-quality software’s, testing one module at one given time, and aiding in the production of a
high-quality product. In this approach, quality is improved through testing and reviewing which
is usually done after every module has been developed. When testing and reviewing are done,
one will also have to find and fix such found bugs at each and every step, and in this case, if
there is a mismatch in expectation then it will be identified and corrected early enough and
hence giving a quality software which will be delivered at the end.
In the predictive approach, there will no working software which will be produced until
the final phases of development. Software will only be generated at the last phase of the
software development lifecycle (Shah, 2018). Testing and review must be performed only at the
last stage of the model lifecycle (Kumar, 2018). These have made the efforts put in this
procedure to be void and wasted since the entire process will have to be repeated so that it can
accommodate the identified requirements.
Predictive approach is also not suited for projects which have complex object-oriented.
This methodology is will only be usable for all projects which are smaller and the requirements
are defined when one is starting the project and the end results are known and determined
from the first stage. Another concept is that predictive methodology is not suitable where all

AGILE METHODOLOGY IS ADAPTIVE NOT PREDICTIVE
the requirements are known or when there is a risk of changing with time. This makes not to be
inapplicable for all long and ongoing projects due to being very rigid and with strictly defined
stages.
Adaptive agile is the best methodology to implement during any development of a given
project. Since in many cases, a project is used by many users, when it is developed using the
adaptive approach it may give us the best end results. In this methodology, there is extensive
user involvement which is employed before, during and after every step in the development. By
use of the predictive approach, the development will be expected to be slow because all the
stages must be finished so that the software can be tested. However, in the agile adaptive
methodology, the end results are produced to the client in each stage, this enables
transparency between them and thus making it easy for them to collaborate. Adaptive being
iterative makes it easy for the developers to tackle a sprint which is a component of a single
module which may be done faster and easier. As seen from the above deductions it will be clear
to say that agile SDLC is a kind of an adaptive approach other than predictive.

AGILE METHODOLOGY IS ADAPTIVE NOT PREDICTIVE
List of References
Aldao, A. and Nolen-Hoeksema, S., 2012. When are adaptive strategies most predictive of
psychopathology? Journal of abnormal psychology, 121(1), p.276
BANERJEE, R., 2018. System and method for estimating package implementation effort of SDLC
activities. U.S. Patent Application 10/146,511.
Erturk, E. and Sezer, E.A., 2015. A comparison of some soft computing methods for software
fault prediction. Expert systems with applications, 42(4), pp.1872-1879.
Jain, R., Sharma, D. and Khatri, S.K., 2017, December. Hybrid artificial intelligence model based
on neural network simulation models for software maintainability prediction. In 2017
International Conference on Infocom Technologies and Unmanned Systems (Trends and Future
Directions) (ICTUS)(pp. 705-708). IEEE.
Kumar, L., 2017. Predicting Software Quality Parameters using Artificial Intelligence Techniques
and Source Code Metrics (Doctoral dissertation).
Li, S., Li, K., Rajamani, R. and Wang, J., 2011. Model predictive multi-objective vehicular
adaptive cruise control. IEEE Transactions on Control Systems Technology, 19(3), pp.556-566
Matharu, G.S., Mishra, A., Singh, H. and Upadhyay, P., 2015. Empirical study of agile software
development methodologies: A comparative analysis. ACM SIGSOFT Software Engineering
Notes, 40(1), pp.1-6.
Nawar, S., Buddenbaum, H., Hill, J., Kozak, J. and Mouazen, A.M., 2016. Estimating the soil clay
content and organic matter by means of different calibration methods of vis-NIR diffuse
reflectance spectroscopy. Soil and Tillage Research, 155, pp.510-522.
Pradeep, R., 2017. Predictive cum Adaptive Systems Development Methodology for HydroGIS
Tool Development, 3(2), pp.10-13
Shmueli, O. and Ronen, B., 2017. Excessive software development: Practices and
penalties. International Journal of Project Management, 35(1), pp.13-27.
Shah, A., Muthusamy, S. and Ramakrishna, K., Cognizant Technology Solutions India Pvt Ltd,
2018. System and method for efficiently predicting testing schedule and stability of applications.
U.S. Patent Application 10/025,698.