Agile Software Development

Agile methodologies by: Jose Sena as systems analyst we know in these times, the pace that leads the software industry is totally different from previous decades, everything today requires a faster. The traditional methodologies such as the waterfall model, present many difficulties since it tends to be seen as bureaucratic, slow. While waterfall model is well suited for large projects, usually not very suitable for current projects, where the systems environment tends to be very changeable, especially when it is required to reduce development time while maintaining the quality. As a way of responding to this problem, it is then that arise the so-called agile methodologies. Because they are specially oriented for small projects, agile methodologies are a tailored solution to this changing environment, providing a high simplification which nevertheless does not renounce to the essential practices to ensure the quality of the product. All these developments related to the problems of the methodologies classic, led to that at the beginning of the year 2001 in the city of Utah, USA met a group of experts from software engineering and created The Agile Alliance, whose starting point was what became known as the manifesto of the agile methodologies (Manifesto for Agile Software Development 2001) (Beck, Beedle & al, 2001). The objective of this Alliance is the promote the concepts related to the agile software development and helping organizations adopt those concepts in a beneficial way. This document formulates four essential guidelines (Beck, Beedle & al, 2001): individuals and interactions over processes and Tools Software that works over comprehensive documentation customer collaboration over contract negotiation responding to change over following a plan.. A leading source for info: Eliot Horowitz.


Tags:

 
 
 

Comments are closed.

© 2011-2019 Cyber Snaps All Rights Reserved