The malfunction of E-Government in developing countries

In this article, the aim was to analyze the possible profound factors that must be avoided to increase success ratio in the implementation of electronic governing procedures.

It has been proven that the societies with the flexibility of choosing the uprising technologies vociferously cultivates more rapidly. Despite advancement in other scientific branches, the invention of computer science has galvanized the whole society by proposing the new escalated trading ways , communication means and the education systems.
The primary challenge is the inclusion of computer technology to govern the institutions. However, it is appalling that developing countries are not slicked enough to hook such fast and useful technology to bring revolution in administration and governess procedures.

According to the survey and poll results, the success rate of e-government projects in the developing countries is only 15% , 50% of the project face total failure and 35% get the partial success. In this article, the aims will be to discover the possible reason behind malfunction of electronic government.
(a).
The first and the most imminent problem is the appointment of a project leader. It is a common practice in every country, that a person is employed to lead a project that is not related to his area of expertise. For instance, if an individual is veteran to operate and debug a machine of kind ‘x’, it does not mean that the same person has the similar skills to control or operate the machine of the kind ‘y’. For instance, a naïve project leader frequently urges for the rapid software development. As the development of a computer software follows a per-defined orchestrated life cycle. Hence, the rapid development results in low quality and could face the failure in implementation phase due to traumatic issues regarding the up gradation and maintains.

(b).
Despite experience, a software project also requires the entrenched planning including the clear objectives, hiring of staff and their responsibilities, resource management and financial distributions. Hence, forged planning vicariously leads to the abortive implementation.

(c).
The higher expectation from a software product is another dilemma that can straine its success rate. For instance, the worker expects the automation to an imaginary threshold limit that is insuperable to achieve. Hence, consolation is mandatory to educate the users before the implementation.

(d).
The uncertainties, for instance, financial and technical may teeter the project life and also entail to its failure. The project financial deals with the expenses such as the payment of salaries and rejuvenation of hardware and software produces. The technical aspect is more daunting and comes when the team is struggling to complete a project due to lack of technological experience. Such situations can be avoided by using the feasibility study.

(e).
The project must be able to provide the job security to the employees along with carrier growth. Frequently, the workers leave the organization when receive a better carrier oriented opportunity. This affect the progress of ongoing development in addition, the organization lost its experienced slick. Similarly, the new member may need some time to get synchronized with the ongoing development.

(f).
Generally, under going projects are more profound in documents. Infect no project is ‘failure’ when it comes to documentation. Hence, the outcome of a project must be measured in terms of an object-oriented way rather than document oriented

(g).
The project must be free from the political influences of employees working inside the organization. It is axiomatic that the peoples with competing interests are tends to more critical and objective for their counterparts.

(h).
The worker or end users (the persons that use the computer software) are the real assets within an organization. Even perfect software cannot get the success without the participation of working community. In this context, the followings are the additional parameters that persuade to the project failure after the implementation.

(i) Psychological
Psychologically, the workers don’t want to lose their owner ship that they hold on the manual processing procedures. The electronic file processing method curbs the social influence inside organization.
(ii) Technical.
The technological transformation for a person who worked on the manual files throughout his life is another astounding issue. This problem can be solved by introducing special detailed training sessions by providing the training kits in Urdu.
(iii) Economical
The economic factor deals with the inclusion of special salary increments to the employees working on the new technology. This will provide a motivation and workers will try to learn fast and increase the success of product.