IMPLEMENTATION (ALIAS: “PARTY TIME”). Three Phases of Implementation InstallActivateInstitutionalize.

Slides:



Advertisements
Similar presentations
Planning for Enterprise Systems
Advertisements

Tutorial 9 Lanjun Zhou SEEM Outline Introduction to Assignment Phase 4 Transition to the new System (Chapter 13) – Making the transition to the.
Change Management. Overview Change Equals Effect Over Time (CET) Model Lewin’s Force Field Analysis Model Force Field Analysis Exercise Barriers to Change.
Change Management By MCA-SEM IV.
Chapter 8 Planned Change.
Unit “ 10 “ CONTROLLING. Controlling Final step in the management process: actions taken to ensure that actual outcomes are consistent with those Planned.
Data - Information - Knowledge
Organizational Behavior Managing Organizational Change and Development Chapter 18 It’s all about: CHANGE.
1 Samples The following slides are provided as samples and references for the Quarterly Reviews Additional slides will be added.
Implementation.
Chapter 6 Systems Development.
System Implementations American corporations spend about $300 Billion a year on software implementation/upgrade projects.
Organizational Change  Lecture #23. Lewin’s Force Field Analysis.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
© Copyright 2011 John Wiley & Sons, Inc.
Computing Essentials 2014 Systems Analysis and Design © 2014 by McGraw-Hill Education. This proprietary material solely for authorized instructor use.
Organization Change and Development
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
 SAP AG CSU Chico Change Management1 Change Management Final Stages of Implementation ERP Configuration and Use Fall 1998 Dr. Gail Corbitt.
PowerPoint Presentation for Dennis, Wixom & Tegarden Systems Analysis and Design Copyright 2001 © John Wiley & Sons, Inc. All rights reserved. Slide 1.
Organizational Change Occurs when an organization restructures resources to –increase the ability to create value –improve effectiveness.
Building Information Systems lesson 26 This lesson includes the following sections: The Systems Development Life Cycle Phase 1: Needs Analysis Phase.
1Part Organisational Change Cont…. Characteristics of Effective Change Programs  Motivating change by creating a readiness for the change among employees.
1Part Organisational Change Cont…. Characteristics of Effective Change Programs  Motivating change by creating a readiness for the change among employees.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 4th Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
Initiating and Planning Systems Development projects
Working with change. In our constantly changing world we need to find effective ways of dealing effectively with change. This presentation outlines some.
Design Completion A Major Milestone System is Presented to Users and Management for Approval.
Laudon & Laudon: Canadian Edition
CSIS3600 Systems Analysis and Design Systems Implementation: Installation.
Organizational Change
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design, 2 nd Edition Copyright 2003 © John Wiley & Sons, Inc. All rights reserved.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Co-location Sites for Business Continuity and Disaster Recovery Peter Lesser (212) Peter Lesser (212) Kraft.
CHAPTER 17 PLANNING& IMPLEMENTING INTRODUCTION For managers to be effective they must develop strategies to plan, direct and control change. To be effective.
16 1 Installation  After development and testing, system must be put into operation  Important planning considerations Costs of operating both systems.
Building and Implementing Decision Support Systems Week 6.
Organisational Change and Stress Management. Questions To what do people really respond / react when they need to cause / suffer change? Have you ever.
Technology New York State Learning Standards for Grades 7 & 8.
INFS 6225 Object Oriented Systems Analysis & Design Chapter 14: Installation & Operations.
The Operating System ICS3M.  The operating system (OS) provides a consistent environment for other software programs to execute commands.  It gives.
Construction, Testing, Documentation, and Installation Chapters 15 and 16 Info 361: Systems Analysis and Design.
Change Management Change is the constant thing in this world and it also true for the organization also. Change management involves two major dimensions,
Module 4: Systems Development Chapter 14: Design And Implementation.
Installation (ch. 15) MSO 08/09, WP. Issue  It is about the final step of “installing” a new software in an organization.  The issue is not just about.
Chapter 10 Innovation and Change. Purpose of the Chapter Discuss how organizations change How managers can direct the innovation and change process Discuss.
Chapter 11 Strategic Leadership and Managing Crises and Change Lussier, R. and Achau, C. (2007): Effective Leadership, 3 rd Edition, South-Western, Cangage.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Introduction to IT investment decision-making Pertemuan 1-2 Matakuliah: A Strategi Investasi IT Tahun: 2009.
Organizational Design, Diagnosis, and Development Session 14 The Management of Change.
CIS Review for Exam 11 Review for Exam I. CIS Review for Exam 12 Gorry and Scott Morton Framework Robert Anthony Herbert Simon.
Thepul Ginige Lecture-7 Implementation of Information System Thepul Ginige.
HO Final Session: Wrap-up EK BUNCHUA Room # 528 Thammasat Business School.
SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright © 1997.
Change Management. Definition Change management is a structured approach to transitioning individuals, teams, and organizations from a current state.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Systems.
Contemporary Business Issues Change Management Theory Module Tutor: Nigel Bryant Session th February 2016.
Outline Risk Identifying risks to your project Change Managing change for your project.
Change Management.
Information Systems Development
Conversion Strategies
Developing Information Systems
Installation Conversion is the technical process of replacing the old system with the new one. Designers select the method, timing, and location of the.
Managing Organizational Culture and Change
Chapter 14: Installation and Operations
Resistance to Change and Change Management
INFS 6225 Object Oriented Systems Analysis & Design
Strategies for Implementing Change
Chapter 18 Organizational Behavior: Foundations, Realities, & Challenges Nelson & Quick, 5th edition Managing Change.
INFS 6225 Object Oriented Systems Analysis & Design
Presentation transcript:

IMPLEMENTATION (ALIAS: “PARTY TIME”)

Three Phases of Implementation InstallActivateInstitutionalize

Hardware Hardware Software Software People People Procedures Procedures Data Data Conversion and Information Systems Components

Parallel Conversion Strategies Old System New System Old System New System Cutover

Conversion Strategy Advantages & Disadvantages Conversion Strategy: Cutover 1. No duplication of effort for the users 2. No transition costs 3. Learning advantage for groups converted later 1. High risk 2. Cannot compare results with the old system 3. Sense of user insecurity + -

Conversion Strategy Advantages & Disadvantages Conversion Strategy: Parallel 1. Low risk 2. Sense of user security 3. Ability to compare results with old system 1. Duplication of effort for users 2. Transition costs 3. Additional processing strain on the computer + -

Implementation Meets With Resistance Install Activate Institutionalize

Failure Perception Technology Infrastructure Human Factors Failure Reality Technology Infrastructure Human Factors (Note: Bars in both graphs are not to scale; representative only)

Information Systems Development Parallel Tracks User Management Responsibility Information Systems Management Responsibility Users must stay involved and be prepared to use the new system The system must be prepared and meet the user specification Convergence with both user and system being ready at the same time PROBLEM: When either track is ready ahead of the other track.

Implementation Critical Success Factors u User commitment u Organizational trust u Open communication u Financial commitment u Common view of the development strategy

Stages of Organizational Change and their Relationship to Implementation Organizational Change Phases Implementation Phases Unfreezing Moving Refreezing Install Activate Institutionalize (Adapted from: Lewin, K., Field Theory in Social Science, Harper & Row, New York, 1958.)

Action Research & Force Field Analysis Action Research: A method for identifying the data associated with the degree of conflict or resistance in a business’s environment and then dealing with it in a real-time manner. Force Field Analysis (Tool/Form): A tool used to identify an individual’s perceived positive and negative aspects about some current or pending organizational change.

Force Field Analysis Tool Blank Force Field Analysis Form Driving Forces (Positive) Restraining Forces (Negative)

Completed Force Field Analysis Form Driving Forces (Positive) Restraining Forces (Negative) industry std. dept. std. better support site license new software etc... learning curve DOS programs machine slow more memory etc... total = X inches total = Y inches

Party On, Dude!