IS 425 Enterprise Information I LECTURE 9 Autumn 2004-2005  2004 Norma Sutcliffe.

Slides:



Advertisements
Similar presentations
Roadmap for Sourcing Decision Review Board (DRB)
Advertisements

Course: e-Governance Project Lifecycle Day 1
UNDERSTANDING THE BUSINESS VALUE OF SYSTEMS AND MANAGING CHANGE
Risks  All projects have some degree of risk  Risks are issues that can cause problems  Delay in schedule  Increased project costs  Technical risk.
Systems Analysis and Design 9th Edition
Workforce Planning Training for Supervisors Presentation Subtitle/Description Presenter’s Name Date.
Chapter 2.
IS 425 Enterprise Information LECTURE 7 Winter
Project Estimation Describe project scope, alternatives, feasibility.
Managing the Information Technology Resource Jerry N. Luftman
Recall The Team Skills 1. Analyzing the Problem 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System.
IT Planning.
Chapter 10 Information Systems Management. Agenda Information Systems Department Plan the Use of IT Manage Computing Infrastructure Manage Enterprise.
1 July 23, 2002 Strategic Technology Plan Briefing to LOT Committee.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Computer Security: Principles and Practice
Principles of Information Systems, Sixth Edition 1 Systems Investigation and Analysis Chapter 12.
Pertemuan 15 Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Project Management and MS Project. The project management triangle: Time Resources Scope.
Remedy, a BMC Software company Change Management Maximize Speed and Minimize Risk in the Change Process.
Project Risk Management Risk Mitigation. Risk Management  The prime objective of risk management is to minimize the impact and probability of the occurrence.
Development and Quality Plans
Development plan and quality plan for your Project
VENDORS, CONSULTANTS AND USERS
Module 8: Risk Management, Monitoring and Project Control We would like to acknowledge the support of the Project Management Institute and the International.
S/W Project Management
Project Risk Management. The Importance of Project Risk Management Project risk management is the art and science of identifying, analyzing, and responding.
May 12 th Monitoring and Project Control. Objectives Anticipated Outcomes Express why Monitoring and Controlling are Important. Differentiate between.
© 2001 by Carnegie Mellon University PSM-1 OCTAVE SM : Senior Management Briefing Software Engineering Institute Carnegie Mellon University Pittsburgh,
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
Project Management Tomáš Sabol Technical University in Košice
Chapter 13: Developing and Implementing Effective Accounting Information Systems
MGT 461 Lecture # 19 Project Initiation Phase (I OF II)
Alaska Staff Development Network – Follow-Up Webinar Emerging Trends and issues in Teacher Evaluation: Implications for Alaska April 17, :45 – 5:15.
Basic of Project and Project Management Presentation.
Chapter 12: Systems Investigation and Analysis. Agenda  How to Develop a CBIS?  Systems Development Life Cycle (SDLC)  Prototyping  Join Application.
Module 4: Systems Development Chapter 12: (IS) Project Management.
Lecture 3 Managing the Development Project SFDV Principles of Information Systems.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Project monitoring and Control
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Object-Oriented Software Engineering
IS 425 Enterprise Information I LECTURE 10 Autumn  2004 Norma Sutcliffe.
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.
+ Chapter 9: Management of Business Intelligence © Sabherwal & Becerra-Fernandez.
IT 499 Bachelor Capstone Week 4. Adgenda Administrative Review UNIT Four UNIT Five Project UNIT Six Preview Project Status Summary.
Principles of Information Systems, Sixth Edition Systems Investigation and Analysis Chapter 12.
VENDORS, CONSULTANTS AND USERS. WHY CAN’T COMPANIES DEVELOP THEIR OWN ERP PACKAGES? To develop an ERP package is a complex & time consuming activity which.
Project Management Methodology Development Stage.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Project Risk Management Planning Stage
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Project & Risk Management
SecSDLC Chapter 2.
Module 5 Session 5.2 Visual 1 Module 5 Refining Objectives, Scope, and Other Project Parameters Session 5.2 Reviewing the PAR and refining key project.
An EDI Testing Strategy Rosemary B. Abell Director, National HIPAA Practice Keane, Inc. HIPAA Summit V October 30 – November 1, 2002.
Chap 8: Administering Security.  Security is a combination Technical – covered in chap 1 Administrative Physical controls SE571 Security in Computing.
Erman Taşkın. Information security aspects of business continuity management Objective: To counteract interruptions to business activities and to protect.
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
Report Performance Monitor & Control Risk Administer Procurement MONITORING & CONTROLLING PROCESS.
NEM201 Week 4 Project Plan Create and complete outstanding items. 01. Front Cover 02. Document details 03. Scope Document 04. Technical Design 05. Creative.
Info-Tech Research Group1 Manage the IT Portfolio World Class Operations - Impact Workshop.
CBIZ RISK & ADVISORY SERVICES BUSINESS CONTINUITY PLANNING Developing a Readiness Strategy that Mitigates Risk and is Actionable and Easy to Implement.
Outline Risk Identifying risks to your project Change Managing change for your project.
IS 455 Project Management – What is a project?
Systems Analysis and Design in a Changing World, 4th Edition
Description of Revision
Cyber security Policy development and implementation
The Survival Plan.
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

IS 425 Enterprise Information I LECTURE 9 Autumn  2004 Norma Sutcliffe

IS425 Autumn Norma Sutcliffe Session 92 Sourcing Decisions & Risk Management Exercise Quiz Lecture

IS425 Autumn Norma Sutcliffe Session 93 Exercise Each team is given Leadership Effectiveness tasks For each task: Give one example of the wording of the task in: Directive Style and who is the appropriate audience Interactive Style and who is the appropriate audience Nondirective Style and who is the appropriate audience

IS425 Autumn Norma Sutcliffe Session 94 Quiz DL students have homework assignment on COL

IS425 Autumn Norma Sutcliffe Session 95 Risk Management Definition The process in which potential risks to a business are identified, analyzed and mitigated, along with the process of balancing the cost of protecting the company against a risk vs. the cost of exposure to that risk. Or, "What imperils getting benefits from effort?"

IS425 Autumn Norma Sutcliffe Session 96 General Categories of Risks: Economic Risks Technical Risks Organizational Risks Legal Risks Terrorist Risks

IS425 Autumn Norma Sutcliffe Session 97 General Categories of Risks: Economic Risks applies to risks that can potentially impact the business. These risks could result to failure or loss of business. business environment changes vendor survival

IS425 Autumn Norma Sutcliffe Session 98 General Categories of Risks: Technical Risks applies to the risks that can impact the development, implementation, and the operation of a system. Sources of these risks can come from the project team’s degree of familiarity with the technology, familiarity with the application, security and project size. integrating technology with existing portfolio poor training poor monitor/control

IS425 Autumn Norma Sutcliffe Session 99 General Categories of Risks: Organizational Risks applies to the risks that could potentially impact the acceptance of the project. Problems arise when there is potential reduction of manpower, changing the way business process is performed, and when there is increase of workload. Consequences to these risks are defined below: resistance to the system low morale of personnel lack of political support possible rejection of the system poor procedures lack of trained support lack of trainers ineffective use by users poor help desk

IS425 Autumn Norma Sutcliffe Session 910 General Categories of Risks: Legal Risks applies to risks arising from potential lawsuits and liabilities associated with the implementation of a project. fiduciary responsibility of managers laws and regulations inappropriately administered personal financial and criminal liability (from shareholder lawsuits and FCPA)

IS425 Autumn Norma Sutcliffe Session 911 General Categories of Risks: Terrorist Risks applies to risks arising from intentional destruction or malevolent modification of the physical equipment data and information files communication links software

IS425 Autumn Norma Sutcliffe Session 912 Sources of Project Risks Project Work Project Team and Leader Management Business Situation Other Projects External Factors Technology Vendors and Contractors Business Processes Business Units Customers and Suppliers

IS425 Autumn Norma Sutcliffe Session 913 Sources of Project Risks Project Work – quality and completeness of the work Project Team and Leader – personality issues allocation of resources trust issues Management – poor or no decision making lack of attention Business Situation -- assumptions change -- conditions change

IS425 Autumn Norma Sutcliffe Session 914 Sources of Project Risks Other Projects -- Changes in priorities External Factors -- regulatory changes, -- union pressures, -- consumer groups -- various special interest groups Technology -- changes that can make project irrelevant

IS425 Autumn Norma Sutcliffe Session 915 Sources of Project Risks Vendors and Contractors -- reliability -- quality -- sustainability Business Processes -- reengineering changes power bases Business Units -- management changes -- organization changes -- staffing changing Customers and Suppliers -- changes in mix

IS425 Autumn Norma Sutcliffe Session 916 Keeping Track of Risks ProjectsEconomicTechnicalOrganizational Keep a count of the OPEN RISKS by type for each project – Update regularly Keep track of your progress in mitigating / resolving risks REMEMBER – MANY RISKS WILL COME TOWARDS THE END OF THE PROJECT – SO THINK / PLAN AHEAD

IS425 Autumn Norma Sutcliffe Session 917 Constraints on Taking Actions Before taking actions to resolve/mitigate risks keep in mind— Symptoms seen as Problems symptoms can be treated leaving the underlying problem unresolved & growing Seen as panicking If you constantly bring the risks to management’s attention – may be seen as crying wolf Look before you leap – get enough facts first

IS425 Autumn Norma Sutcliffe Session 918 Risk Strategies Deal only with critical factors – need to monitor all problems and catch those before they balloon React quickly to issues – need to know enough about what causes issues Proactive but still conservative – use a method that will help you know you have enough to act and then act

IS425 Autumn Norma Sutcliffe Session 919 Preferred Project Risk Strategy Method Group issues by Impact if not solved Time pressure to do something Use your judgment and experience on positioning issues

IS425 Autumn Norma Sutcliffe Session 920 Issues to be Addressed Issues 23 and 27 must be addressed Issue 10 has time pressure so investigate

IS425 Autumn Norma Sutcliffe Session 921 Time Marches on Some issues go away Some issues emerge Some get more troublesome

IS425 Autumn Norma Sutcliffe Session 922 Risk Issue Management Process 1. Create project risk issue database 200+ commonly known problems 2. Identify most likely based on experience 3. Present potential issues to management with project proposal 4. In estimating project tasks – more issues may emerge 5. All issues relate to tasks – if not find the missing tasks

IS425 Autumn Norma Sutcliffe Session 923 Risk Issue Management Process 6. Phase beginning -- team meetings on near term issues -- discuss impact of issues -- track the issues -- develop issues resolution table -- use 1-page project summary to Mgt. 7. Create table of issues versus projects Create GANTT chart (major tasks / issues) -- follow-up on resolved issues (no reappearance) -- implement actions when known or appropriate 8. When resolved -- celebrate

IS425 Autumn Norma Sutcliffe Session 924 Management Communications Focus on informal communications with management on risk issues Focus on getting management slowly on board with knowledge of problem growing Then on presenting alternatives Then on getting approval for actions

IS425 Autumn Norma Sutcliffe Session 925 Project Risk Portfolio Approach Same issues database for all major projects Common issues reporting method Periodically prepare new table of issues versus projects Support / facilitate Meetings Analysis on issues When issue resolved -- take the decisions, then -- identify action items for each impacted project -- follow up on action items across project -- report to management

IS425 Autumn Norma Sutcliffe Session 926 AFTER PROJECT DEPLOYMENT RISKS CONTINUE and MUST BE HANDLED

IS425 Autumn Norma Sutcliffe Session 927 OTHER RISK APPROACHES For IT investments – not project management Portfolio approach – manage risks by treating IT resources such as hardware, software, services and personnel as collection of investments. Decisions are made based from the potential return of investment or payoff against the level of risks. Interdisciplinary Approach – applies an integrated assessment of the risks from various groups in a company to determine and assess all dimensions of risks.

IS425 Autumn Norma Sutcliffe Session 928 NEXT WEEK REVIEW DEBATE WORKSHOP