|
Software upgrades can be a lucrative opportunity
for software developers, or they can be a support
nightmare. Here are some software upgrade tips
to help make the process pain-free and profitable.
Seamless Upgrades
When a customer upgrades from an old version
to the latest version, the upgrade should be seamless.
Data and software settings should remain intact
through the upgrade. The upgrade path should always
be pain-free for existing customers.
Bugs
Keep in mind bug fixes are not upgrades. Customers
are normally willing to pay for upgrades only
if the new version contains new features or enhancements
that expand or improve the software's functionality
or capabilities.
Compelling
There must be a compelling reason for customers
to upgrade. Upgrades should incorporate new features,
or enhance the software's existing abilities.
Do not rely on release notes to convey reasons
why customers should upgrade -- develop sales
copy that details what new problems or issues
the upgrade will resolve.
Operating Systems
Consider support for a new Operating System
as a feature. When a new operating system is released,
applications will often require an upgrade in
order to function properly. If the new upgrade
version no longer supports a specific operating
system, be sure to make that clear to existing
customers in the documentation and sales materials.
Compatibility
Upgrades should always be backwards compatible
when ever possible.
Encourage Backups
Even if the upgrade process is flawless, you
should still encourage customers to completely
backup the software application and their data
BEFORE they install the upgrade. This will help
protect the customer's data and information in
the event something goes wrong during the upgrade
process.
Distinguish
Be sure to clearly distinguish between minor
version upgrades and major version upgrades, both
in the version numbering, and in the level of
promotion that an upgrade receives. All existing
customers should receive email notifications for
major releases.
Use Conventional Numbering
Version numbering should follow standard conventions,
where minor releases are "point" releases and
major version releases result in version number
changes.
Example:
Minor Upgrade: 2.1 - 2.2
Major Upgrade: 2.2 - 3.0
Timely
Upgrades should be spread out over time. Developers
who release upgrades too often may cause their
customers to question the software's stability.
On the other hand, MicroISVs who do not keep a
product updated may find that their customers
think the software has been abandoned.
Thorough Testing
Upgrades should be thoroughly tested before they
are released. Existing customers should not be
used as guinea pigs or unknowing beta testers;
they should be valued, so be sure that upgrades
are thoroughly tested before they are released.
Use these tips to make the most of your software
upgrades.
Related Articles:
Going Retail
How
to Recreate Customer Problems
How to Conduct
Effective Beta Testing
|
Developer
101
Tips
for Software Upgrades