Our vision is to provide our clients with a platform which evolves as
the market and the business environment change; a system which allows
PortaOne customers to gain a competitive advantage and successfully
expand their ventures; a system they can rely on today, tomorrow, and
for many years ahead in the future.
Every year, PortaOne development team produces about three new
maintenance releases of PortaSwitch. Each maintenance release is a
comprehensive collection of improvements, bug-fixes and, most
importantly, new modules, features, and capabilities.
We appreciate and welcome all suggestions about improvements to our
software products, especially those submitted by our customers. The
"wish list" of features (a collection of suggestions, recommendations
and ideas) usually contains several hundred items, and new entries are
constantly being supplied by our existing and prospective customers,
partners, and internally, by PortaOne engineers.
When a new maintenance release is planned, we face a challenge of
choosing a specific set of features to include in it. All of the
features in the wish list are useful and beneficial in one respect or
another. Since there is just a few months time for development and
testing of a new release, only a small subset of all the possible
features can be implemented in a given release. Any other features have
to wait until the next release is planned, when we will do the same
selection process again.
The question of selecting specific features to be included in a release
is an extremely important one. Our responsibility is to apply our
engineering resources with the maximum possible benefit for PortaOne
customer. We do not project our vision of the market and decide on the importance
of one feature or another based on some non-objective factors each
PortaOne customers business is unique, and each knows best what is
most important for them. Therefore, we offer a fully transparent and
fair feature selection process that allows our customers to actively
When a specific feature is important to a customer, this customer may
become a "project owner" of its development. The customer sponsors the
development efforts associated with the particular feature, and in turn,
we prioritize this custom feature development by including it in the
next available release and committing to a specific delivery date.