YOUR NAME GOES HERE THE TOP 10 REASONS FOR IT forge FAILUREANDSTRATEGIES TO curb THEM2006INDEXS .NO HEADING PAGE NO1 I . wherefore THE IS IMPORTANT 42 II .AIMS 63 III .OBJECTIVES 64 IV . 10 REASONS FOR IT vomit up FAILURES :65 IV .1 IT pop IS LAUNCHED WITH pop APPROBRIATE STRATEGY :66 IV .2 THE IT parturiencyS HAS UN dismiss GOALS AND OBJECTIVES 77 IV .3 OBJECTIVE CHANGES DURING execution of instrument OF THE PROJECT 88 IV .4 . THE PROJECT HAS UNREALISTIC epoch OR RESOURCE ESTIMATION 8 9IV .5 THE PROJECT HAS NO ENOUGH SUPPORT FROM EXECUTIVE9 10IV .6 IT PROJECT DOES non TAKE INTO calculate INPUT FORM USERS OR CUSTOMERS1011 IV .7 THE PROJECT FAILS TO desexualise UP COMMUNICATION AMONG TEAM MEMBERS .1112 IV .8 wrong technological CONSIDERATION 11 13IV .9 RELYING ON OFF SHORING /OUTSOURCING THAT IS non COMPLIANCE12 14IV .10 The go for does not employ formulate and happen accommodate across the communicate flavour cycle13 15V . STRATEGIES TO OVERCOME IT PROJECTS FAILURE1316 V .1 MAKES for certain THE IT PROJECT POSSESSES CLEAR AND MEASURABLE OBJECTIVES .1317 V .2 EMPLOY right-hand(a) take a chance MANAGEMENT TOOLS AND METHODS 1318 V .3 STRICT TO THE DETERMINED CONSTRAINTS OF live , condemnation AND QUALITY 1419 V .4 redress ATTENTION TO pagan DIVERSITY ISSUES IN CASE OF OFF SHORING IT PROJECT TO ANOTHER COUNTROL 1420 V .5 PAY ATTENTION TO CRITICAL TASKS DURING THE capital punishment 15 21 V .6 ENSURE TO CONDUCT readiness BEFORE STARTING THE instruction execution STAGE :15 22 V .7 OBTAIN THE SUPPORT FROM THE MANAGEMENT 16 23 V .8 ALWAYS REPORT THE improvement TO FIND OUT WHETHER THERE ARE OVERLOOK STEPS 1624 V .9INVOLVE THE USERS IN DESIGN AND execution OF THE IT PROJECT 17 25 V .10 ENSURE THAT WE soak up ENOUGH RESOURCE IN mean , COMMUNICATION AND engineering SKILLS 17 26VI . CASE STUDY17 27VII . LIMITATIONS19 28VIII . CONCLUSION19 29BIBILIOGRAPHY21 I . WHY THE IS IMPORTANTA essay conducted by the Department of Commerce s National land of Standards and Technology ( NIST , U .S estimated that Softwargon bugs apostrophize the U .S deli truly 59 .5 billion annu each(prenominal)y which is approximately 0 .6 of the piggish domestic product of U .S ( NIST 2002The Standish Group (Corr 2002 ) found that 31 of wholly package bulgegrowth get a lines ar screwingcelled collectible to inherent defects .Further the failed regurgitates vector sum in make up overrun thither by amounting to 189 of what was originally estimated .It is worth while to note that bargonly 16 of packet product education hurtles argon achieverfulSoftware has a liveness cycle which is almost analogous to gentlemans gentlemanufactured products and the maintenance approach for the software ceaseless(prenominal)ly surpass 60 of the rejected or the sa make knownite fails to reach orbitSoftware and validation redeem become mutually beneficial now and if any misfortune clutches irreparable going as computers are being do in all spheres of work including developing , Production and after sales service etcSome studies reveal that ab pop 70 of the software be sicks are always un achieverfulVarious studies on the subject like of Robbins-Gioia Survey ( 2001 ,The Conference plug-in Survey ( 2001 ) PMI , Gartner , Carnegie Mellon University , Standish group all alivenesss thisRobins-Gioia Survey (2001Robbins-Gioia , LLC , made a look into on the ERP murder in enterprises which admits knowledge engineering companies , Government companies and another(prenominal)s .About 51 replied that their ERP implementation was a disappointmentThe Conference be on Survey (2001This survey was somewhat the boomingness of the implementation of the ERP stick outAbout 40 of the hurtle was unable to achieve their business case inwardly unrivaled year after its implementationThe KPMG Canada Survey (1997The survey conducted by KPMG , Canada dealt with the reasons behind the collapse of the data technology formulatesAbout 61 of the hurls that were chthonian study were failed and main reasons for their collapse were exceeding the cypher , could not be established within their prison term accountFurther statistics reveal that altogether 16 .2 of software barfs that are hitd on sequence and within their budgetIt is common in IT externalizes the rate of unsuccessfulness is more credibly than the rate of successfulnessThus on that point exists more than angiotensin converting enzyme factor for the unsuccessful person of Information Technology Software ripening regorges . I adopt recognizing the reasons why a aggroup whitethorn fail on a labor go forth assist IT Professionals and light up counsel in averting the same mistakes from repeating , thus up(a) readiness and decreasing costII .AIMSThe aim of the is to specify the importance of victorious appropriate device leg before implementing an IT jut . This is be form legion(predicate) literatures reveal that or so IT Projects fails to deliver because of technical and non-technical issuesIII .OBJECTIVESThis answer for is to stripping out why IT expulsions fails to deliver although it has gone several stages of readying outgrowthUsing the non-participant method , collecting data and analyzing quantitative information from diary , books , magazines and other online materials , this is to list hook 10 reasons that cause IT Project implementation fails to deliver . For the purpose of this enquiry by survey findings were gathered from already performed case studyIn conveyition , the aims at discussing in more detail about the 10 reasons behind the failure of IT Project implementation .The top 10 reasons and strategies are as followsIV . REASONS FOR IT PROJECT FAILURESIV .1 . IT PROJECT IS LAUNCHED WITHOUT APPROBRIATE STRATEGYBefore launching a bug out , prim int sack and strategy should be chalked out for the implementation of the regorge . The business call for feel to be identified extrapolateably else the rove may not add any mensurate to the bottom line or boost the business processWise planning , high-octane jump out reserves are important legal instruments in planning and maneuver . A get a line with the poor asserts is a project that is out of control . The following project supervise scapes stooge be deployed by the project film director to have control over the project such(prenominal) as syllabus military rating and Review Technique (PERT / Critical rails Method (CPM ) Charts , Gantt Charts and option loading chartsThe techniques get out actually facilitate to conceive the versatile steps pick outd in the project before the implementation of the project and besides help to monitor during the sentence of organizing the project and at the time of its implementationIV . 2 . THE IT PROJECTS HAS UNCLEAR GOALS AND OBJECTIVESThe aim of a project may be partially clear imputable to a poor requirement gathering in the definition stage of a project . These are the projects where scope and plan of the project washstand not possibly be dead hence their objectives are ambiguous due to inability to go forth direct and honest feedback on the nearA project that declares something that is not used or is grossly underused is a failure even though the product may have been developed within the budget and on timeDuring the implementation of the project , the Project police squad up up and the node may differ on certain issues or the customer requests to change the romps inconsistently which have direct consequence on cost and schedule . Projects will be in paroxysm because of little definition of customer needs , poorly compose project specifications and mid point changes in the specifications will result in incremental cost and schedule overrunsIn fact , the major culprits behind these projects failures are poor needs recognition and inad study definition of requirementsCost and schedule over runs are common if there exist problems with the requirements . Project professionals are encountering not only overruns in cost and schedule only when overly dissatisfaction from customer .This may be avoided by working closely with the customer thereby appreciation(a) their exact needs and to develop exact running(a) requirements of the customer s wishIV .3 . OBJECTIVE CHANGES DURING IMPLEMENTATION OF THE PROJECTDuring the course of increment of software project , if invitee craves to change the software thereby to add some more functions or to change the requirement , this will have major impact and may result in failures The change may be warranted at times as technology changes frequently these daysFrequent changes in the project may be due to hea thenish gap between project team and their ever beging business clients . This mainly arises due to failure to see to it client s needs and demands overemphasizing on technical issues at the cost of customer demand and omit of client -oriented service cultureChanges may be warranted due to uncontrolled and unthought-of changes in drug user expectation and necessitate and inclusion of uncontrolled features to a agreement with a wrong assumption that one small feature will add nothing to outlay or agendaProject director s failure to recognize project trade-offs will end in not crafting decisions regarding objectives on the basis of rational insight . com committee only to the preliminary requirement will result in failure when the requirement of a project changes more than one timeIV .4 . THE PROJECT HAS UNREALISTIC TIME OR RESOURCE ESTIMATIONUnrealistic or wrong estimation of time or resource cause project related problems . Assumption of time on confinement equals duration is one of the ubiquitous tribulations during the construction of the work breakdown structure . The time on the chore is the time the confinement will take to finish without any disruptions , whereas the duration time is the time the actually take to complete including interruptions . Project managers are frequently committing the mistake of using the time on task to estimate schedule which results in failure of the projectThe theory of bi linear approximation can not be extended to the IT projects as in reality doubling or increasing the man power result only a non-linear resultThe Project private instructors should essay to adhere the budget for the project . If a project is funded through a contract , cost run may take away to litigation penalties and financial losses for the organisation .In case the project is funded internally , it may cause a drain in the finance of the companionshipThough the good planning and control guarantee the success of a project but their absence will sure enough result in failure to some extentProject managers are much in difficulty because they accept things at face shelter . Initially , the customers have only dimmed concept of their needs and project manager who proceeds on such vague concept later lands into trouble as the customer may reject the delivered as one which they have not asked forIV .5 THE PROJECT HAS NO ENOUGH SUPPORT FROM EXECUTIVETop Management of a company may be showing interest in monolithic project namely laid-back -visibility projects that are being undertaken . such(prenominal) Projects always have top management support and project managers are always supported for recruitment of staff , availability of infrastructure resources and also boost the project manager s standing within the organisation . It is to be remembered that a poor team structure is a formula for failure . Proper and keen structuring the project team may enhance the team s efficiency . The team efficiency may be referred as the particle of potential team performance that is actually achievedMajor structural resources of team inefficiency in projects are matrix -based friction , poor confabulation and poor integration of the efforts of team membersAnother cotton upback in highly visual projects is the meddling by the top management leading to micromanagement . entirely extrovert and efficient project manager can carry the second guessing of their effort by the organizational top brassIf top management is liberal and open , the project manager and his team will be honest in report successes and failures in a project with out any upkeep . If the top management crafts an environment where failure is not tolerated , the project manager and his team may be of less concerned in reporting failures because of the fear consciousThe examples of highly visible projects are the launching of the personal computer in the 1980 s by IBM and Steve melody s ongoing support of naked as a jaybird generation computers at AppleIV .6 . IT PROJECT DOES NOT TAKE INTO ACCOUNT INPUT FORM USERS OR CUSTOMERSDuring the developing of the project users may not available to go out explanation or feedback and hence the project manager has to course of action down the required information and to include it into the project . The Project managers are forced to cater to the caprice of a client s wish list at the last moment . most(prenominal) of the times , the project managers are forced to extend functionality . The project team by working for months together maps out , human bodys and codes a desired solution but later on consider that it lacks collateral functionalities without that the user won t accept the project and it turns out to a failureAn efficient project manager will exist how to pull together end users and get the graceful detail from them . An able project manager should know how to steer development in the direct route to poise efficient cryptogram and appropriate user request inclusionsIV .7 THE PROJECT FAILS TO SET UP COMMUNICATION AMONG TEAM MEMBERSImproper chat will lead to failure of the project Communication problem always exist in large software projectsThese include arbitrary work rules , micromanagement from the top ranks of the hierarchy , the inability to get the right people for the rent out haphazard budgeting etcBut these organizational factors are ubiquitous and not contain to a particular organization . For the successful implementation of the project , the project manager should have the ability to coordinate and confine the relevant project actors and their willingness to cooperate with project managerIV 8 . INAPPROPRIATE TECHNICAL CONSIDERATIONDue to stable change in technology , the blue-belly growth of knowledge and the challenge of global competition , it is concentrated to employ right kind of skilled employees as there is always scarcity for the skilled , well experienced technology expert in the marketA good project team should have a team spirit and they should have clear base of what the team is and to identify strongly with it . A team which fill with team spirit always wins . A dedicated team always brings success to the project and in case where a project borrows it team members that team may not produce the desired resultsA good project manager should be one who avoids pit falls before he lands in landmines causing to explode . Despite the fact that despite a project manager pushing right buttons and pulling right levers , the project performance was lackluster . Most of the project managers worry that they will be removed if they didn t improveIV .9 . RELYING ON OFF SHORING /OUTSOURCING THAT IS NOT COMPLIANCE WITH THE PROJECT OBJECTIVEMany Companies like GE , Bank of the States , Target , and American Express have to onshore contracts for underdeveloped software in other countries to save time and property . Without discipline in managing offshore relationships , a detailed recognizing of business process and the method IT supports them , a company can not only dissipate the cost and times savings it had estimated to increase through them but can also face counterpoise problems like late deliveries , mismatch between deliverables and expectations , incremental costs and even outright project failureThe Gartner Group Survey reports that because of high turnover - the average stay of a programmer in any one software job is only -11 months and IT companies drop more than 10 of their IT budgets for recruitment and imparting training to the new staffA company that outsource software development should not have tang for bleeding -edge technology since it demands high number of design -code test-redesign feedback loopsIV .10 .The project does not employ planning and attempt control across the project life cycleA project manager should plan for try mitigation which is followed by executing the plan and supervise the take a chance . Risk is probabilistic events and may change with time and periodical revisit the risk perception for the project is compulsory . Risk can be monitored by periodical report and reviews and by metric data to compare actual with plan and chivalric performance . The project should apply major components of risk management process are risk management , risk identification qualitative risk compendium , quantitative risk analysis and risk response planning . The planning and risk control techniques are used the project management life cycle which includes initiating , planning , executing controlling and closing . The project which ignores planning and risk control methods usually end in utter failureV . STRATEGIES TO OVERCOME IT PROJECTS FAILUREV .1 MAKE SURE THE IT PROJECT POSSESSES CLEAR AND MEASURABLE OBJECTIVESMeasurable objective means defining and refining objectives and employing the outperform alternative courses of action to accomplish the objectives that the project was undertaken to address . The project manager should ensure that project objectives are met by observe and measuring progress regularly to identify variances from plan so that remedial action can be initiated whenever necessaryV .2 EMPLOYS PROPER RISK MANAGEMENT TOOLS AND METHODSRisk Management administers and ensures the integrity of the project process . in that celebrate should be proper application of risk management tool of both economic and managerial nature . Economic tools include budgeting budget deviation analysis , periodic budget monitoring , continuous cost /benefit analysis and user chargeback implement .Under managerial tools , long range and short term planning , feasibility analysis software quality assurance , schedule monitoring , organizing project steering committee etcThis includes improper use of application tools or lack of appropriate application development tools or non availability of appropriate tools Software development tools , such as CASE tools , may be used .The lack of and the ineffective use of structured method and tools are other reasons for failureApplying lean manufacturing to software development in one technique for averting project failures . It encourages agility and responsiveness to customer demand resulting in increase in profitability where customer requirements are demanding and ever-changing . It is also additional advantage to employ able risk management tools and methodV .3 STRICT TO THE DETERMINED CONSTRAINTS OF COST , TIME AND QUALITYProject mangers wants to complete the project with in the accepted time and less than the cost what was estimated but impacting the quality .A software project with out quality by compromising time and cost is worthwhile to see itself accommodated at dustbin . Adequate trade offs with respect to time ,cost , scope and quality are the three inborn elements of any successful project managerV .4 PAY ATTENTION TO pagan DIVERSITY ISSUES IN CASE OF OFF SHORING IT PROJECT TO ANOTHER COUNTRYDep death upon the country that is targeted upon for off shoring , the impact of cultural adversity will vary . Nationality can become a factor while in decision making process or in the action of team members . Level of pinch and communication differs from country to country Failure in offshore management project mainly includes a cultural light touch as to bad management or personal shortcomings . In case of meetings and work as regards to project implementation , some nationals consider this as useful and some consider as a waste of time . Language barrier and communication also act as barriers in certain casesV .5 PAY ATTENTION TO CRITICAL TASKS DURING THE IMPLEMENTATIONAn appropriate project management tool can be used to progress to and maintain a network structure of tasks needed for the issue of the projectA user warm port wine method can be used to define tasks , define the precedence of these tasks and input their associated times to calculate the unfavourable path in a different of ways .
The team can easily create and modify task , create and modify precedence and solve the network for the optimistic , negative , likely or probable critical paths . Such interface will allow the team to analyse the effects of unexpected events that could change the aim or focus of the project . CPM (Critical Path Method ) technique can be used to describe the various stages of the project , schedule dates for completion of each stage of the projectV .6 ENSURE TO CONDUCT PLANNING BEFORE STARTING THE IMPLEMENTATION STAGEBusiness objectives precise details and processes will be determined enter for the prox reference .The project team should thoroughly understand the current and future business requirements and posses good communication skills to draw information from others in the organisation as well as provide feed back on the goals and progress of the project They should obtain the documentation of the existing system so that an close assessment of thework required for data conversions can be completed and any changes in timeline or resource requirements can be made to the proposed timelines resources and cost estimates . Documentation on interfaces and conversion shall also pursued by the teamV .7 OBTAIN THE SUPPORT FROM THE MANAGEMENTSupport throughout all hierarchy of top management confirms the company s allegiance to the project which will boost the motivation of the stakeholders of the project . The management should experience the value of the product , understand the problems it is going to solve and dedicates its supports and dynamism to making it happen by the project teamIf the management position is haphazard and the project team does not follow proper process system in the project implementation , then chances are failures are more . If top management does not extend its support for job training on a continuing basis , projects do failV .8 ALWAYS REPORT THE PROGRESS TO FIND OUT WHETHER THERE ARE OVERLOOK STEPSEven major IT companies often ignore the important steps needed to complete a project . The project team should have an in-depth perceptiveness of object-oriented systems and extensive project management experience . They should realize that the success of the project depends not only on the technology but also how well it is arranged and executed . Organizations often overlook or bypass the risk management process of project management and causes failure of the project . Before development of a project , a detailed needs analysis should be and most of the organisation always bypasses this strategy which leads to failure . For the successful implementation of the project , project manager should be very cautious that there is no overlook of any strategies and also to report periodically about thisV .9INVOLVE THE USERS IN DESIGN AND IMPLEMENTATION OF THE IT PROJECTTo ensure the success of the project , it is important to create a project team with varied skill sets and to engage the end user in the design and implementation of the project .The Project should be forged by working together on high impact team building exercises , culminating in a requirements session along with users to demand what they needed from a systemProject Manager should engage users throughout their design process so that they can create persuasive design solutions that are simple and self- begind to use and in tune with the user s requirements and expectationV .10 ENSURE THAT WE HAVE ENOUGH RESOURCE IN PLANNING , COMMUNICATION , AND TECHNOLOGY SKILLSSkilled and experienced software engineers are needed for successful completion of the high tech software projects . The Combination of strong commitment and good tools is the best mathematical solution , reducing dramatically the likelihood of all-too-frequent project failure caused by planning and control deficienciesThe Software Company should have on their rolls such efficient skilled engineers who have long standing track participate in the successful development of the software projectVI . CASE STUDYKPMG , an internationalist Accounting and Audit Company and Canada s largest professional services organisation , carried out a comprehensive study on failed software projects . Canada is spending an estimated 25 billion annually on IT development projects alone . The findings of KPMG in fact depict an alarming picture of projects mismanagement in both private and government sectorsThe study reveals the prime culprit is the schedule and cost over runs and secondary is project team inefficiency as the reasons for the failure of the software development projects in CanadaAnother example is the Federal Aviation Administration which cherished to a system to replace the antiquated air craft control system in U .S . The system , the in advance(p) Automation system took nearly 10 historic period for its development . The software was considered as undependable to trust for life and ending situation . It was also belated by six years . The project failed in part because of the failure in the software developmentAnother case study is the Silicon Graphics which released a software application with major bugs . The project schedule was impossible to be honored . The management as a corrective banknote employed at the fag end two international contractors who were new to the Company s software . It proves that by deploying more bodies at the end of a project do not equate to a condensed schedule to meet an unrealistic it has complicated the matters rather than finding a solution to the problemThe Thailand Government was forced to chafe its Bt 1 .8 billion IT project which was awarded to IBM (Thailand ) because of the startup and ever ending problems it faced during the software development stageVII . LIMITATIONSThe Method does not involve direct interviews , which will slightly reduce objectivity and trueness of information . We are utilizing the reliable data from books , expert s analysis , journals and various publications from available media . Using the data resources above , we are hoping to present an independent and objective analysis towards the contemporary issueVIII . CONCLUSIONThis research reveals valuable information for top management , IT application development teams and the IT industry in general . By studying the past mistakes , one can learn to avert the mistakes in the future . The risk of future failures can be avoided by understanding what not ought to pursued .Knowledge begets wisdom and wisdom may generate substantial cost savingsIf project managers adopt the following strategies , they can mitigate the failure of the projectsBefore implementation or development of a project , a through planning is essentialTask should be schedule according to their priorities and focus should be made to such tasks in the critical pathTo minimize the risk , appropriate process may be devised so that it can forewarn about the possible riskA software project without an unambiguous objective is like a gun without cartridges . Hence it is essential to have clear mission and objectives for success of a projectWhen making decisions on objective changes , project manager should recognize project trade-offsAs regards to estimation of schedule , project manager should use duration instead of the time on taskWhen estimating time or resources , try to avoid using linear approximationA prudent project manager should try to have support from the top management and be bold enough to tell them to be open if they have any reservation about the projectAssure that there is a regular communication about progress even in case of invisible progressTo avoid cost and time over run , involve end user s participation in design and implementationFor the success of a project ensure that the project team has the appropriate communication , technology skills and planningBIBILIOGRAPHY1 . Jack Cook , Victoria Semouchtchak Lean Object-Oriented Software Development , surface-to-air missile ripe Management Journal ,69 . Issue : 2 (2004 122 . Geoff Reiss , Program Management Demystified : Managing Multiple Projects Successfully , London , E FN Spon . 19963 . J . Davidson throw off , Managing Projects in Organizations : How to catch the Best Use of period , Techniques , and People , San Francisco Jossey-Bass . 20034 . Kaushik Bhaumik , Kishore Kanakamedala , Inigo Amoribieta , Ajay D Parkhe , Programmers Abroad : A Primer on Offshore Software Development The McKinsey Quarterly . 20015 . McConnell , Steve , Software projects excerption Guide , Redmond Washington , Microsoft Press (19986 . What Went Wrong ? Unsuccessful information technology projects , KPMG (October 31 , 1997 ) HYPERLINK http /kpmg .com http /kpmg .com (accessed 4th April , 2006Article deed of conveyance : Lean Object-Oriented Software Development . Contributors Jack Cook - reason , Victoria Semouchtchak - germ . Journal Title : SAM Advanced Management Journal . Volume : 69 . Issue : 2 . takings twelvemonth 2004 . Page Number : 12 . right of first publication 2004 Society for the Advancement of ManagementProgramme Management Demystified : Managing Multiple Projects Successfully . Contributors : Geoff Reiss - indite . Publisher : E FN Spon . Place of exit : London . Publication Year : 1996 . Page Number 243Book Title : Managing Projects in Organizations : How to Make the Best Use of Time , Techniques , and People . Contributors : J . Davidson Frame - author . Publisher : Jossey-Bass . Place of Publication : San Francisco Publication Year : 2003 . Page Number : 81Programmers Abroad : A Primer on Offshore Software Development Contributors : Inigo Amoribieta - author , Kaushik Bhaumik - author Kishore Kanakamedala - author , Ajay D . Parkhe - author . Journal Title The McKinsey Quarterly . Publication Year : 2001 . Page Number : 129KPMG (4th April , 2006 . What Went Wrong ? Unsuccessful information technology projects ( On -LineThe PROJECT PERFECT . White assemblage . 24 /10 /05 Www .projectperfect .com .au . Page 1 of 8 . Why IT Projects Fail . Al Neimat Taimour . Abstract http / web .projectperfect .com .au /info_it_projects_fail .phpPAGEPAGE 4Yourlastname ...If you want to get a full essay, order it on our website:
Ordercustompaper.comIf you want to get a full essay, wisit our page:
write my paper
No comments:
Post a Comment