Agile Methodology is Adaptive Not Predictive

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.