Even with the research showing advantages of the Agile software development practices and methodology, there is still resistance. Any change brings challenges, costs and extended timelines – not all organizations are ready to take on these challenges and not all user bases are ready to make major changes to their long established way of doing things and performing their jobs. Change is painful for many, not to mention scary, confusing, frustrating and carries the always apparent potential for failure and embarrassment.
Introducing Agile practices into an organization can be a challenging task. For new adopters, the case for Agile methods has to be supplemented by results showing the high failure rates in traditional projects. Highlighting the inherent defects in the Waterfall model and promoting the idea of iterative development could also serve as useful strategies...