Agile Methodology For Developing Better Software And Reduce Risk

1820 Words Mar 22nd, 2016 8 Pages
Agile Methodology - Using Agile to Develop Better Software and Reduce Risk Introduction
Imagine an enterprise software development project where the customer says "we are going to take a long time to get this done and we don 't expect to see any results for at least two years". Can you imagine it? Me neither, and the truth is that it will probably never happen:) So what is reality? In the real world of enterprise software development, the key for any development team is to provide maximum value to and work closely with the customer, to be able to build a culture of true ingenuity, and to be able to meet the customer 's changing needs in a way that there is minimal disruption, if any.

In the early days of software development, it was not uncommon for months to pass before any development began, and once development started, it could be months or years before any type of finished product was ready for testing. The requirements definition and gathering process was often very long, and in many cases the development team was isolated from the customer.

Once requirements were complete and development had begun, change was just not something that was easily entertained. Let 's keep in mind that concepts such as Continuous Integration and Configuration Management were unknown and use of source control repositories was not as mainstream as it is now. A change in requirements was just quite difficult to accommodate and was generally frowned upon.

The Agile Methodology
Agile was…
Open Document