A Comparative Analysis of Traditional Software Engineering and Agile Software Development

Abstract

Over the last decade (or two) the pendulum of developer mindshare has swung decidedly towards agile software development from a more traditional engineering approach to software development. To ascertain the essential differences and any possible incompatibilities between these two software development paradigms this research investigates a number of traditional and agile methodologies, methods, and techniques. The essential differences between traditional software engineering and agile software development are found not to be (as one may first suspect from a cursory consideration) related to iteration length or project management, but rather more related to other attributes like the variety of models employed, the purpose of the models, and the approach to modeling. In the end though the two approaches are not seen to be incompatible, leading to the future possibility of an Agile Software Engineering (ASE).

The relationship of personality models and development tasks in software engineering

“…In addition to these arguments, there are some developments that challenge our understanding of software developers' personalities: Software development trends such as technological change (Gallivan 2004), new methodological paradigms (Aitken et al 2013), outsourcing (Gopal et al 2009), distributed teams (Espinosa et al 2007), open source development (Roberts et al 2006), developments in task complexity (Varona et al 2012), globalization, or new business models (ExecutiveBrief 2013) fundamentally change the tasks software developers are confronted with (Snyder et al 2006).…”

Agile Methodologies and The Use of Its Waterscrumfall Derivative For Software Project Development

“…The basic idea is that the requirements are totally completed in each step. This is practically impossible and does not recognize that rework is needed for most projects [2].…”

“…Scrum appears to be the most popular of the agile methods and is being used with the traditional waterfall method to provide a mixed derivative referred to as the 'Water-Scrum-Fall methodology [2].…”

Aplicação Do SQFD Em Um Software De Vendas No Contexto De Desenvolvimento Ágil Gerenciado Pelo Scrum

“…Já no modelo Incremental, os requisitos são divididos em subconjuntos (STOICA; MIRCEA; GHILIC-MICU, 2013). O modelo Incremental corresponde melhor ao mundo real do que o modelo em Cascata, visto que reconhece a necessidade de voltar e modificar resultados de fases anteriores, e que os desenvolvedores de software nunca conseguem, de fato, completar totalmente qualquer atividade (AITKEN; ILANGO, 2013). Esse modelo é a base para as metodologias de desenvolvimento ágil (STOICA; MIRCEA; GHILIC-MICU, 2013).…”