Software developers and project managers are struggling to assess the appropriateness of agile processes to their development environments. This paper identifies limitations that apply to many of the published agile processes in terms of the types of projects in which their application may be problematic. INTRODUCTION As more organizations seek to gain competitive advantage through timely deplo...

Formal Model Driven Engineering (MDE) can be considered incongruent with Agile methodologies. However, with the advent of Agile, Software Engineering educators have an obligation to teach Agile development. Many instructors do so by employing experiential learning through Agile classrooms and projects. Teaching formal MDE and convincing students of its benefits can be challenging in such enviro...

Many software companies are interested in using Agile methods in their software projects. Contrary to traditional software development methods, Agile methods are people oriented. This fact shows the significant role of individuals in these methods. Increasing prevalence of Agile methods forces software companies to consider people related factors as critical issues in adoption and transition to...

Organizations delivering offshore software development services have traditionally focused on CMMI framework to deliver quality software. With agile methodologies gaining more wide spread acceptance, such organizations cannot stay away from them. There are concerns about combining agile methodologies with offshoring. There are also concerns about mismatch of agile methodologies with CMMI framew...

While research has demonstrated positive productivity and quality gains from using agile software development methods (SDMs), some experts argue that no single SDM suits every project context. We lack empirical evidence about the project contextual factors that influence when one should use these methods. Research suggests several factors to explain agile method appropriateness; however, genera...

Agile software development methods have been developed and evolved since early 1990s. Due to the short development life cycle through an iterative and incremental process, the agile methods have been used widely in business sectors where requirements are relatively unstable. This paper explains the differences between traditional software development methods and agile software development metho...

Agile methodology continues to evolve due to business and technological demands. However, there are few studies reported related to encouraging new organizations to adopt agile practices especially in Asian countries. This paper presents the initial findings from an action research study on agile-extreme programming (XP) adoption amongst software engineering (SE) teams. The results showed that ...

Lightweight, 'agile' software development methods are not a replacement for traditional, heavyweight methods. But under certain assumptions, they are a welcome alternative in many areas of software development. In this paper, we outline the di erences between agile and traditional approaches of software development and examine how development tools are used in the latter. We consider experience...

This article compares traditional requirements engineering approaches and agile software development. Our paper analyzes commonalities and differences of both approaches and determines possible ways how agile software development can benefit from requirements engineering methods. Index Terms Requirements Engineering, Agile Development

Agile methods and MDE are often considered to be polar opposites of each other. Agile methods are fast, adaptive, responsive; MDE is heavyweight, planfirst, and requires high up-front investment. But are agile methods and MDE really so contradictory? Or could they co-exist and even work together to maximize each other’s benefits? In this talk, I will reflect upon our recent study with two large...