Risk Analysis Scoresheet
2232826.xls / Organization203/04/2008
Not obtaining consensus.Y = 0, N = 1Y = 10 N = 0Y = 5, N = 0Y = 2, N = 0Y = 0, N = 3Y = 2, N = 0Organizational Total0Low Risk
Number of user areas and decisionmakers?Equal to number of user areas / decisionmakers.Identify key representative. Establishdecision makingprocess/responsibilities.Multiple geographicallocations?Equal to number of geographical areasdivided by thenumber of implementation sitesTime to distribute deliverables andco-ordinate activities.Select a pilot implementation sitethen a phased implementation.Establish focal point for developmentactivities.Previous user ISproject experience?Unrealistic expectations. Lack of communication. Lack of knowledgeof roles and commitment.Schedule briefing and trainingsessions early in project. Increaseuser involvement/participation.Size of departmentsimpacted?< 200 = 0, 200-500= 1, 500-2000 = 3,> 2000 = 5(This is the number of people whosefunction will be changed as aconsequence of the new system)Complexity of requirements andpossibility of conflicts.Training requirements andimplementation logistics. Consider phased implementation if self-contained increments can beidentified. Plan implementation asearly as possible.Inappropriate level of sponsorship?When a problem arises, the sponsor may not have the authority, or perspective, to support the projectadequately.Extend project board to include amore appropriate sponsor.Key usersunavailable?Lack of understanding of requirements. Lack of involvementof users in production of deliverableswith a consequential lack of commitment to project.Use techniques which are lessdependent on user input, e.g.,relational data analysis rather thandata modeling. Use user representative on Project Board to"encourage" user participation.Extend review activities.Organizationalchanges required (interms of structure /responsibility)?Resistance to system byorganization.Hold briefings throughout project onwhat the repercussions will be.Increase user involvement. Obtaintop management commitment.Level of changesrequired to user procedures?High = 3, Moderate= 2, Low = 1Users inadequately prepared for asuccessful implementation andhandover.Increase level of user training, use of prototypes and presentations of thenew procedures, both system andAre users duallyinvolved in themanagement andexecution of theproject?Lack of commitment to assuringquality of technical deliverables andto plan.Increase user participation in thetechnical activities by use of JAD,and the interactive sessions, togather information and createmodels. Determine user roles in theproject organization (Project Board,Project Coordinators).Will extensiveeducation berequired to facilitateuse of the system?Inadequate budget and time framefor training.Include prior walkthrough of thetraining sessions and materials togain commitment from user management.