CASE-Risk-Analysis-for-PI by akgame

VIEWS: 46 PAGES: 6

CASE-Risk-Analysis-for-PI

More Info
									Risk Analysis Scoresheet
External Dependency Factor
Multiple vendors / contractors?

Value

Scor Problem e
0 Coordination.

Counter Measure

Y = 2, N = 0

Ensure adherence to standards, both technical and managerial. Emphasize the importance of regular status reporting.

Poor vendor support?

Y = 1, N = 0

0 Time wasted waiting for response to queries or due to rework arising from mistaken assumptions made by the project team in the interim. 2

Critical dependence on Y = 2, N = 0 external suppliers?

Number of inter< 3 = 0, 3-5 = 3, > 5 = project dependencies? 5

0

Overlapping scope with Y = 3, N = 0 other projects?

0

Contradicts LRSP Y = 10, N = 0 direction? Plan requires extensive Y = 2, N = 0 recruitment of resources?

0 0

External Dependency Total

2

Impose contractual constraints/safeguards. Request documentation in advance. Ensure effective account manager. Identify a user group with other clients. May miss milestones waiting for Ensure suppliers are aware of schedule deliverables. commitment. Request interim status reports and review of partially complete deliverables so that the project team can verify the supplier's estimates of the effort to go. Impose contractual obligations. Time wasted awaiting completion of Have a co-ordination project with the other projects not within the stage critical path specified in terms of manager's control. projects. Recommend a strategic / architectural plan is produced. Parallel, or duplicate, development of Establish cross-project standards to similar areas with different approaches ensure consistency. Establish change causing confusion and irritation to the control procedures to manage the user. different changes proposed by different systems. Recommend a strategic/architectural plan is produced. Project initiated for no justifiable reason, Ensure Project Board and Strategy e.g., political. Committee are aware of the situation. Time and expense Investigate training current resources. Plan gradual take on to allow for familiarization and training. Investigate viability of using short term experienced contractors. Low Risk

Organizational Factor
Number of user areas and decision makers? Multiple geographical locations? Equal to number of user areas / decision makers. Equal to number of geographical areas divided by the number of implementation sites 3 Not obtaining consensus. Identify key representative. Establish decision making process/responsibilities. Select a pilot implementation site then a phased implementation. Establish focal point for development activities.

1 Time to distribute deliverables and coordinate activities.

bf4bc93e-e462-4c73-8d53-00d708346c85.XLS

1

11/27/2009

Risk Analysis Scoresheet
Previous user IS project experience? Size of departments impacted? Y = 0, N = 1 0 Unrealistic expectations. Lack of communication. Lack of knowledge of roles and commitment. 0 (This is the number of people whose function will be changed as a consequence of the new system) Complexity of requirements and possibility of conflicts. Schedule briefing and training sessions early in project. Increase user involvement/participation. Training requirements and implementation logistics. Consider phased implementation if self-contained increments can be identified. Plan implementation as early as possible.

< 200 = 0, 200-500 = 1, 500-2000 = 3, > 2000 = 5

Inappropriate level of sponsorship?

Y = 10 N = 0

0 When a problem arises, the sponsor may Extend project board to include a more not have the authority, or perspective, to appropriate sponsor. support the project adequately. 0 Lack of understanding of requirements. Lack of involvement of users in production of deliverables with a consequential lack of commitment to project. 2 Use techniques which are less dependent on user input, e.g., relational data analysis rather than data modeling. Use user representative on Project Board to "encourage" user participation. Extend review activities. Resistance to system by organization. Hold briefings throughout project on what the repercussions will be. Increase user involvement. Obtain top management commitment. Users inadequately prepared for a Increase level of user training, use of successful implementation and handover. prototypes and presentations of the new procedures, both system and manual. Lack of commitment to assuring quality Increase user participation in the of technical deliverables and to plan. technical activities by use of JAD, and the interactive sessions, to gather information and create models. Determine user roles in the project organization (Project Board, Project Coordinators). Inadequate budget and time frame for Include prior walkthrough of the training training. sessions and materials to gain commitment from user management.

Key users unavailable? Y = 5, N = 0

Organizational changes required (in terms of structure / responsibility)? Level of changes required to user procedures? Are users dually involved in the management and execution of the project?

Y = 2, N = 0

High = 3, Moderate = 2, Low = 1 Y = 0, N = 3

3

0

Will extensive education be required to facilitate use of the system? Organizational Total

Y = 2, N = 0

2

11 Moderate Risk

Planning Factor
Dependent on scarce Y = 5, N = 0 resources / skills? Complex task Y = 3, N = 0 dependencies? Critical implementation Y = 5, N = 0 date? 5 Competition for resources or personnel with appropriate skills. 0 Critical dependencies unknown, increased chance of slippage. 0 May have to cut back on quality and/or functionality, or project discarded if date missed. Make resource requirements known as early as possible. Increase level of planning. Tighten project control. Verify significance of date. Ascertain which portions of system are required for that date. Consider incremental development. Plan and control at detailed level.

bf4bc93e-e462-4c73-8d53-00d708346c85.XLS

2

11/27/2009

Risk Analysis Scoresheet
Informal control procedures? Effort versus elapsed time? Y = 5, N = 0 0 Inaccurate Project Status information. Encourage take on of formal controls by training and provision of project management software. Increase control procedures and introduce additional level of management. Divide into achievable subsystems. Have a co-ordination project. Establish overall architectural plan. Minimize project interdependencies. Increase the number or control points. Increase the number or control points.

Effort time/Elapsed time

Number of major subsystems?

< 3 = 1, >= 3 = 3

2 The greater this ratio, the greater the number of simultaneous tasks. Increased staff associated with development and associated overheads. 1 Managing Interfaces.

Subsystem more than 3 Y = 2, N = 0 elapsed years? Subsystem more than Y = 2 N = 0 12 elapsed months? Level of confidence? >85% = 1, <85% = 3

0 0 Increased chance of slippage due to possible changes in requirements or scope over longer elapsed time. 1 Level of planning experience of unknowns within the plan may make estimates low. 0 No commitment to plan, unachievable date.

Ensure management tolerances and contingencies are identified. Verify significance and justification for dates. Produce a plan.

Key dates set by project team from the plan? Experience of project manager? Planned resources available? Planning Factor Total

Y = 0, N = 3

High = 0, Moderate = 1, Low = 3, None allocated = 4 Y = 0, N = 5

0 Plans may not exist. Control procedures Provide training and support from may not be adequate. experienced project manager. Increase involvement by Project Board. 5 New plan will be required to fit with maximum resource constraint or project could be canceled/postponed. 14 Low Risk

Business Case Factor
Major increase in costs Y = 3, N = 0 possible? Evolving business requirements? Incomplete definition of scope / requirements? Ill-defined benefits? Y = 5, N = 0 0 If greater than +/-5%, then likely to miss Set appropriate tolerance levels. stage end targets. Investigate mechanisms for further controlling costs. 3 Do not know where project should be Use iterative development approach. heading, difficulty in justification, Establish detailed scoping study. significant rework likely. Increase user involvement. 1 Cannot estimate effort as a lot of rework Involve more senior user representatives. is likely. Establish detailed scoping study. Increase time spent in analysis. 2 Difficult to select optional solution, potential for project being canceled. 2 May never achieve pay-back. Use CRA to help define tangible benefits. Establish focused sessions with user to evaluate benefits. Reduce scope of system to include most profitable segments.

Y = 5, N = 0

Y=2, N=0

Lead time for return on Twice development investment time = 2, Five times or more the development time = 5 Mission critical Y = 5, N = 0 system?

0 Business may fail if project fails.

Increase planning and level of control.

bf4bc93e-e462-4c73-8d53-00d708346c85.XLS

3

11/27/2009

Risk Analysis Scoresheet
Fundamental to IS strategy? Business commitment to development? Business Case Total Y = 5, N = 0 High = 1, Low = 3 5 Foundation system impacting other developments. 1 System perceived as belonging to I.S. department. 14 High Risk Increase planning and level of control. Hold assessments requiring user sign-off. Increase user involvement. Produce detailed Business Case.

Technical (Environment) Factor
Inappropriate development tools? New / unfamiliar technology? Stable development team? Low team knowledge of business area? Project team skills? Y = 2, N = 0 0 Required tools unavailable. Review tools and associated justification. Evaluate other productivity areas. Conduct training. Recruit experienced staff. Obtain vendor support. Document in standard format as project progresses. Increase attendance at reviews to spread knowledge. Increased user participation. Increase frequency and formality of reviews. Increase the frequency of Quality Assurance Reviews and Project Checkpoints. Include experienced staff as specialized technical support. Account for experience levels when planning. Implement a standard approach to development, ensure staff familiarity.

Y = 5, N = 0 Y = 0, N = 5

5 Time required for learning curve during development. 0 Lost information. Time required for handover. 0 Increased reliance on users. 1 If the balance of expertise is low, then there is an increased risk of defects.

Y = 1, N = 0 Expert = 0, Balanced = 1, Trainee = 5.

Use of development method / standards?

Y = 0, N = 2

0 Project team does not know what to do. Tasks may be duplicated or omitted.

Technical (Project) Factor
Complexity of functions? Complexity of database? Low = 0, Moderate = 2, High = 5 Low = 0, Moderate = 2, High = 5 2 Increased risk of defects. Increase effort in Logical Design to validate. Increase level of reviews. Use formal techniques. Increase data validation steps throughout. Ensure thorough Physical Design Tuning. Increase DBA involvement.

2 Performance problems.

Database to be shared by a number of applications? Number of physical system interfaces?

Y = 3, N = 0

3 Difficult to tune successfully in Physical Attempt to establish overall volumes and Design. requirements. Keep design flexible. 0 Increase risks of systems failure. Increase time in defining interfaces in detail. Involve experts from associated systems. Increase user involvement.

< 3 = 0, >= 3 = 3.

Clearly specified Y = 0, N = 3 requirements? Number of design 0-25% = 0, 25-60% = decisions at discretion 3, 60%+ = 5 of systems architect (no user involvement)?

0 Rework may be necessary as systems may not meet users' needs. 0 Rework may be necessary as system may Increase user involvement. not meet user's needs

bf4bc93e-e462-4c73-8d53-00d708346c85.XLS

4

11/27/2009

Risk Analysis Scoresheet
Is a package solution available? If using a package, was the package evaluated and selected, based upon detailed specifications and requirements? If using a package, were package changes required? Complex on-line networks? Multi-level hardware requirement? Y = 0, N = 3 Y =0, N = 3 0 Effort required in design, construction and testing. 2 Mismatch likely. Ensure buy/build option is appropriately conducted. Carry out evaluation if cost justified.

0-5% = 0, 5-15% = 3, over 15% = 5 Y = 2, N = 0

Y = 2, N = 0

0 Required information may be difficult to Contract vendor to do changes. Evaluate obtain, or not supported. alternative solutions. Minimize changes to front/back ends. 2 Increased risk of technical problems Add activities to prototype the on-line (incompatibility, etc.) architecture. Involve technical experts in physical design stage. 2 Interfaces, data distribution. Separate technical feasibility project started early. Ensure availability of required skills.

Technical (Operational) Factor
Upward compatible hardware? Y = 0, N = 3 0 Hardware constraints will increase problems in physical design and implementation. 0 Tight timing constraints will increase problems in physical design and construction. 0 Tight timing constraints will increase problems in physical design and construction. 0 Tight timing constraints will increase problems in physical design and construction. 0 Tighter performance constraints will increase problems in physical design and construction. 0 Performance and storage constraints will increase problems in physical design and construction. Increase time scheduled for physical design and construction stages. Involve technical experts in physical design stage. Increase time scheduled for physical design and construction stages. Involve technical experts in physical design stage. Increase time scheduled for physical design and construction stages. Involve technical experts in physical design stage. Increase time scheduled for physical design and construction stages. Involve technical experts in physical design stage. Increase time scheduled for physical design and construction stages. Involve technical experts in physical design stage. Increase time scheduled for designing the database and for storage and performance predictions. Involve technical experts in physical design stage. Increase time scheduled for physical design and construction stages. Involve technical experts in physical design stage.

24 hour availability?

Y = 3, N = 0

Rapid response time (below 2 seconds) ?

Y = 3, N = 0

Small batch window?

Y = 3, N = 0

High-volume throughput?

Y = 3, N = 0

Very large database?

Y = 3, N = 0

Short recovery cycle?

Y = 3, N = 0

3 Tighter recovery constraints will increase problems in physical design and construction. 22 Moderate Risk

Technical Total

bf4bc93e-e462-4c73-8d53-00d708346c85.XLS

5

11/27/2009

Risk Analysis Scoresheet
63 Moderate Risk

Overall Project Total

bf4bc93e-e462-4c73-8d53-00d708346c85.XLS

6

11/27/2009


								
To top