What Are the Advantages and Disadvantages of Agile Software Engineering?
What are the advantages and disadvantages of Agile Software Engineering?
One mooted solution to project management issues is Agile Software Engineering. Agile software engineering was devised, in the early 1990's, as a counter to the then-prevalent preference for huge, carefully-planned and expertly orchestrated grand projects. As Alistair Cockburn has noted, "the 1990's saw some of the most bloated, over-organised attempts at problem-solving imaginable, whereas agile software engineering came in like a breath of fresh air and proclaimed that the era of the individual was back" (Cockburn, 2001). While the old system was believed to deliver nothing more than bureaucracy, inconsistency and ineffectiveness, agile software engineering was seen as a new way of offering software engineers the chance to work on a series of steps, making their own decisions and working with others as and when they saw fit. Eventually, in 2001, the proponents of the new, more agile methods of software engineering met and issues an Agile Manifesto, which laid out the new principles that they believed should govern software engineering.
The agile software engineering movement had a number of key aims: rapid response to change was favoured over just following a plan; working with customers was favoured over simple contract negotiation; working software was favoured over partially-working software with complex documentation; and finally, individualism was favoured over the use of individuals as simple steps in a process. Also, agile software engineering sought to ensure the continued and rapid delivery of changes and new ideas would impress upon the customer that the engineers were able to react to constantly changing situations. Meanwhile, it was also considered important to allow for constant changes, including changes at the very last minute, just as the product was ready to be unveiled. Finally, it was felt that the process had become almost more important than the outcome, so agile
One mooted solution to project management issues is Agile Software Engineering. Agile software engineering was devised, in the early 1990's, as a counter to the then-prevalent preference for huge, carefully-planned and expertly orchestrated grand projects. As Alistair Cockburn has noted, "the 1990's saw some of the most bloated, over-organised attempts at problem-solving imaginable, whereas agile software engineering came in like a breath of fresh air and proclaimed that the era of the individual was back" (Cockburn, 2001). While the old system was believed to deliver nothing more than bureaucracy, inconsistency and ineffectiveness, agile software engineering was seen as a new way of offering software engineers the chance to work on a series of steps, making their own decisions and working with others as and when they saw fit. Eventually, in 2001, the proponents of the new, more agile methods of software engineering met and issues an Agile Manifesto, which laid out the new principles that they believed should govern software engineering.
The agile software engineering movement had a number of key aims: rapid response to change was favoured over just following a plan; working with customers was favoured over simple contract negotiation; working software was favoured over partially-working software with complex documentation; and finally, individualism was favoured over the use of individuals as simple steps in a process. Also, agile software engineering sought to ensure the continued and rapid delivery of changes and new ideas would impress upon the customer that the engineers were able to react to constantly changing situations. Meanwhile, it was also considered important to allow for constant changes, including changes at the very last minute, just as the product was ready to be unveiled. Finally, it was felt that the process had become almost more important than the outcome, so agile
Bibliography: Bell, Michael (2008). 'Service-oriented Modelling '. New York: John Wiley and Sons Bott, J. & Carver, H. (2000). 'Service-oriented Architecture: Standards and Practices '. London: Routledge Brooks Jr., Fred (1975). 'The Mythical Man Month '. London: Addison Wesley Brooks Jr., Fred (1995). 'The Mythical Man Month (Revised) and Other Essays '. London: Addison Wesley Erl, Thomas (2005). 'Service-Oriented Architecture: Concepts, Technology and Design Practice '. London: Prentice Hall Glass, Robert L. (2002). 'Software Runaways: Lessons Learned From Massive Software Project Failures '. London: Prentice Hall Van Vliet, Hans (2008).