CHILDREN´S POEMS IN ENGLISH

Traditional Software Development vs Agile Software Development

Software development is a discipline that all relate directly to the progress, improvements in productivity, and a lot of smart people working hard and generating significant benefits for businesses and society. At the same time we note that projects often suffer delays and the expected results despite the talent and effort put into action by analysts, programmers and users to that "new" work properly and on time are obtained.

 A contiuación are named and described how they have been working as software development (traditional) and the way in which it intends to improve this development (agile).

The traditional way of developing software based on predefined processes with very precise documentation and a detailed initial planning that must be strictly followed. This way of working emerged naturally fifty years ago as an adaptation of the management of engineering projects, which was the closest thing to develop programs that are known at that time, and it worked reasonably well at first. It is also necessary to note that computers were extremely expensive, most of the investment is the carrying computer equipment and for this reason the programs are tailor made for machines that were purchased, lest we forget, for some tasks very specific.

But software development projects today include very different challenges that arise when constructing bridges and houses, so it is not surprising that the traditional methods of software development are in crisis.

Development projects with Agil is intended that all efforts are used in creating the best software that meets customer needs. This means that all who are part of the team are focused solely on tasks and processes that add customer value of the product being created, improved or implemented. Additionally, users or clients receive regular functioning prototypes or versions of the product as it is being built, which allows them to evaluate the work done, warn of problems identified, and suggest improvements or valuable functionality that was not originally considered (either through forgetfulness, or because the new functionality is inspired by the experience of evaluating the product while being built).