Six Steps to Implementing Change Management that Works Arvind Parthiban.

Slides:



Advertisements
Similar presentations
Effective Meetings.
Advertisements

Report to the IIJIS Implementation Board October 20, 2004 Dale Good – SEARCH Dave Usery – IJIS Institute.
Agenda for Discussion Agenda for Discussion Risk Management Stakeholder Analysis project solutions for your world Gina Davidovic, PMP
OPSM 639, C. Akkan Monitoring Progress How does a project get one year late? … One day at a time –Frederick P. Brooks MBWA: Management by Walking Around.
Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.
Change Management (with an IT perspective). MBA Statement of Objective The object of undergoing this study-project is to develop an understanding.
1 INTERNAL CONTROLS A PRACTICAL GUIDE TO HELP ENSURE FINANCIAL INTEGRITY.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
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.
Course Technology Chapter 3: Project Integration Management.
By Saurabh Sardesai October 2014.
IS550: Software requirements engineering Dr. Azeddine Chikh 4. Validation and management.
Computer Security: Principles and Practice
Executive Dashboard Systems Secure CITI Adam Zagorecki April 30, 2004.
Monitoring, Review and Reporting Project Cycle Management A short training course in project cycle management for subdivisions of MFAR in Sri Lanka.
Fox & Sons Company: IT Change Management Policy Presentation Britt Bouknight Caitlyn Carney Xiaoyue Jiu Abey P John David Lanter Leonardo Serrano.
Change Management Chris Colomb Trish Fullmer Jordan Bloodworth Veronica Beichner.
Change Management Initiative. Definitions What is a change? – A change is the addition, modification or removal of anything that could have an effect.
Emerging Latino Communities Initiative Webinar Series 2011 June 22, 2011 Presenter: Janet Hernandez, Capacity-Building Coordinator.
Project Governance Structure
Policy? Guidance? Standard Operating Procedure? Tips on how to achieve compliance with minimum red tape Carolyn Bargoot, Associate Director Post-Award.
Change Advisory Board COIN v1.ppt Change Advisory Board ITIL COIN June 20, 2007.
How the Change Control Process Affects Project Quality
Release & Deployment ITIL Version 3
© 2006 Jupitermedia Corporation Webcast TitleSuccessful Rollout Planning 1 January 19, :00pm EST, 11:00am PST George Spafford, President Spafford.
What is Business Analysis Planning & Monitoring?
The Key Process Areas for Level 2: Repeatable Ralph Covington David Wang.
Copyright Course Technology 1999
BW Tuckman’s four stages of team development
Involving the Whole Organization in Creating or Restructuring a Volunteer Program Louise DeIasi DeCava Consulting.
LEADERSHIP. What is leadership? Leadership is a process by which a person influences others to accomplish an objective and directs the organization in.
Be more effective at “planning the work and working the plan” Project Management Tips.
Time Mastery Profile ® The Time Mastery Profile ® helps people understand how they think about and use their time. This understanding is the foundation.
‘Developing the appraisal process in the wider context of the Sport and Fitness sector of Higher Education’. Welcome & Introductions.
Company duties under the ISM Code
Hartley, Project Management: Integrating Strategy, Operations and Change, 3e Tilde Publishing Chapter 3 Stakeholder Management Strategies for continuous.
Building a Corporate Risk Culture Shane Troyer, CPA, CIA, CFE, CISSP Principal Operational Advisory Joost Houwen, CISA,
Conservation Districts Supervisor Accreditation Module 9: Employer/Employee Relations.
BUSINESS PLUG-IN B15 Project Management.
Module 7. Data Backups  Definitions: Protection vs. Backups vs. Archiving  Why plan for and execute data backups?  Considerations  Issues/Concerns.
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
Soft Tech Development Inc. 1 Software Project Tracking A CMM Level 2 Key Process Area Soft Tech Development Inc.
Software Development Process and Management (or how to be officious and unpopular)
Service Transition & Planning Service Validation & Testing
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Software Project Management
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.
Service Management for CERN Change Management Acceptance Meeting Geneva, Jochen Beuttel.
Leadership & Management Reading for Lesson 7: The Chain of Command and Leadership Triad.
QA Methodology By Rajib Roy Independent Consultant Qcon.
Getting There from Here: Creating an Evidence- Based Culture Within Special Education Ronnie Detrich Randy Keyworth Jack States.
STEP 4 Manage Delivery. Role of Project Manager At this stage, you as a project manager should clearly understand why you are doing this project. Also.
McGraw-Hill/Irwin Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. Business Plug-In B15 Project Management.
1  2002 North Haven Group 1 Six Sigma Improvement Process Improve Phase Activities Introduction Identifying Solutions Evaluating Potential Solutions Solution.
(Project) RISK MANAGEMENT PROCESS SEPTEMBER 5, 2008.
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
Project Organization Chart Roles & Responsibilities Matrix Add Project Name.
Change Management & ITIL V3
SOLGM Wanaka Retreat Health and Safety at Work Act 2015 Ready? 4 February 2016 Samantha Turner Partner DDI: Mob:
Introduction to ITSM processes. CONFIDENTIAL Agenda Problem Management  Overview  High Level process Change Management  Overview  High Level process.
Info-Tech Research Group1 Info-Tech Research Group, Inc. Is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
Building a Sound Security and Compliance Environment for Dynamics AX Frank Vukovits Dennis Christiansen Fastpath, Inc.
Disaster Recovery Management By: Chris Rozic COSC 481.
1 Working with Project Stakeholders in a Statewide Project PMI-SVC PMO Forum Monthly Meeting Dan Conway, PMP October 22, 2008.
Computer Security: Principles and Practice First Edition by William Stallings and Lawrie Brown Lecture slides by Lawrie Brown Chapter 17 – IT Security.
IT Service Transition – purpose and processes
Change Management Change Management.
ITPD ISSUE MANAGEMENT PROCESS SEPTEMBER 5, 2008
Our new quality framework and methodology:
Principles of Change Management
Presentation transcript:

Six Steps to Implementing Change Management that Works Arvind Parthiban

Agenda Identify why you want the change Sell the Value of Change Management Define what a Change is Assign Roles & Responsibilities Define a process for handling changes Define key performance indicators

A “Failed Change” Are You A Victim?

What are businesses doing without proper change management in place?

The Maverick

One Man Show

Half baked

Gut Feel Vs Actual Risk Change is simple Doesn‘t require any major planning Slippages when you underestimate the time required Never expects any failure – ignoring the dependencies. Most of all “the people problem”

End Result ~ Failure

Change Management is Never Easy…

The right questions What is the cost of making the change? Does the benefit outweigh the cost? What is the business priority of the change? How do we implement the change? Who will implement the change? When should we implement the change? What do we do if the change goes wrong? Do we have a backup plan in place? Why: The reason for the change. What is the business benefit you hope to achieve with the change? What: Is it hardware, software, system architecture, a process, documentation, or a combination of these that will be subjected to change? Impact: What are the possible negative consequences of the change ?

Six Steps to Implement Change Management that Works

1.Identify what you want to change ?

Get executive buy-in for your change management implementation by selling the benefits and the objectives at a high level. Stakeholders On-board

Agree to a high-level change policy that prohibits unauthorized changes and gives the change management function the authority to make decisions and handle resistance Agree to a Change Policy

2.Sell the value of Change Management

Communicate the “why” before you communicate the “what.”

Answer the question, “what’s in it for me?” for each stakeholder group.

3.Define what a change is?

Change Types Standard – (Low Risk )Approval not required changes Minor – (Low Risk with limited potential Impact) CAB usually not necessary Normal – (Moderate Risk ) CAB is a Must Major – (High Risk) Higher Change Authority for approval Emergency – (Disrupting Business Impact) Quick practical approach

Change Advisory Board CAB is a group of experts/advisors who can recommend on the change proceedings, both requesters & technicians can be part of CAB. Change Manager He is the key decision maker of the change request, who has the authority to approve or reject a change. Change Authority Every change requires a formal authorization before it can be implemented. Depending on size, cost, and risk, an appropriate change authority is required to provide this approval. The change authority may be a director, c-level manager, or indeed, the board of directors ECAB The ECAB is a smaller, core group of CAB members that is available on short notice to respond to emergency changes that must be made on a short notice to remedy an urgent issue. 4.Assign Roles & Responsibilities

5.Define a process for handling changes

6.Define Key Performance Indicators Key performance indicators refer to: Number of successful changes Number of failed changes that were rolled back Number of changes in the backlog Number of incidents caused by change Number of emergency/out-of-hours changes Number of unauthorized changes identified  Resources used and funds spent on changes  Percentage of changes that happened as per the FSC  Critical Success Factors:  Define a set of KPIs that are relevant to your organization.  Use KPIs to communicate the value of change management to the business and specific IT groups on a regular basis.

AVOID being bureaucratic PROCEDURES for Minor, Major & Emergency Changes Well COMMUNICATED & UNDERSTOOD process AUTOMATED process for ‘standard’ changes DELEGATED authority to Change Manager EASY to raise and track a change Clear REASONS for decisions taken Clear COMMUNICATION to requestors and to affected users AUTHORITY must reside with CAB & Change Manager to avoid ‘independent’ action Tips for a Successful Change

Thank you Twitter