1 reply
by dc guy
As a consultant for many years who saw the insides of dozens of IT shops, my studied opinion is that contracting is only cost-effective in the long run if its use is strictly limited.
As a general rule the most successful companies had the most successful, best run, panic-free IT shops and the most trouble-free software. The policy in these shops was invariably to insource unless an airtight case could be made for outsourcing.
Airtight cases were very limited. A system that needed to be built only for interim use. (And how many of us have seen "interim" systems still in production twenty years later?) An arcane type of software in which expertise could simply not be acquired in house. (And just who was going to maintain it in that case?) A big project that would create a one-time bulge in the workforce that could not be absorbed after project completion. (What IT shop couldn't make use of a few dozen really good programmers?)
The biggest problem with contracting is lack of continuity. We've all had the experience of finding out that the most horrible assignment in the world is to maintain somebody else's code.
It goes without saying that the best shops I observed also had the lowest turnover.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending