The internet has a profound impact on software. Even on software that is locally installed on a device (in this case the iPhone)

Here are the guidelines that Apple gives to their ISVs how often to update their applications.

(c) Apple Inc.

Please note what they consider to be a “low frequency” in updating!

We feel the same way. Our client/server product conjectCM has a steady monthly release rhythm. Not every customer gets every release, but we work in a steady monthly cadence.

For our SaaS product conjectPM we have a bi-weekly release schedule. If a post-release defect makes it necessary to have another release on the next day – no problem!

We used to release each individual story. This led to multiple releases every week. Now we bundle the work of one iteration (two weeks) into one release. This allows us to better communicate changes to our users and gives us more time for testing those parts of the application which we haven’t covered with automated tests, yet.