Core Systems Framework
2. Preview Business Decisions

Impact Analysis Checklist for Requirements Changes

Download Impact Analysis in Word Format

Predecessor to this tool?
Enterprise Opportunity Assessment

Note: This tool assumes the agency is intending to "do something" as an alternative to address their "System Trends and Alerts" and/or "Requirements Profile." If the agency is leaning towards or chooses "do nothing" as an alternative, please click on the following link for the tool that addresses those impacts. Go to "Impact Analysis Checklist For 'Doing Nothing' As An Alternative"

Intended audience:
Agencies (for potential use and discussion with MOSTD Consultant and ISB Core Systems Sub-Committee)

Who fills this out?
Agency I.T. and Business Managers

Purpose of this tool
This impact analysis helps agencies, MOSTD staff and the ISB surface the critical business and technical issues that impact the feasibility of a core system project. It is intended to help summarize your overall "first-take" speculative assessment at this point in time.

Both business and technical leaders should use this impact analysis to surface the important issues of your Core System. The agency and the ISB Core Systems Sub Committee should discuss these issues at a high level as they review the project's business justification at Decision Point two. These issues are used and analyzed in detail later when developing the feasibility study.

• Please attach your "Requirements Profile" tool to provide context for this analysis:
  
  
• Please assess how the issues below may impact the risk, scope, schedule or budget of your potential core systems project (driven by your "Requirements Profile"), by checking the appropriate box. When assessing, consider what a low, medium, significant impact would be within your agency.

NOTE: Some areas may be unknown at this point.

Core System Issue	No Impact	Low Impact	Medium Impact	Significant Impact	Not Applicable
Organizational
Internal I.T. Resources
Internal Business Resources
Staffing Availability
Having to backfill positions
Stakeholder's Input on Requirements
Staff knowledge of the Technical Requirements
Training Internal Agency Staff
Training Other External Stakeholders or Users
Communications Plan & Communicating
Contracts
EXISTING Maintenance Contracts
NEW Maintenance Contracts
EXISTING Development Contracts
NEW Development Contracts
EXISTING Consulting Contracts
NEW Consulting Contracts
External Related
Level of need for external / contracted I.T. resources
Level of need for NEW software (third party)
Integrate third party software
Technical
Existing software
Licensing Issues (Backup S/W)
EXISTING hardware
NEW hardware
Hardware and software scalability
Impact to EXISTING Security
Modification of EXISTING network(s)
Existing Agency Architecture (data models, arch. Models etc.)
Existing Agency Infrastructure (overall H/W, networks, etc.)
Support level for NEW requirement(s)
Developing NEW User Interface components
Modifying EXISTING User Interface components
Developing NEW Business Process Conversion & Business Process change
Modifying EXISTING Business Process Conversion & Business Process change
Developing NEW user publications and help screens
Developing NEW source code
Modifying EXISTING source code
Growth of code complexity
Developing and evaluating a prototype. (Or, other user input required to verify the proposed change.)
Develop NEW reports
Modify EXISTING reports
Develop NEW database elements
Modify EXISTING database elements
Extent of Data Conversion
Degree of rework following reviews and testing
Impact of running parallel operations before cutover
Financial
Financial impact of Core System's change to customers / end-users
Financial challenge / impact of Core System's change to Agency
Project-Related
Impact on the agency's project management operations or project office
Level of need for or impact to multi-agency Steering Committee
Impact on agency's Quality Assurance Plan, software configuration management plan, or other plans
Cutover (System, Technical) efforts
Configuration Management (CM) efforts
Rollout Plan
Placing unacceptable demands on any computer resources required for the development, test, or host environments
Affect performance requirements or other quality attributes
Affect support for some of the existing services

• What is a summary of the impact if the "Requirement(s)" are not implemented or done (doing nothing)? (Examples: Further degradation, slower response times, increased backlog of "critical" issues.)

   

   

• What are the possible adverse side effects of implementing the new requirement(s) or proposed change(s)?

   

   

• Briefly summarize the projected tangible and intangible benefits of your Core System project:

   

   

• Complete this sentence by checking the appropriate box.

“The Agency's...	Low	Medium	High	Significant
overall prioritization of the new requirement(s) is / are...”
estimate of overall Benefits are...”
estimate of overall Risk is...”
estimate of overall Cost is...”

Next Steps?

• Results from this completed "Impact Analysis" help with decisions to be made with the "Alternatives" and the "Business Justification Outline."