But, what makes Agile Methodologies different from traditional engineering methods?
There are two major differences between both methodologies: Instead of finding a new way to improve requirements definition, Agile methods assume that these initial definitions will be changed, focusing the teams effort in adapting to new requirements rather than in predicting them. Even if analysts could settle the fuzziness of requests and get an accurate and stable set of requirements, the projects wouldn’t be kept from failing. In today’s economy the fundamental business forces change the value of software features too rapidly and most of these changes are unpredictable. That’s with IT teams need methodologies that give them control over unpredictability. This is what adaptive processes is all about. Agile methods are people-oriented rather than process-oriented. The goal of traditional engineering methods is to define a process that will work well whoever happens to be using it. Agile methods assert that no process will ever make up the skill of the development team, so the role o
