 SAP AG CSU Chico Change Management1 Change Management Final Stages of Implementation ERP Configuration and Use Fall 1998 Dr. Gail Corbitt.

Slides:



Advertisements
Similar presentations
Implementing a Behavior Based Safety Process at Rockwell Automation
Advertisements

best practice project management methodology ©Platinum Services Group Limited What is XPRODi ?
IMPLEMENTATION (ALIAS: “PARTY TIME”). Three Phases of Implementation InstallActivateInstitutionalize.
MANAGEMENT RICHARD L. DAFT.
Presentation to HRPA Algoma January 29, My favourite saying… Fail to plan, Plan to Fail. 2.
Systems Analysis and Design in a Changing World
Enterprise Resource Planning
Planning for Enterprise Systems
Drmasanom 1 Chapter 5: Prepare for the Journey PROJECT METHODOLOGY.
Chapter 1 Assuming the Role of the Systems Analyst
Designing new systems or modifying existing ones should always be aimed at helping an organization achieve its goals State the purpose of systems design.
SUMMER 2005 JUNE Preparing an Organizational Change Management Plan Org Change Management Activities by Project Phase.
University of Southern California Enterprise Wide Information Systems Instructor: Richard W. Vawter.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Geographic Information Systems Implementing a GIS.
Implementing information Security
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Organization Change and Development
SDLC. Information Systems Development Terms SDLC - the development method used by most organizations today for large, complex systems Systems Analysts.
McGraw-Hill/Irwin © 2005 The McGraw-Hill Companies, Inc. All rights reserved Chapter The Future of Training and Development.
Introduction to Systems Analysis and Design
Development and Quality Plans
SCC EHR Workshop for Contractors: Implementation Considerations May 25, 2011.
1Part Organisational Change Cont…. Characteristics of Effective Change Programs  Motivating change by creating a readiness for the change among employees.
Charting a course PROCESS.
Release & Deployment ITIL Version 3
Picture 1 model: ICT lifecycle in a company 1. business needs & business strategy 2. ICT strategy - ICT assessment - ICT strategic plan - ICT implementation/tactical.
© 2006 Jupitermedia Corporation Webcast TitleSuccessful Rollout Planning 1 January 19, :00pm EST, 11:00am PST George Spafford, President Spafford.
Developed by Stephen M.PetersHarcourt, Inc. items and derived items copyright © 2001 by Harcourt, Inc. hapter Change and Development Harcourt, Inc. items.
McGraw-Hill© 2004 The McGraw-Hill Companies, Inc. All rights reserved.
Quiz 1  Availability – check calendar. Chapter 4 Managing Organizational Culture and Change.
How to Manage the Organizational Change LaMarsh & Associates, Inc.
May Agenda  PeopleSoft History at Emory  Program Governance  Why Upgrade Now?  Program Guiding Principles  High-Level Roadmap  What Does This.
Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.
Copyright Course Technology 1999
Information Systems Planning
Organizing Information Technology Resources
ERP Lifecycle.
1 Systems Analysis and Design in a Changing World, Fourth Edition.
Systems Investigation and Analysis
Organizational Change
Name Class.  Review of Implementation Process  Identify Critical Success Factors  Define Change Management (big picture)  Define Role of Corporate.
EMI INFSO-RI SA2 - Quality Assurance Alberto Aimar (CERN) SA2 Leader EMI First EC Review 22 June 2011, Brussels.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Alter – Information Systems © 2002 Prentice Hall 1 The Process of Information System Planning.
16 1 Installation  After development and testing, system must be put into operation  Important planning considerations Costs of operating both systems.
CHANGE Chapter 13. The Concept of Change Change is taking part of the existing organisation and altering it to establish a new or different form. Change.
普 华 永 道 Phase 1: Project Preparation Phase 1: Project Preparation Phase Overview Phase Overview.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
CSI-MAXIMUS, Inc CSI Comprehensive Service & Support Implementing the CSI Way.
1 ISA&D29-Oct ISA&D29-Oct-13 Systems Analyst: problem solver IT and Strategic Planning.
Chapter 8 Managing Change and Innovation. Forces for Change n External: n Customers n Competitors n Technology n Economic n International n Internal:
ERP at The University of Nebraska: Defining Roles Don Mihulka, University of Nebraska Dave Reifschneider, Prescient Consulting Jim Buckler, Prescient Consulting.
+ Chapter 9: Management of Business Intelligence © Sabherwal & Becerra-Fernandez.
1 Change and restructuring, Re-engineering Geoff Leese September 2005 revised September 2006, August 2008, August 2009.
Module 4: Systems Development Chapter 14: Design And Implementation.
Chapter 10 Innovation and Change. Purpose of the Chapter Discuss how organizations change How managers can direct the innovation and change process Discuss.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Crime Analysis and Mapping Jonathan Lewin. Impacting Crime Considerations in Developing a Crime Mapping Application.
Oman College of Management and Technology Course – MM Topic 7 Production and Distribution of Multimedia Titles CS/MIS Department.
Managing Organizational Culture and Change
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Project Life Presented by Chuck Ray, PMP ITS Project Manager.
Slide 1 Software Construction Software Construction Lecture 3.
HOW A PMO CAN DRIVE A PROJECT MANAGEMENT CULTURE Allan R. Loucks, M.A., Psy.D. Robert J. Hess, PMP January 27, 2010.
Change Agents Why your Transformational IT Initiative Will Fail Without Them Terri Campbell Sr. Director of Change Leadership.
Managing Organizational Culture and Change
ORGANIZATIONAL Change management
Managing Change and Innovation
McGraw-Hill © 2004 The McGraw-Hill Companies, Inc. All rights reserved.
Presentation transcript:

 SAP AG CSU Chico Change Management1 Change Management Final Stages of Implementation ERP Configuration and Use Fall 1998 Dr. Gail Corbitt

 SAP AG CSU Chico Change Management2 Overview of Topics Review of Implementation Process Identify Critical Success Factors Define Change Management (big picture) Define Role of Corporate Politics and Other Pitfalls Discuss the Changing Roles in Technology Transfer Situations Overview of “Go Live” Issues and Concerns

 SAP AG CSU Chico Change Management3 Review of Implementation Process Launch the Project Project Planning Define Standards and Procedures Technical Requirements Planning/Initiation Kick-off Define the “As Is” Business Blueprint -- what is the business Identify areas of needed change (re-engineering) Learn what SAP can and can not do

 SAP AG CSU Chico Change Management4 Review of Implementation Process cont. Design the “To Be” Re-engineer the processes that need changing Develop Detailed Design of how ERP will be configured to support the “To Be” business  Configuration of system  Design of Reports  Design all interfaces  Design and test all conversions  Develop Implementation (Go Live) Plan Function and Integration Test

 SAP AG CSU Chico Change Management5 Review of Implementation Process cont Implement or Go Live Install the Tested Configured System on the Production System Set up and Test the support system for users Train the users Populate the Database (bring in legacy data) Cut Over to New system

 SAP AG CSU Chico Change Management6 Critical Success Factors Continuous Visual Behavioral Support from Top Management Understand the Corporate Culture Surrounding Change: Ready the Organization for Change Make Changes to Organizational Structure Well in Advance of Go Live (before you start project is ideal) Document and Communicate Project Status Continuously Project Manager must be able to Stick to the Task/Deliverable Schedule

 SAP AG CSU Chico Change Management7 Critical Success Factors Cont. Project Team must be best at understanding the business and SAP Commitment to the Change (need to ride out the problems) Have a Team that Can Make Decisions Use a Good Project Management Methodology -- Commit to Use It

 SAP AG CSU Chico Change Management8 Components to the Project Business Process (includes Data and Organizational components) Conversions and Interfaces (External systems that need to work with SAP) Development of custom Programs, Reports and Screens (internal SAP interface) Change Management (Site Readiness and Go Live Plan) Integration and Project Management to Coordinate all of the above

 SAP AG CSU Chico Change Management9 Change Management (Big Picture) Change Management: Strategies for awareness, acceptance & incorporation of change into the organization’s environment Systems Administration of hardware and software components Version and Change Request Control Conducting business differently Verblen’s Principle (Weinberg and Gause 1989) “There’s no change, no matter how awful, that won’t benefit some people, and no change, no matter how good, that won’t hurt some.” Plan or Manage the Change so that users and System are ready at the same time and expectations on both sides are matched

 SAP AG CSU Chico Change Management10 Change Management (Big Picture) Change Manager Development Project Team Prepare Users Prepare System Convergence

 SAP AG CSU Chico Change Management11 Goals of Change Management Convergence of User and System Readiness Optimize Organization’s Social (Cultural) and Technical Infrastructures Create a Learning Organization Continuous Improvement Customer Focus Adaptable to changes in the environment (external and internal)

 SAP AG CSU Chico Change Management12 Key Principles of Change Management Steering Committee Must Have Product and Process Champions or Stakeholders Communication needs to multi-channeled (up is as valued as down) Conflict resolution and knowledge acquisition are collaborative (information sharing not hoarding) Implementation Team (change management team) has a structure and roles of individuals are defined Resistance to Change is always there but may be hard to detect until after Go Live (Be Proactive)

 SAP AG CSU Chico Change Management13 Challenges and Pitfalls Change process must be planned and managed Magnitude of change is ALWAYS greater than imagined Resistance to change appears in different forms -- must be addressed In global organizations cultural factors need special consideration Change in organizations occurs in stages -- need strategies for EACH stage

 SAP AG CSU Chico Change Management14 Stages of Change Boston consulting Group 5 Stage Model: Stagnation (building desire to change) Anticipation (acceptance of change is highest here) Implementation (critical time for commitment -- most pain occurs here) Determination (expectations get real -- people begin to incorporate change into daily routine) Fruition (acceptance begins to climb back up) Lewins’ 3 Stage Model: Unfreeze, Move and Re-freeze

 SAP AG CSU Chico Change Management15 Strategies for Stages Unfreezing: Develop awareness of change Users see or have a need to change (internal felt need) Driving forces for change outweigh the Restraining Forces Moving: Involve users in project team (as is --> to be processes) Train the users Develop in-house gurus -- change agents that can help resisters

 SAP AG CSU Chico Change Management16 Strategies for Stages Re-freeze or Institutionalize Change: Support organization is in place and working Resistance to change has been addressed Development Team moves on to a new project At all Stages Communication must be Open Trust within the organization must be high Knowledge must be Shared

 SAP AG CSU Chico Change Management17 Force Field Analysis Technique to identify positive or driving forces and negative or restraining forces in the environment that contribute to the impending change Can be personal or environmental Identify the item as well as the strength of each item Uses: Determine readiness at the beginning of the process Measure progress and surface new issues as we move through process Build strategies and tactics that reinforce the positive and address the negative (at all stages)

 SAP AG CSU Chico Change Management18 Force Field Example Change: Change to Word from Spellbinder Driving Forces Restraining Forces Department Standard Free Secretarial Support Updates to software are free Long learning curve Dissertation files may have to be re-entered Printer control is difficult Mail merge is harder to use

 SAP AG CSU Chico Change Management19 Force Field Example: Pick something in your life you’d like to change List the forces (Driving and Restraining) Draw the lines for strength Interpret Results

 SAP AG CSU Chico Change Management20 Changing Roles in Technology Transfer Situations Knowledge Needed to Implement Change is not Available Change Agents are Consultants Roles include Scouting for New Work and Executing Existing Work Consultant will exit organization (need Knowledge Transfer) Trust of consultant must be high Action in organization must be unique to organization but most consultants use boiler plate solutions Outsourcing can be Viable

 SAP AG CSU Chico Change Management21 Latest Challenges/Changes in IT Reduced Need for Programmers Reliance on Complex Technology Higher User Involvement User’s Own Systems -- IT more of Servant Role How do these issues affect you? How do you feel about these? How are you prepared to work in an environment where these things occur?