Stakeholder Management Plan

SAP BW Tutorial Best Practice on Stakeholder Management Plan [Template]

Table of Contents

The Key Steps To Developing Your Project Stakeholder Management Plan

As a SAP HANA Project Manager, it is important for you to identify each project stakeholder, evaluate that stakeholder, gather their requirements, estimate the time to implement each requirement and also to develop a Stakeholder Management Plan.

In this article, I discuss the importance of identifying Project Stakeholders and how that process naturally leads to several other subsidiary SAP Project Management Plans we recommend you develop.

In addition to the Project Risk Register, the other tool we recommend you immediately start work on is the Stakeholder Management Plan.

Stakeholder Management PlanNail Down Your Stakeholder Management Plan Early to Ensure Project Success

 

10 Critical Chain Project Manager Tips

Learn What is Catch Weight Management

Understanding Embedded Systems vs SAP HANA

 

What is a Stakeholder and why should you have a Stakeholder Management Plan?  A stakeholder is anyone who has an interest in your project.

Three Stakeholder Types

There are at least 3 types of project Stakeholders including:

  • Friendly Stakeholders
  • Neutral  Stakeholders
  • Unfriendly Stakeholders

 

Friendly stakeholders are people who want to see your project succeed. The Project Sponsor can be a friendly stakeholder. The Project Sponsor is responsible for the project concept and for launching the project so they should be the most friendly project stakeholder. Friendly stakeholders have requirements.

 

Friendly Project Stakeholder

There are also unfriendly stakeholders. These are people who don’t want to see change. They could also be people who might want to see you fail or who might try to sabotage your project.  

Unfriendly stakeholders have requirements as well. It is important not to ignore unfriendly stakeholders because they can interfere with your project. It is important to identify unfriendly stakeholders, evaluate their requirements, determine the risks and benefits of their requirements, realize they may always be unfriendly and to devise a containment plan so that you can complete your project successfully, implement their requirements and protect the success of your project from unfriendly stakeholders.

 

Unfriendly Stakeholder 

Don't let the Unfriendly Stakeholders Tie You Down.

Neutral stakeholders are people who are kind of neutral toward the success or failure of your project. From a strategy point of view, when you need more friends on your project, try winning over more of the fence sitting neutral stakeholders to your side.

 

Neutral Project Stakeholder

Neutral Stakeholders Need to Be Persuaded

 

Practice Project Stakeholder Management Best Practices

 

Whether they are friendly, unfriendly or neutral, all stakeholders have requirements.

You should continue to identify stakeholders until no further stakeholders can be identified that will impact your project in one way or another. In any organization, this could take some time and should be an ongoing process. These are your stakeholders and they set your project scope. Everyone and everything else outside the scope is outside your project. Every new request you get after that you have to ask yourself, is this in scope or out of scope. If it is in scope then you need to take care of it. If the new request is out of scope, then save it for the next project.

Stakeholder Influence

Stakeholders have an impact on and affect the following attributes of your project:

  • Requirements
  • Scope
  • Quality
  • Risk
  • Schedule
  • Costs
  • Success
  • Failure

From a project management stand point, Stakeholder Requirements are the most important because requirements drive everything else that happens on your project.

Requirements set the project expectations and deliverables (Project Scope).

Requirements set the expected level of quality for the deliverables which affects overall project costs.

Estimating Project Durations

Your Project Schedule is also determined from the requirements. The time required to implement a particular requirement is estimated and costed based on past experience.

This is not the only method, but is one of the best.

The time estimates for all requirements are then put into a critical path schedule time line. This becomes the project schedule. More on how to do this later.

Some requirement have more inherent risks involved than others perhaps because there are unknown technical challenges to be faced and also because they take longer to implement. All these risks are factored into the overall schedule.

There are several different project duration estimation techniques that I have tried and that work. I will talk more about estimating project durations in a later article.

Project Scope

Overall, implementing the requirements, the scope, of your project is what the project is all about. There are Time Requirements, Schedule Requirements, Cost Requirements and Quality Requirements. These are all forms of project Constraints.

Project Scope 500 wht 8918

Identify the Project Scope

 

I do not recommend that you jump in and start WRICEF development until you have spent some time identifying stakeholders and gathering their requirements.

Ask yourself, how can you implement if you do not know what product or service you are supposed to create?

You can't.

This is where you will run into trouble with the customer.

So if requirements are so important, it becomes important to manage the requirements and in order to do that, you have to manage the stakeholders, otherwise the requirements will be a moving target.

Without managing the stakeholders you can never finish the project because the requirements will be constantly changing.

This is called Scope Creep.

You can’t allow this. You will need to create several additional project management subsidiary management plans.

You need a:

  • Stakeholder management plan
  • Scope management plan
  • Schedule management plan
  • Risk management plan
  • Communications management plan

Is Microsoft Project a Project Management Plan?

As you can see, a project management plan will contain several subsidiary management plans all of which take time to develop (like a few months). It is clear that a list of tasks presented in a Microsoft Project file is not a Project Management Plan.

A lot of people make this mistake.

A Microsoft Project file is simply a task scheduler created as part of an overall Project Management Plan.

There is a time and a place to use Microsoft Project but not until long after the stakeholders have been identified and after the requirements have been identified.

Communications Management Plan

Stakeholders also want and need to know what is going on with the progress of the project. They want to know the project status and where things are at. They want to know hourly, daily and weekly where you are at with the project. So We can identify one additional plan the project manager needs to create:

  • The Communications Management Plan

The Stakeholder management plan drives the requirements gathering process. Requirements drive the project scope. As new stakeholders come and go on the project or the sponsoring organization, all stakeholders will constantly be asking for this or that HOT new requirement and they will want to know what is your promise date and when you can have it done.

Setting proper expectations upfront, getting everyone on the same page with regular communications is important.

Communications Management Plan cell phone pc 400 clr 2321

Communicate with Stakeholders

In this article we have discussed a little bit about the following topics:

  • Risk Register
  • Stakeholder List
  • Stakeholder Types
  • Stakeholder Management Plan
  • Project Scope
  • Scope Management Plan
  • Communications Management Plan
  • Schedule
  • Estimating Project Durations

 

I will discuss each of these topics in further articles as well as provide you with templates and my practical hands on project management tips.  In the meantime, you can download a proven Project Stakeholder Management Plan Template by pressing the button.

 

Download Template  Stakeholder Management Plan

 

People who read this also read: 

How to Use a Project Charter to Start a Project

10 Key SAP BW Project Risk Management Tips

10 Advanced SAP BW Project Estimation Techniques

10 Reasons You Need a SAP Project Review

How You Can Estimate a SAP BW Project in Under 5 Minutes

Download SAP BW Mindmap

Learn what SAP Business Warehouse is and what it does in under five minutes

Get this Mindmap

Doug Ayers

I am an MBA, B.S. in Computer Engineering and certified PMP with over 33 years working experience in software engineering and I like to go dancing after work. I program computers, solve problems, design systems, develop algorithms, crunch numbers (STEM), Manage all kinds of interesting projects, fix the occasional robot or “thing” that’s quit working, build new businesses and develop eCommerce solutions in Shopify, SAP Hybris, Amazon and Walmart. I have been an SAP Consultant for over 10 years. I am Vice-President and Co-Founder of SAP BW Consulting, Inc.

View All Articles by Doug Ayers

The SAP Blog

Subscribe to our blog and receive SAP BW Updates, demand generation, inbound marketing, sales enablement, technology and revenue generation insights and ideas delivered right to your email.