Envision an enterprise
software development project where the client says "we are going
to take quite a while to accomplish this and we don't hope to see any
outcomes for no less than two years". Will you envision it? Me
not one or the other, and the fact of the matter is that it will most
likely never happen:) So what is reality? In this present reality of
enterprise software development, the key for any development group is
to give greatest quality to and work nearly with the client, to have
the capacity to manufacture a society of genuine resourcefulness, and
to have the capacity to meet the client's changing needs in a manner
that there is insignificant disruption, if any.
In the beginning of
software development, it was not unprecedented for quite a long time
to go before any development started, and once development began, it
could be months or years before any sort of finished item was
prepared for testing. The prerequisites definition and get-together
process was frequently long, and by and large the development group
was isolated from the client.
When prerequisites
were finished and development had started, change was quite recently
not something that was effectively entertained. How about we remember
that ideas, for example, Continuous Integration and Configuration
Management were obscure and utilization of source control stores was
not as standard as it is presently. An adjustment in prerequisites
was just truly hard to suit and was for the most part grimaced upon.
Agile was initially
presented in February 2001 through the Agile Manifesto, an archive
made by a gathering of designers who met in Snowbird, Utah to discuss
the standards behind an approach to do lightweight software
development. From that point forward, the Agile Methodology has
developed and been broadly received by software development groups
and organizations around the world.