Upgrades used to control Software Delivery.

How well do you upgrade from one version to the other, do you run them side-by-side, etc, etc?

When we deployed client/server the big separator is that they were ALWAYS distinct.

Now we live in a world where we can “toggle” between the old and new, bringing about its own challenges.

If you’re building software that toggles between feature sets there are a few scenarios you should always be aware of;

  1. Make sure one setting doesn’t bleed into the other.
  2. Keep them independent.
  3. If you’re introducing the toggling to get feedback, ask for it, if they don’t want to give it, don’t force them to toggle each time.
  4. Give them a reason to toggle (some different and new).
  5. Don’t keep it running forever, the new has to take over the old at some point – two years of toggling is not useful.

Or you can go back to the way it was, update the user with your new version, and move on.

Software Delivery is not about slowly boiling the user into accepting the situation they are in.

Want more? Check out my book Code Your Way Up – available as an eBook or Paperback on Amazon (CAN and US).  I’m also the co-host of the Remotely Prepared podcast.

Author

Write A Comment