Expectations Management

From apppm
Revision as of 17:50, 1 October 2017 by Gudjon (Talk | contribs)

Jump to: navigation, search

As stated in the The 5th edition of PMBOK from the Project Management Institute (PMI), "It is critical for project success to identify the stakeholders early in the project or phase and to analyze their levels of interest, their individual expectations, as well as their importance and influence." This article will focus on the individual expectations aspect mentioned. To do so, some basic concepts on stakeholder management will be introduced and explained as a basis for the core of the article


How different stakeholders will have different expectations within a project, how these stakeholders need to be categorized based on the interest and influence on the project, and how to successfully manage the expectations of different types of stakeholders.


Different methods and tools on how to align and manage expectations are introduced and explained. Furthermore, those methods are categorized based on when in the process they are relevant and for what type of stakeholder they are relevant. Limitations and weaknesses of each method are examined and suggestions on how to avoid them given.

Contents

Overview

Introduction

Project management is used across the world, in all sectors and industries. Project management is used to improve project results through different stages of the project lifetime.

In the context of project management, expectations management relates to the stakeholders in the project, which then is a concept within the general concept of stakeholder management. ISO 21500 defines a stakeholder as, "Person, group or organization that has interests in, or can affect, be affected by or perceived itself to be affected by, any aspect of the project. [1]. As a project is a temporary endeavor with a defined beginning and end, expectations management is extremely important and needs to be considered from the first phases of a project and through out the project lifetime.

Project stakeholder management was added as the tenth knowledge area in 2013 by the project management institute. [2]. Project stakeholder management was formerly part of the project communication management knowledge area. This shows clearly the increased emphasis being put on stakeholder management in later years. This also suggests that project management is moving more in the direction of stakeholder expectations management and away from managing products and deliverables. Furthermore, recent literature suggests that project success is in large a result of stakeholder management. [3] One could even argue that a project ending up with all the stakeholders happy is a job well done.

As expectations management is different between the different types of stakeholders, a closer look will be taken into stakeholder management to establish the ground.

Identifying the stakeholders of a project is of great importance, especially the ones who are defined as the major stakeholders.

The stakeholder circle is a methodology designed to include stakeholder management in project management. This methodology has the following five steps in terms of stakeholders: Identify, prioritize, visualize, engage and monitor the stakeholders. The first step here is very relevant for this article. Identifying the projects stakeholders and understanding their needs will play a key role in understanding and managing their expectations throughout the project.

The methodology categorizes stakeholders according to directions of influence (002517) These directions are: upwards (senior managers), downwards (the team), sidewards (peers of the PM) and outwards (outside the activity).

the iron triangle of the project environment states that success equals "On time, on budget and delivering the specified scope"

Knowing who the important stakeholders are early in the life of the work, and knowing their expectations, ensures that conflicts can be recognized and addressed proactively.

Application

Expectancy Theory

Expectancy theory was formulated by Victor H. Vroom in the 1960s. This is still today a very popular theory within motivation management, as it focuses on all three parts of the motivation equation: inputs, performance and outcomes. The theory claims that individuals will behave in a certain way based on a desirable outcome, related to that behavior. The theory identifies three major factors determining a persons motivation

  • Expectancy: Links effort to performance as follows: Ones perception on how his or her effort leads to a certain level of performance
  • Instrumentality: Links performance to Outcomes as follows: Ones perception of how a certain level of performance results in attainment of outcomes
  • Valence: How desirable the attained outcomes are to a person

Stakeholder management

Stakeholder inventory

Properly identifying stakeholders of a project early on allows the project manager to allocate his time appropriately between the stakeholders. The focus will be on the tools of the process, whereas the inputs and outputs are scoped out of this article. Three tools commonly used in stakeholder identification are: Stakeholder analysis, expert judgement and Meetings [4] Stakeholder analysis is used to map all the stakeholders of a given project, to do so, qualitative and quantitative information needs to be gathered. This information is then used to evaluate each stakeholder. Stakeholder analysis generally follows three steps. [4].

  • Identify all relevant stakeholders. Key stakeholders should be easy to identify. Identified stakeholders are then interviewed about other possible stakeholders until the list of stakeholders is complete.
  • Analyze stakeholder impact or support. This can be very important in terms of expectations management
  • Assess how key stakeholders are likely to respond in various situations. This is more of an retrospective approach and is intended to prepare the project manager on the best way of dealing with unforeseen problems in the project.

Stakeholder mapping

Figure 01: Stakeholder mapping

This can be mapped in many different ways, the one shown in Figure 1 is a Power/Interest grid


Once the stakeholders have been identified by any of the mentioned methods, they need to be categorized into specific groups. One of the methodology addressing this is the stakeholder circle. [5]. One of the tools represented here is identification, where the stakeholders are split into 4 types from the perspective of the project manager.

  • Upwards: This concerns the Senior managers of the company. Those are the stakeholders that secure the internal commitment of the company to the project. Often these stakeholders have high power over the project without necessarily having so much interest in it. Thus they should be kept satisfied, and if possible, the aim should be to increase their interest in the project to make sure the continued internal support of the project.
  • Downwards: Members of the project team, hence the people doing the actual project work. This group is often overlooked as being important by project management. Typically the group wound end up in the lower right corner of the power/interest grid although fairly high up in that quadrant. Those stakeholders should be kept informed
  • Outwards: This is in most cases the biggest group out of the four and includes all the external stakeholders. Depending on the project this group could include governments, unions, shareholders, customers, suppliers e.c. Because of the versatile nature of this group and the different types of projects it is very difficult to place the group as a whole in any one part of the power/interest grid. Those stakeholders are likely to be spread out over the grid.
  • Sidewards: Peers of the project manager, such as other project managers. this group can generally be placed in the lower left quadrant of the grid, and minimum effort should go into the stakeholders of the group, although it can be beneficial to the project to try and move those stakeholders further to the right to increase the internal drive of the project.

Stakeholder expectations

Clarifying stakeholder expectations at an early stage is very important. The importance of the planning phase of a project is often underestimated. This phase is extremely important in terms of project success. A big part of this planning should be expectations management, identifying what values are important to the key stakeholders and seek out ways of how to deliver them. Expectations of key stakeholders, not planned for, which are discovered later on in the process, can prove both very costly and time consuming, which in return can lead to the snowball effect of the project not being able to meet the expectations of other stakeholders in terms of cost and time. Once the important steps of properly identifying and mapping the stakeholders, the next step is therefor to figure out the expectations of each of the identified stakeholder. This third phase in the stakeholder management process can be quit time consuming, given the fact that stakeholders often don´t have a clear view of their expectations themselves, the first step of this process often is to help stakeholders identify their own expectations. That again means that this phase is very dependent of the project managers personal and communication skills. Even though there are tools available for this process, the project managers soft skills, and his abilities to understand his key stakeholders expectations can prove to be more important than any of them. expectations are often communicated non-verbally and do therefor require certain skills of the project manager. Those people and communication skills can again prove priceless in situations where unexpected and or unforeseen expectations arise later on in the project. In such cases the ability of the project manager to properly communicate and manage the change in the project heavily rely on the mentioned personal and communication skills.

Limitations

  • Stakeholder diversity: Once projects grow in size, especially in terms of stakeholders, it becomes increasingly difficult to satisfy every stakeholder involved. It has been debated for a long time weather the ability to satisfy one stakeholder group always comes at the expense of another stakeholder group or not. More recent studies argue that the following three primary stakeholder groups can be satisfied all at the same time, employees, customers and owners [6]. However, as the number of stakeholder grows within a project, program or portfolio, and even as the 3 mentioned primary stakeholder groups grow, the task of meeting everyone's expectations becomes more and more difficult.
  • Changing priorities:

Annotated bibliography

  • Essentials of Contemporary Management, Sixth Edition - Chapter 9

The Chapter, Motivation, looks at motivation from a general perspective within management. It looks in depth at a few key models and theories within motivation management, and one theory in particular, expectancy theory looks into the relationship between individuals efforts and the individuals believes in those efforts resulting in something desirable for him or her.

References

  1. ISO21500. 2012. Guidance on Project Management. International Organization for Standardization.
  2. Schibi, O. (2014). The expectations manager: The future of project management: The future of project management. Paper presented at PMI® Global Congress 2014—North America, Phoenix, AZ. Newtown Square, PA: Project Management Institute.
  3. Cavarec, Y. B. (n.d.). Revisiting Definition of Project Success. Retrieved September 26, 2016, from http://www.pmi.org/learning/library/revisiting-definition-project-success-6098/
  4. 4.0 4.1 Project Management Institute. (2004). A guide to the project management body of knowledge (PMBOK guide). Newtown Square, Pa: Project Management Institute.
  5. Stakeholder management Retrieved September 22, 2017, from http://www.stakeholdermapping.com/stakeholder-circle-methodology/
  6. Strong, K. C., Ringer, R. C., & Taylor, S. A. (2001). THE rules of stakeholder satisfaction (timeliness, honesty, empathy). Journal of Business Ethics, 32(3), 219–230.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox