Mobile solutions are expected today to come with frequent
updates, solution improvements and requested functionality. Especially if your
particular solution is being built along an agile development methodology,
clearly advocated in my previous article, don't assume your business know what
they need in this brave new world - this is an interactive requirements cycle. This setup drives the needs for an accompanying Release Management
(RM) methodology which allows for these frequent updates to take place. The
topic I’m about to cover is really aimed at enterprise mobility solutions which
are integrated with at least one back-end platform.
