Presentation is loading. Please wait.

Presentation is loading. Please wait.

Stakeholder Identification OCM 4 ASAP Guide. Who will / might be impacted by the roll-out? Who are the decision makers in that area and who are the subject.

Similar presentations


Presentation on theme: "Stakeholder Identification OCM 4 ASAP Guide. Who will / might be impacted by the roll-out? Who are the decision makers in that area and who are the subject."— Presentation transcript:

1 Stakeholder Identification OCM 4 ASAP Guide

2 Who will / might be impacted by the roll-out? Who are the decision makers in that area and who are the subject matter experts? What is the number of identified stakeholders? Where are these people located? What are their expectations to the roll-out and needs? What are previous experiences of identified stakeholder with the projects alike? What is the attitude of the stakeholders to the project / roll- out? What could be the reaction of stakeholder groups according to the planned changes? What are the benefits for these stakeholder groups? What are possible disadvantages for them? What will be the change for the identified stakeholder groups? How intensive will be the change for them? When will the change happen? What are the impacts? When do they occur? How exactly does the impact affect the stakeholder? Plan and perform activities to overcome resistances Manage resistances Coordinate communication and training activities in terms of stakeholders Manage stakeholders’ requirements and manage them through the constraints (time, budget etc.) Stakeholder Identification Execution Change impact analysis Stakeholder Analysis Stakeholder Management Cycle Checking with the existing stakeholders whether their attitudes have changed. Are there new stakeholders? Have impacts changed? Have priorities changed? How the planned STHM activities can be adjusted to the current situation. Stakeholder Management Monitoring

3 SAP OCM Analysis Tool Main deliveries Group Identification Stakeholder Acceptance Change Impact Execution List of measures Gather Information Execute Analyze Information

4 Who will / might be impacted by the roll-out? Who are the decision makers in that area and who are the subject matter experts? What is the number of identified stakeholders? Where are these people located? What are their expectations to the roll-out and needs? What are previous experiences of identified stakeholder with the projects alike? What is the attitude of the stakeholders to the project / roll- out? What could be the reaction of stakeholder groups according to the planned changes? What are the benefits for these stakeholder groups? What are possible disadvantages for them? What will be the change for the identified stakeholder groups? How intensive will be the change for them? When will the change happen? What are the impacts? When do they occur? How exactly does the impact affect the stakeholder? Plan and perform activities to overcome resistances Manage resistances Coordinate communication and training activities in terms of stakeholders Manage stakeholders’ requirements and manage them through the constraints (time, budget etc.) Stakeholder / User Identification Execution Change impact analysis Stakeholder analysis Stakeholder Management Cycle Checking with the existing stakeholders whether their attitudes have changed. Are there new stakeholders? Have impacts changed? Have priorities changed? How the planned STHM activities can be adjusted to the current situation. Stakeholder Management Monitoring

5 Objective Stakeholder Type Level of Influence Description of the identified stakeholders (groups) in terms of their personal features, job locations, etc. Grouping of employees who meet similar criteria, i.e. end users with the same tasks, etc. Description of all the project related stakeholders / stakeholder groups High level description of stakeholder groups Identification and grouping of people who are (A.) influencing the project and (B.) Groups and employees impacted by it. The purpose is to identify the level of “Buy-in” and Risk for each Stakeholder group & in some cases important individuals. Setting the basis for change management activity planning. What are we looking for? Deliverables Stakeholder and User identification All groups are identified and managers are aware of the people that they should work together with and how best to approach them. The headcounts are identified Benefit Clear definition of the project scope High level project plan Availability of internal documents, i.e. organizational chart; roles description, etc. Input conditions

6 Identification of relevant stakeholder groups – criteria Three main questions help to identify the relevant groups. Who is directly impacted by the project? (The groups that are strongly impacted by the project.) Analysis of the organizational structure Analysis of the processes Who has an interest in promoting or delaying the project because of personal agendas or fear etc? Analysis of the stakeholder Who is indirectly impacted by the project? (The groups that will have changes in their own daily process activities.) Analysis of the organizational structure Analysis of the processes

7 Possible sources of information for stakeholder identification There are many sources of information you might use to identify your stakeholders. Here are some examples: Client’s organizational chart Project’s organizational chart Leadership alignment interviews Meetings with SME’s and experienced employees Conversations / interviews with Client’s management (include different levels) Brainstorms with your project colleagues and other experienced consultants Field observations Personal experience Workshops in which matrices, diagrams and other instruments of analysis are developed collaboratively Note 1 Review Note that stakeholders change over time, so review your documents as the project changes phases. Note 2 If in doubt – include! If you have any doubts if you should include the stakeholder or not, DO include him/her.

8 Overview of some standard stakeholder groups CEO Works council Head of branch End user Group leader Business partners Customer Supplier Head of department Board members … Each situation is unique though, and requires an understanding of local conditions and realities.

9 Identification of user and stakeholder groups Name (headcount) Info 123 Highly impacted Medium impacted Slightly impacted Name (headcount) Info Name (headcount) Info Low importance Medium importance High importance User Groups Stakeholder Groups Managers Owners Employees Customers Partners Suppliers Press Government Local communities Public authorities Other organizations

10 Some challenges you might face during stakeholder identification Some stakeholders always stay on the side, to “hide” from the stakeholder identification process. Many people simply do not feel part of formal institutions. Many projects are large and complex, so it’s better to take time and identify your stakeholder properly. Employees often belong to various groups, so avoid putting people into simple “boxes”. The project needs a strong effort from key stakeholders. Every stakeholder constructs his/her own understanding of the reality. This is why the behavioral models of stakeholders/stakeholder groups have to be analyzed and proper measures must be assigned to each of them in order to have the stakeholders “buy-in” for the project

11 Thank you!

12 Copyright 2009 SAP AG All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warrant.


Download ppt "Stakeholder Identification OCM 4 ASAP Guide. Who will / might be impacted by the roll-out? Who are the decision makers in that area and who are the subject."

Similar presentations


Ads by Google