Defining a Problem Escalation Strategy

,

Something has happened that put the project plan at risk. Late shipments from suppliers, equipment malfunctions, sickness, random acts of nature, resignations, priority changes, errors, and a host of other factors can lead to problems that affect deliverables, deliverable schedules, and resource schedules. The project team owns the problem and must find a solution.

This situation is very different for the project manager than the case of a change request. When a change request has been made, the project manager has some leverage with the client. The client wants something and might be willing to negotiate to an acceptable resolution. That is not the case when a problem arises on the project team. The project manager does not have any leverage and is in a much more difficult position.

When the unplanned happens, the project manager needs to determine who owns the problem and the extent of the problem, and then take the appropriate corrective measures. Those measures often include helping the owner of the problem find an acceptable solution following the escalation hierarchy discussed later in this chapter. Minor variations from the plan will occur and may not require corrective measures. There are degrees of corrective measures available to the project manager: In trying to resolve a problem, the project manager begins at the top of the escalation hierarchy and works down the hierarchy, examining each option until one is found that solves the problem.

There are three levels of escalation strategy: project team–based, resource manager–based, and client-based.

Project Manager–Based Strategies

If the problem occurs within a non–critical-path activity, it can be resolved by using available slack, which is defined in Chapter 5. One example is to reschedule the activity later in its ES–LF window or extend the duration to use some of the available slack. Note that this strategy does not affect any other activities in the project. By using slack, you affect the resource schedule for all activities that have this activity as a predecessor. Another approach is to continue the schedule compression techniques employed in defining the original project plan. This strategy can affect resource schedules just as in the prior case. The last option open to you is to consider the resource pool under your control as the project manager. Can some resources be reassigned from non–critical-path activities to assist with the problem activity?

Resource Manager–Based Strategies

After you have exhausted all the options under your control as the project manager, it is time to turn to the resource managers for additional help. This help may take the form of additional resources or rescheduling of already committed resources. Expect to make a trade-off here. For example, you might be accommodated now, but at the sacrifice of later activities in the project. At least you have bought some time to resolve the downstream problem that will be created by solving this upstream problem. If you have other projects that you are currently managing, some trades across projects may solve the problem.

Client-Based Strategies

When all else fails, you will have to approach the client. The first option would be to consider any multiple-release strategies. Delivering some functionality ahead of schedule and the balance later than planned may be a good starting point. The last resort is to ask for an extension of time. This may not be as unpleasant as it seems because the client's schedule may have also slipped and the client may be relieved to have a delay in your deliverable schedule, too.

The Escalation Strategy Hierarchy

The problem escalation strategy presented here is based on the premise that you, as the project manager, will try to solve the problem with the resources that you control. Failing to do that, you can appeal to your resource managers. As a last resort, you can appeal to the client.

One thing to note here that is very different from the change request situation discussed previously is the leverage to negotiate. As mentioned, you, as the project manager, have leverage when the client has requested a change, but no leverage when you have a project problem to solve. The client has nothing to gain and is therefore less likely to be cooperative. In most cases, the problem can be reduced to how to recover lost time. The following six outcomes are possible to this problem situation:

No action required (Schedule slack will correct the problem) — In this case, the slippage involved a non–critical-path activity and it will self-correct.

Examine FS dependencies for schedule compression opportunities — Recall that you originally compressed the schedule to accommodate the requested project completion date by changing FS dependencies to SS dependencies. You should use that same strategy again. The project schedule will have changed several times since work began, and there may be several new opportunities to accomplish further compression and solve the current problem.

Reassign resources from non–critical-path activities to correct the slippage — Up to a point, you control the resources assigned to this project and others that you manage. You may be able to reassign resources from non–critical-path activities to the activities that have slipped. These non–critical-path activities may be in the same project in which the slippage occurred or they may be in another project that you manage.

Negotiate additional resources — Having exhausted all of the resources that you control, you need to turn to the resource managers as the next strategy. To recoup the lost time, you need additional resources. These resources may come in the form of added staff or dollars to acquire contract help.

Negotiate multiple release strategies — This strategy involves the client. Just as in the case of a change request, you can use a multiple-release strategy to your advantage. An example will illustrate the strategy: The project manager shares the problem with the client and then asks for the client to prioritize the features requested in the project plan. The project manager then offers to provide the highest-priority features ahead of their scheduled delivery date and the remaining priorities later than the scheduled delivery date. In other words, the project manager gains an extended delivery schedule, but gives the client something better than the original bargain offered — namely, something ahead of schedule.

Request a schedule extension from the client — This is the final alternative. Although it's similar to the multiple-release strategy, it offers the client nothing in trade. The slippage is such that the only resolution is to ask for a time extension.

You, as the project manager, should try to solve the problem by starting at the top of this list of six outcomes and working down until a solution is found. By using this approach, you will first try to solve the problem with resources that you control, then with resources that the resource managers control, and finally with resources and constraints that the client controls.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.145.90.26