Discussion Locked

IT Debate: Applications deployment

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

According to Gartner, small and midsize businesses can obtain application functionality in one of three ways: build their own, buy packaged applications, or retain a variety of outsourced application deployment services. But there is no perfect solution: Organizations must weigh their options.

What do you think is the best choice? What has been your experience with buying, building, or outsourcing applications? With so many packaged applications that can be customized, when do you think it makes sense to build? Several high profile ESPs and ASPs have abruptly closed, leaving clients in a bind. Do you think this has doomed the future of the rental option?-especially for mission-critical applications?

You can read the related Gartner article, which will be posted 3 A.M. Wednesday, at
https://www.techrepublic.com/article.jhtml?id=r00620010221ggp01.htm

10 replies

by fgarber

In our company we do all three. Many of our mission critical applications are built and maintained in house while others are outsources to reputable consultants. Many of our desktop applications are off the shelf. We have a very small (11) staff supporting a nationwide network of 70 + Novell and Windows servers. What we have time and resources to do in house we do. The rest we handle any way we can.

by realgem

There is no single best answer. As usual, with these types of questions, the answer is "it depends".

Each form of deployment has its pros and cons. You must trade off cost, quality, control, stability, longevity, development time, etc.

With packaged or outsourced deployment, you may pay more up front, less in the long run, but you hand over control of the upgrade plan to someone who is not necessarily considering your needs.

With internal deployment, you may pay less up front, but you might be re-inventing the wheel and paying for this cost. You must also support the application.

Pick the one that suits you best, but for goodness' sake do a proper analysis first. Don't think that ASPs are silver bullets just because they get a lot of air time. Don't be a "not invented here" bigot either.

by johnyboy

Outsourcing is very risky in that you become reliant upon a 3rd party that will nail you down with the contract and any further enhancements/changes will be costed.
In-House dev if you have the staff then this is the most cost effective, if the developers are inhosue they will have a true understanding of the business logic invloved, and can make quick(ish) changes.
Off the shelf - can be successful, but it is very hard to find a package that does everything you want it to, try looking for a package that contains its own scripting routines that way if you find a package that will do 95% of your tasks the scripting will provide the other 5%

by aonwell

The company system architect/engineer's
career is changing from one of pure technical
IT knowledge to one of indepth knowledge of
the companies business objectives and
direction. The SA/E's role is to assist and
define the long term software strategy for
the company. By buying, the IT department
becomes a group of integ. rather than
developers. "Buying" implies a partnership
with the software provider. If they are not
willing to provide on-site support, etc.,
then the buy decision isthe wrong way to go.
If in doubt, extensive trial period is the
best way to evaluate and possibility rent is
the best approach. However, once a decision
is made, expect the develop a long term
relationship with the provider and adopt
their architecture to the business.

by jimhm

It depends, each have their pro's and con's. But outsourcing is better if you manage the outsourcer and not let the outsourcer management you.
Here for outsourcing we include in the contract, deliverables and scope of work, "knownledge transfer." This includes all documentation from project design to code. We also assign one or two inhouse staff as seniors to the project to ensure corporate standards are followed.
We have found outsourcing to be a plus as long as we manage them from birth to grave and have all requirements, scope of work, milestones, and deliverables in the contract before we get started. (if you do your work, outsourcing is can large productivity gain.)

This discussion is closed to new replies.