GLENAH A.

TAGUIBAO RISK FACTOR MANAGEMENT STRATEGIES Derive traceability information to assess requirements change impact, maximize information hiding in the design. Prepare a briefing document for the senior management showing hoe the project is making a very important contribution to the goals of the business. Investigate the possibility of buying a higher performance database. Investigate buying in components, investigate use of a program generator. Prepare a briefing document for senior management showing how the project is making a very important contribution to the goals of the business. Alert customer of potential difficulties and the possibility of delays, investigate buying-in components. Reorganize team so that there is more overlap of work and people therefore understand each others jobs. Replace potentially defective components of known reliability. Establish clear procedures for storage and disposal of electronic records and media. Regularly update antivirus, malware, firewall program and test security systems regularly. Be acutely aware of your current competencies in IT and seek CE for deficits. Ensure the plan has contingency built into it to allow for less than expected resource availability.

RISK FACTORS Requirements changes

Organizational restructuring

Database performance Underestimated development time Organizational financial problems

Recruitment problems Staff illness

Defective components Hardware and Software

Continuing education Team members leave or become sick

Key team member becomes available

Solution does not meet the business needs.

Insufficient participation from the business units and users

Significant change in the business and its consequent needs (eg restructuring, mergers etc)

Technical solution has major flaws

Technical solution has operational flaws

System failures

Hardware, network or system sizings inadequate to meet live demands.

Ensure project procedures include good knowledge sharing and documentation so that the thought process, designs and decisions are not lost. Ensure good participation and collaboration involving representatives and resources from all concerned areas of the business (and external parties where appropriate). Ensure the Project Sponsor and supporting sponsors are aware of the importance of promoting and rewarding participation. Agree how they will convey that message. Business needs frequently change, so plan the project so that it could adjust rapidly at relatively low cost, for example, a number of short incremental steps towards the goal could be easier and cheaper to redirect than one enormously long delivery project. Invest in appropriate levels of testing. Consider a period of parallel running. Have a fallback contingency plan to revert to a previous system if necessary. Put in place an "early care" program to deal with immediate snags. Ensure processes, resources and responsibilities for on-going maintenance are established well before live date. Invest now in fault tolerant components and adequate redundant contingency resources. Ensure the plan includes appropriate backup, recovery, and disaster recovery procedures (and tests them). Sizing calculations are always difficult. Many successful eSolutions have been swamped by demand.

Users fail to use the new system effectively and efficiently

Users resist the changes

Make sure the systems you use can be scaled up by a significant factor before any need to move to a different technological platform. Plan for a detailed Training Needs Analysis and put in place an appropriate training program. Consider how to coach and support users after live date. Use change management experts to assess the issues and create a change program. Co-ordinate communications and sponsorship activities to convey the message. Confront big issues early in the project (not just before live operation).

QUALITY ASSURANCE PLAN DESCRIPTION Equates quality with the fulfillment of a specification or stated outcomes. Sees quality as fulfilling a customers requirements, needs or desires. A method or technique that has consistently shown results superior to those achieved with other means, and that is used as a benchmark. Used to maintain quality as an alternative to mandatory legislated standards and can be based on selfassessment or benchmarking. Following specific specification requirements. The ease of use and learnability of a human-made object. The quality of being accessible, or of admitting approach; receptibility

CRITERIA Fitness for purpose

Best practice for purposes

Adherence to a specific standard or specification Usability Accessibility

Validity Accuracy

Timely Reliability Predictions of failures

Producing the desired results; efficacious: The state of being accurate; freedom from mistakes, this exemption arising from carefulness; exact conformity to truth, or to a rule or model; precision; exactness; nicety; correctness; as, the value of testimony depends on its accuracy Done or happening at the appropriate or proper time The quality of being dependable or reliable Tells about something in advance of its occurrence by means of special knowledge or inference