General discussion

Locked

Move from in-house to outsource provider

By Bob L. ·
The software development department of our small IT service company started as an in-house department at our largest client. We are in the process of growing, and expect to service multiple clients. Does anyone have experience making this transition?
The large client still expects fairly intimate relations during development. What kind of network connectivity works best?

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Move from in-house to outsource provider

by jmessina In reply to Move from in-house to out ...

YES, we have done this for a few companies and have also accomplished it for ourselves, We are a "small" consulting firm that has gone through these ssame changes. The less stress on the client the better. What are you doing now for Network connectivity ?, Why Change It?.

Collapse -

Move from in-house to outsource provider

by Bob L. In reply to Move from in-house to out ...

I'm looking for wisdom gained from similar experience.

Collapse -

Move from in-house to outsource provider

by Bob L. In reply to Move from in-house to out ...

Our applications development department is still working within the client network. In order to service other clients, we will have to move them to our own network. That raises questions about where we store source code, the technical acceptability of testing via a link through Terminal Server, etc.

Collapse -

Move from in-house to outsource provider

by capthlp In reply to Move from in-house to out ...

Bob, I am in the service deliver business to multiple clients. My suggestion would be to capitialize on the delivery methodologies you have developed for the initial client, be flexable enough to modify according to the needs of the new clients and be very very careful during transition and implementation of new clients. Remember to dance with the one who brang you!!!! Good Luck, if you have any specific questions please feel free to email me. I have been in the outsourcing business for over 13 years and can tell you that each engagement brings its own set of issues regardless of the package it is wrapped in.

Regards, capthlp@attbi.com
George

Collapse -

Move from in-house to outsource provider

by Bob L. In reply to Move from in-house to out ...

The question was auto-closed by TechRepublic

Collapse -

Move from in-house to outsource provider

by Todd Kimbrell In reply to Move from in-house to out ...

This is a good problem to have, and I've been fortunate enough to spearhead a project similar to yours two years ago when a local hospital wanted our development group to coincide with their information technology group.

I do not intend on providing an answer, just what we experienced during this celluar mitosis.
Critical Path Method
First off, I am certain that you have specific outlined IT policies in place. And so does your client. I am suggesting that these policies are the first issueof resolve before we begin with network connectivity. Case and point: Convergence of IT Policies Phase.

Appoint client relations management, there are key people on both sides that should have the appropriate relationship and domain knowledge that is needed during the integration phase, and should have chain of command outlined in a flow chart.

Addressing timeline: What are the existing time constraints that apply to your clients needs. This should be broken down into phases or inchstones, whatever you want to call them. Again having the key players responsible for reporting and addressing issues.

Theses were the basics we had to learn during this process, You probably have much more already in progress.

Now on to network connectivity.
Having our customer within the same metropolitan area as ours, we had to bring over all the code, mx records, dns addresses etc, to our network. We used terminal server at the beginning, however, we had some heated discussion about security, so we decided to utilize a VPN structure and created a metropolitan backbone between sites, this allowed us and them the ability to communicate, and co-locate between projects. The medium was a T-3 with cisco 8300's on both sides, and we also trunked 3 lines over to extend the pbx (Nortel Meridians). Then eventually using VoIP between sites.

Collapse -

Move from in-house to outsource provider

by Todd Kimbrell In reply to Move from in-house to out ...

I would also like to address the source code placement issue you brought up. We started out with a central server that contained the working source code, and then individual folders, help files, osi and layer compliance, forms, queryies, API, and DLLs. Each folder allowed the the appropriate individual(s) access to them during the development process. A second server contained a mirrored copy of that work in progress that was then backed up and the master DAT was placed off site as the projectwent on This particular layout worked well until we began to Beta the software, we then had to create a pre-production server to allow in-house testing to be performed. The next step was then carried out with select users testing the software in parallel. Anyways, long story, short answer. This is just what we did tk

Collapse -

Move from in-house to outsource provider

by Todd Kimbrell In reply to Move from in-house to out ...

Just one more thing. If you have the resources available to you, swap one of your clients staff members with one of yours that allows an excellent way to enhance communications and domain knowledge between entities.

Collapse -

Move from in-house to outsource provider

by Bob L. In reply to Move from in-house to out ...

The question was auto-closed by TechRepublic

Collapse -

Move from in-house to outsource provider

by Bob L. In reply to Move from in-house to out ...

This question was auto closed due to inactivity

Back to Community Forum
10 total posts (Page 1 of 1)  

Related Discussions

Related Forums