Risk Assessment Quality Review Checklist

Project Name:
Project Number:
Prepared By: Date:
Risk Level
Risk Factors Criteria
Low Med High

PROJECT SIZE

5,000 or less
Man Hours for Project 5,001 20,000
Over 20,000
4 months or less
Calendar Time (Estimated) for Project 5- 12 months
Over 12 months
< 4 members
Team Size at Peak 5-15 members
> 15 members
1
Sites (Numbers of Locations Affected) 1-3
Over 3
0
Number of Interfaces Considered to
1-3
Existing System Affected by Project
Over 3
1
Organizations Affected by Project 2-4
Over 5

PROJECT DEFINITION

Well-defined
Project Scope Defined, but high-level
Vague
Well-defined
Project Deliverables Defined in name, not content
Not defined
Well-defined
Project Benefits Defined in general
Not defined or unclear
Clearly defined
Use Requirements Complexity Somewhat known, but complex
Vague and complex
Knowledgeable of IT & user areas
Responsible User Knowledge Knowledgeable of user area only
Lack adequate user knowledge
All
Business Knowledge of Team Half
None
Complete and current
More than 75% complete/current
Availability/Status of Documentation
Less than 75% complete, non-
existent or out-of-date
0
Dependence on Other Projects &
1
Development Efforts
2 or more
0
Dependence of Other Systems on This
1
Project
2 or more
Project Name:
Project Number:
Prepared By: Date:
Risk Level
Risk Factors Criteria
Low Med High
Completed documented/proven
Cost/Benefit Analysis of Estimates Approximations used
Estimates not documented/proven

SPONSORSHIP

Identified and enthusiastic

Project Sponsor
Commitment of User Management
Commitment of User Organization
Relation to Strategic Systems Plan
Corporate Management Commitment
Identified but passive
Unknown
Understands value and supports
Somewhat reluctant
Skeptical/resistant
Understands value and supports
Somewhat reluctant
Skeptical/resistant
Included or added with approval
Added, but not yet approved
Not yet part of strategy plan
Most understand value & support
Some understand value & support
Few understand value & support

EFFECT ON ORGANIZATION

Is new to IS
Replaces some subsystems
Conversion or New System
Complete conversion from old to
new subsystem
Little change
Effects on Computer Operations Moderate change
Severe change
Little change
Procedural Changes Imposed by New
Moderate change
System
Severe change
Little change
Changes to Organizational Structure to
Moderate change
Support New System
Severe change
None
Policy Changes Required Moderate changes
Extensive changes

PROJECT STAFFING

>3 projects of similar scope

Project Manager Experience Level
Full-time Project Manager
Full-Time Project Team
Experience as a Project Team
1-2 projects of similar scope
No prior projects of similar scope
Full-time
Full-time, minor duties elsewhere
Plus one or more projects
Full-time
Half of team full-time
Less than half of team full-time
All worked together before
Some worked together before
Team members are strangers
Project Name:
Project Number:
Prepared By: Date:
Risk Level
Risk Factors Criteria
Low Med High
More than once
Teams Experience with Implementing
Once
This Specific Application
No knowledge or experience
Team located together
Teams Physical Location Most of team located together
Team located at several sites
Full-time members
User Participation on Project Team Part-time members
No participation

PROJECT MANAGEMENT

Existing ISD SDM

Development Methodology Used
Change Management Procedures
Quality Management Procedures
Project Management Techniques and
Approach
Methodology new to team
No methodology
Well-defined
Established but unclear
Do not exist
Well-defined and accepted
Established but unclear
Do not exist
In use, accepted and proven
Techniques not accepted
Techniques not used

PROJECT HARDWARE/SOFTWARE

None
Requirements for New or Non-Standard
Existing plus additional
Hardware or System Software
All new
Guaranteed availability
Availability of Hardware for Development
Reasonable availability
and Testing
No assurance of availability

PROJECT DEVELOPMENT APPROACH

New Tools and Techniques Used by Team
New Language Required by Project
New Database Management System
Very familiar
Somewhat familiar
Used for the first time
No new languages
Somewhat new languages
New language(s), used 1st time
Well-established in organization
Established but new for application
New DBMS of organization
Project Name:
Project Number:
Prepared By: Date:
Risk Level
Risk Factors Criteria
Low Med High

SYSTEM COMPLEXITY

Batch processing only

Simple online query and update
Type of Processing Required
Complex processing used for 1st
time
>7 seconds 90% of time
System-Required Online Response Time 3-7 seconds 90% of time
<3 seconds 90% of time
95% at host
Requirements for System Availability 98% at host
Greater than 99% at host
1 or 2
Number of Different System-Required
3
Technologies
4 or more
Not complex
Level of Data Complexity Used by New
Moderately complex
System
Very complex
Simple to convert or good quality
Quality of Data for Conversion Process Average complexity or fair quality
Very complex or poor quality

SOFTWARE PACKAGE

Knowledge of Package to be Installed
ISDs Prior Work with Vendor
Functional Match to System
Requirements
ISD Involvement in Package Selection
Approved By:
Previous experience
Conceptual understanding
No knowledge or expertise
3 or more times
1 or 2 times
Never
Well (minimal customization req.)
Fairly well (mod. customization)
Not well (major customization
required)
High involvement in selection
Helped select from short list
Not involved
Date: