Mobile Agile Development Pitfalls: A Back-to-Basics Primer for Stakeholders

Agile has been popular for a long time, and its popularity has only increased with the growth of mobile application development. Mobile applications need constant and progressive enhancements to keep up with end-user expectations, and this is something Agile is particularly well-suited for. While Agile can be your biggest asset, it very easily can turn into a false safety net, and a recipe for disaster. Here are five common mobile Agile development pitfalls, and a back-to-basics reminder of the Agile principles they violate:

Mobile Agile Development1. Treating Agile as an Engineering-Only Exercise.

Too often, non-technical stakeholders do not participate in stand-ups, sprint planning and reviews. There is a perception that Agile, being a software development methodology, is purely in the engineering domain, which can cause other stakeholders to refuse to participate.

In reality, this approach results in decreased visibility into progress, longer and less effective communication channels, and reduced ability to make quick and correct decisions. It is no coincidence that one of the main principles of Agile is: “Business people and developers must work together daily throughout the project.”


About Andrej Kostresevic

Andrej is Nomads' CEO and tribe leader. He has over two decades of experience in the software engineering field and two awesome dogs, Kai and Zen.

Leave a Reply