Don't Be Held To Ransom

TIPS,TRICK,VIRAL,INFO

I was talking to a ... the supplementary hours of daylight who was ... the fact that the company for whom he works was creature held to ransom by a single ... a ... ... who was the abandoned per

I was talking to a businessman the supplementary morning who was bemoaning the fact that the company for whom he works was beast held to ransom by a single individual, a freelance contractor, who was the deserted person competent of maintaining a critical software system for them. He could more or less suit them what he liked.

How had this come about?
How can you avoid this in your company?

In the past, in order to promptness stirring software enhancement and prolong the moving picture of their older mainframe computer systems, this company had invested heavily in a particular proprietary Rapid Application Development (RAD) software system. This became an integral and essential allowance of many of their necessary applications.

Unfortunately, this particular RAD system did not catch on in the wider marketplace. It is not widely used, and is now in addition to rather dated. so it has become increasingly difficult to find people following the vital skills or the wish to get them. Those few individuals taking into consideration the required skills can retain the company to ransom.

Dont let this happen to your company.

Here are a few easy guidelines on how to avoid finding yourself in the thesame position.

1.Dont be an early adopter of supplementary software systems. create sure a product has an established client base back climbing aboard the bandwagon.
2.When you buy a software package, use it as near to standard as you possibly can. Dont demand masses of special modifications. You will be building in the works huge maintenance problems (and costs) for the future.
3.If you must have non-standard add-ons to customary packages, get the knowledge transferred in house. Dont put yourself in hock to your suppliers.
4.If replacing old systems, create definite you accomplish it fully. Dont allow an dated system be kept and used for just one little function. The eventual (increasing) money will in the distance exceed the (reducing) usefulness.
5.Dont lost sight of the computer graphics cycle costs of a system (purchase, installation, maintenance, replacement). Dont end at just the first two of these items.

You can, of course, conveniently apply these checks to any major buy or project for change, not just to software.

The key to it all is guideline number 5 above. If you properly deem the entire cartoon of a project from start to finish you will inevitably tolerate into account the further necessary aspects.

Unfortunately in in view of that many cases the longer term elements acquire swept aside and ignored. colossal consideration stops at the tapering off of implementation. Too often the man in dogfight of the yet to be stages of a project does not have to tolerate responsibility for the cutting edge consequences. fittingly create sure that isnt the accomplishment in your company.

In conclusion:
Be wise previously the event. Be au fait of the consequences. Think of the long term. Dont be held to ransom.