UNDERSTANDING THE BUSINESS VALUE OF SYSTEMS AND MANAGING CHANGE

Slides:



Advertisements
Similar presentations
Project Management.
Advertisements

Information Systems: the Foundation of E-Business (CIS 108) Exploring the business of value of IS and Managing Change Lecture NINE (14 th March 2005)
Capital Budgeting.
MANAGEMENT OF INFORMATION SYSTEM PROJECT AND IMPLEMENTATION
MANAGERIAL ACCOUNTING
B280F Introduction to Financial Management
SESSION 13 UNDERSTANDING THE BUSINESS VALUE OF SYSTEMS
Chapter 3 Program Management and Project Evaluation Professor Hossein Saiedian McGraw-Hill Education ISBN
Introduction to Systems Development and Systems Analysis
1 Management Information Systems - Class Note # 5 (Chap-13) Prof. Yuan-Shyi Peter Chiu Feb
4. Project Investment Decision-Making
Moving from Analysis to Design
Essentials of Management Information Systems, 6e Chapter 14 Understanding the Business Value of Systems and Managing Change Chapter 14 Understanding the.
15.1 © 2006 by Prentice Hall 15 Chapter Understanding the Business Value of Systems and Managing Change.
Understanding the Business Value of Systems and Managing Change
13.1 © 2004 by Prentice Hall Management Information Systems 8/e Chapter 13 Understanding the Business Value of Systems and Managing Change 13 UNDERSTANDING.
IT ARCHITECTURE © Holmes Miller BUILDING METAPHOR 3CUSTOMER’S CONCERN Has vision about building that will meet needs and desires 3ARCHITECT’S CONCERN.
14.1 © 2007 by Prentice Hall 14 Chapter Project Management: Establishing the Business Value of Systems and Managing Change.
Redesigning the Organization with Information System
IS 425 Enterprise Information I LECTURE 9 Autumn  2004 Norma Sutcliffe.
IT Planning.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
The Analyst as a Project Manager
Financial and Managerial Accounting
FDM9 Capital investment appraisal 1 Capital investment appraisal 1.
PROJECT EVALUATION. Introduction Evaluation  comparing a proposed project with alternatives and deciding whether to proceed with it Normally carried.
Week 8: IT Portfolio Management MIS5001: Management Information Systems David S. McGettigan Adapted from material by Arnold Kurtz, David Schuff, and Paul.
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 16-1 Accounting Information Systems 9 th Edition Marshall.
Managing Projects
Chapter 3 – Opportunity Cost of Capital and Capital Budgeting
Introduction ► This slide deck provides a suggested framework for the financial evaluation of an investment project. When evaluating any such project,
Scis.regis.edu ● CIS 480/BA 479: Managing Technology for Business Strategies Week 5 Dr. Jesús Borrego Regis University 1.
Capital Budgeting
Chapter 14 Managing Projects.
Pertemuan © 2008 by Abdul Hayat Business Value of Systems and Managing Change MANAGING CHANGE Pertemuan 13.
DR. IBRAHEM AL-EZZEE-FIN421CHAPTER1 1 Chapter 1 Long-Term Investing and Financial Decisions.
Module 4: Systems Development Chapter 12: (IS) Project Management.
1 Setting Goals, Securing Commitment and Project Justification Project Charter & Business Case Kathy S. Schwaig.
11.1 Prof Jess UEAB 2010Prof Jess UEAB UNDERSTANDING THE BUSINESS VALUE OF SYSTEMS AND MANAGING CHANGE.
14.1 © 2010 by Prentice Hall 14 Chapter Managing Projects.
1 Understanding the Business Value of IS (supplement to Ch. 14) Kat Schwaig.
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 8 Moving from Analysis to Design.
3 1 Project Success Factors u Project management important for success of system development project u 2000 Standish Group Study l Only 28% of system development.
McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, Inc., All Rights Reserved. 1-1 McGraw-Hill/Irwin © 2008 The McGraw-Hill Companies, Inc., All Rights.
Lecture 4. IS Planning & Acquisition To be covered: To be covered: – IS planning and its importance Cost-benefit analysis Cost-benefit analysis Funding.
14 Chapter Managing Projects. Runaway projects and system failure Runaway projects: 30-40% IT projects Exceed schedule, budget Fail to perform as specified.
Chapter 8 Capital Asset Selection and Capital Budgeting.
Software Project Management
1.Upgrade bandwidth 2.Upgrade desktop operating systems 3.Increase the number of servers 4.Determine industry standards 5.Convert to VoIP Which of the.
Project Management Part 1 Projects and Project Goals.
Business Case Ganesh Botcha, Ajoy Chatterjee 16 Nov ’15, Monday.
Monitoring the Business + - x ÷ ÷ x x ÷ : : : : Ratio Analysis C. O' Brien Chanel College.
Capital Budgeting Tools and Technique. What is Capital Budgeting In “Capital budgeting” capital relates to the total funds employs in an enterprise as.
14-1 Copyright © 2013 Pearson Canada Inc. Project Management, Business Value, and Managing Change Oleh : Kundang K Juman Project Management, Business Value,
Information Systems Week 14 Managing Projects.
Pertemuan © 2008 by Abdul Hayat Business Value of Systems BUSINESS VALUE OF SYSTEMS Pertemuan 12.
14.1 © 2010 by Prentice Hall Managing Projects © 2010 by Prentice Hall LEARNING OBJECTIVES Identify and describe the objectives of project management.
The Information Systems Development Processes Chapter 9.
6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice Hall Managing Projects Chapter 14 VIDEO Video Case 1: Blue Cross Blue Shield: Smarter.
Project Evaluation and Programme Management
Factors to consider System component costs Methods
Understanding the Business Value of Systems and Managing Change
Systems Analysis and Design in a Changing World, 4th Edition
Understanding the Business Value of Systems and Managing Change
UNDERSTANDING THE BUSINESS VALUE OF SYSTEMS AND MANAGING CHANGE
Building Information Systems
Introduction to Information Systems
Introduction to Projects
Cost/Benefit Analysis Pertemuan 13-14
Presentation transcript:

UNDERSTANDING THE BUSINESS VALUE OF SYSTEMS AND MANAGING CHANGE 15 UNDERSTANDING THE BUSINESS VALUE OF SYSTEMS AND MANAGING CHANGE

LEARNING OBJECTIVES EVALUATE MODELS DETERMINING BUSINESS VALUE OF INFORMATION SYSTEMS ANALYZE PRINCIPAL CAUSES OF INFORMATION SYSTEM FAILURE ANALYZE REQUIREMENTS FOR BUILDING SUCCESSFUL SYSTEMS SELECT STRATEGIES TO MANAGE SYSTEM IMPLEMENTATION

Challenges Not Tangible Determining benefits of information systems Dealing with the complexity of large scale implementations Large organization, wide area Many staff members, users requirements Technology choices, making a decision Political impact, manager bias

UNDERSTANDING BUSINESS VALUE OF INFO SYSTEMS Does a particular IS investment produce sufficient returns to justify its costs? Three approaches: CAPITAL BUDGETING MODELS PORTFOLIO ANALYSIS REAL OPTIONS PRICING MODEL (Skip this one)

Capitol Budget Cash flow in and out of the firm is the basis. Several methods are can be used to justify IS technology within Capital Budget. Process for analyzing and selecting various proposals for capital expenditures. Cash flow in and out of the firm is the basis. PAYBACK METHOD: How long will it take to pay back the investment? Org inv / annual net cash inflow = # years

Capitol Budget Net ben / total initial invest = ROI RETURN ON INVESTMENT: Does return during useful life of an item exceed the cost to borrow money? (Total ben – cost – depriciation) / useful life = net Ben Net ben / total initial invest = ROI COST-BENEFIT RATIO: Does the ratio of benefit versus cost exceed 1? Total ben / total cost = cost-ben ratio

Capitol Budget PROFITABILITY INDEX: What is the ratio of present value of cash inflow to initial investment? NET PRESENT VALUE: Accounting for cost, earnings & time value of money what is the investment worth? INTERNAL RATE OF RETURN: Accounting for the time value of money, what is the return rate of an investment?

Costs COSTS: HARDWARE SOFTWARE SERVICES PERSONNEL

Benefits TANGIBLE BENEFIT: INCREASED PRODUCTIVITY LOW OPERATING COSTS REDUCED WORK FORCE LOWER COMPUTER EXPENSES LOWER VENDOR COSTS LOWER CLERICAL/PROFESSIONAL COSTS REDUCED GROWTH OF EXPENSES REDUCED FACILITY COSTS

More Benifits INTANGIBLE BENEFIT: IMPROVED ASSET USE; RESOURCE CONTROL; PLANNING INCREASED FLEXIBILITY MORE TIMELY INFORMATION INCREASED LEARNING ATTAIN LEGAL REQUIREMENTS ENHANCED EMPLOYEE GOODWILL, JOB SATISFACTION, DECISION MAKING, OPERATIONS HIGHER CLIENT SATISFACTION BETTER CORPORATE IMAGE

CAPITAL BUDGETING MODELS LIMITATIONS: Assume all relevant alternatives have been examined; cost & benefits can be expressed as $$ Ignores intangible benefits Cost are usually up front and tangible Benefits are usually back loaded and intangible.

PORTFOLIO ANALYSIS: ANALYSIS OF POTENTIAL APPLICATIONS TO DETERMINE RISKS & BENEFITS DETERMINE DESIRABLE FEATURES, ACCEPTABLE RISKS OF REQUIRED SYSTEM GENERATE PORTFOLIO OF CHARACTERISTICS, RISKS FOR EACH ALTERNATIVE Usually a SCORING MODEL is used. Sometime is it more just a matter of group consensus on priorities benefit versus risk

Risk Matrix Scoring Project Risk High Low Cautiously Examine Identify and Develop High Potential Benifit Avoid Routine Projects Low

Typical Scoring Model IDENTIFY DESIRABLE FEATURES Totals TO 1.00 PROVIDE WEIGHTS FOR EACH Totals TO 1.00 LOOK AT EACH ALTERNATIVE: WHICH FEATURES ARE PRESENT? TO WHAT EXTENT (as an amount)? SCORE THE ALTERNATIVE 1-5highest RANK-ORDER THE ALTERNATIVES SELECT HIGHEST RANKED OPTION

Change Management Causes of implementation failure: DESIGN DATA COST OPERATIONS

Change Agent DURING IMPLEMENTATION, INDIVIDUAL ACTS AS CATALYST DURING CHANGE PROCESS TO ENSURE SUCCESS

FACTORS IN IMPLEMENTATION OUTCOME CAUSES OF SUCCESS OR FAILURE: USER INVOLVEMENT & INFLUENCE MANAGEMENT SUPPORT LEVEL OF COMPLEXITY / RISK MANAGEMENT OF IMPLEMENTATION PROCESS

User Designer Gap DIFFERENCES IN BACKGROUNDS, INTERESTS, PRIORITIES IMPEDE COMMUNICATION AND PROBLEM SOLVING AMONG END USERS AND INFORMATION SYSTEMS SPECIALISTS

User Concerns WILL SYSTEM DELIVER INFORMATION I NEED? HOW QUICKLY CAN I ACCESS DATA? HOW EASILY CAN I RECEIVE DATA? HOW MUCH CLERICAL SUPPORT WILL I NEED FOR DATA ENTRY? HOW WILL SYSTEM OPERATION FIT INTO MY DAILY BUSINESS SCHEDULE?

Designer Concerns HOW MUCH DISK SPACE WILL MASTER FILE CONSUME? HOW MANY LINES OF PROGRAM CODE WILL THIS FUNCTION TAKE? HOW CAN WE REDUCE CPU TIME? WHAT IS THE MOST EFFICIENT WAY OF STORING THIS DATA? WHAT DATABASE MANAGEMENT SYSTEM SHOULD WE USE?

Level of Complexity and Risk PROJECT SIZE PROJECT STRUCTURE EXPERTISE WITH TECHNOLOGY

Controlling Risk LOW HIGH SMALL LARGE VERY HIGH VERY LOW MEDIUM-LOW STRUCTURE TECHNOLOGY LEVEL SIZE RISK

CONSEQUENCES OF POOR PROJECT MANAGEMENT COST OVERRUNS TIME SLIPPAGE TECHNICAL SHORTFALLS FAILURE TO OBTAIN BENEFITS

CAUSES OF POOR PROJECT MANAGEMENT IGNORANCE & OPTIMISM MYTHICAL MAN-MONTH: Many tasks sequentially linked, require training. Adding more chefs will not improve the stew. FALLING BEHIND: Bad news travels slowly upward

Challenges ENTERPRISE SYSTEMS: High risk of failure, replacing legacy systems, myriad interconnections BUSINESS PROCESS REENGINEERING: 70% failure rate, deeply rooted in old processes, employees often unprepared

Change Management Challenges MERGERS & ACQUISITIONS: may produce a decline in shareholder value(70% do) difficult to integrate company systems organizational change, worker morale

Implementing Change CONTROL RISK FACTORS: Gear tools, methodologies to level of risk Technical complexity managed with: INTERNAL INTEGRATION TOOLS Technical Project Manager Project management managed with: FORMAL PLANNING TOOLS FORMAL CONTROL TOOLS

Formal Planning Tools PROGRAM EVALUATION & REVIEW TECHNIQUE: Diagram of project activities, sequential and concurrent, shows interactions of activities GANTT CHART: Shows activities as bars along a time line, with beginning, end of each task THESE PROVIDE SCHEDULES

Tools BUDGET: Time, money, resources MONITOR PROGRESS: Completion of tasks, fulfillment of goals CONTROL RISK FACTORS: Cost/benefits

External Integration LINK ALL USERS THROUGHOUT ORGANIZATION USE END USERS AS TEAM MEMBERS SHARE INFORMATION & PROGRESS INCLUDE TRAINING AVOID COUNTERIMPLEMENTATION

Organizational Issues ORGANIZATIONAL IMPACT ANALYSIS: How will system impact structure, attitudes, decision-making, operations SOCIOTECHNICAL DESIGN: Explore group structures, task allocation, job design for human factor

The End Questions