Chasing the Number

Forecasting is easy, but doing it well is hard. I am talking about financial forecasting that is required of project managers engaged in the business of delivering professional services.

Before we get into how to forecast, let’s look at why we forecast. It is an essential part of managing the flow of business activities aimed at achieving a goal that has been set. The idea is to look into the near term future and make an informed guess as to the billable milestones that will be achieved by a certain date. If the forecast deviates too far from the goal, you and management will have the opportunity to take action to put things back on track.

It also is used to set expectations for income, which can be very important to stock performance (I have a special rant related to this but won’t go into it in this post). Since we are setting expectations, we better make sure we achieve those expectations or else we will find ourselves in an unpleasant situation.

Now that we know why we make forecasts, let’s see how it is done.

As I said at the beginning, forecasting is easy. You assign a number to a date and you have a forecast — easy. But how do you know it is the right number and the right date. That is the hard part. It is hard because we are making guesses and guesses are easily influenced by our internal desire to make the goal setters happy by giving them the number requested. But if we don’t know if the number given is going to happen, everyone could be in a world of hurt when the goal date arrives. This is a case of trading near term happiness for long-term sorrow later.

The key to giving accurate forecasts is to have a set of rules to follow that help keep emotions out of the equation. This will also make forecasting much less stressful. Here is what I do that has worked fairly well for me so far.

  1. All milestones start out with a forecast that puts them beyond the current forecasting period, such as the next quarter or even next year.
  2. Once a milestone has been planned and scheduled you can then assign a completion date that you will have some confidence in actually happening.
  3. Modify your forecast every time you complete a status call or receive new information relating to the schedule.

Following these three rules will make forecasting easier, more accurate and less stressful. Of course it may not make life pleasant if the number you are forecasting does not meet the desired goals. But actually, that is a good thing since the whole point of forecasting is to allow management a chance to take action to achieve the goal before it is too late. By following the rules above you are making fact based guesses that are supportable and defensible because they are based on solid information. The same is true for changes made in the forecast since as circumstances change so does the likelihood of achieving the goal.

Using fact based forecasting methods is the only way to do it. You have to not let the pressure from the person who sets the goals drive you into giving a number that cannot be supported by facts. Following the rules will keep you on track. As you develop a reputation for having accurate forecasts, your value to the company will rise and you will have pride in how you deliver.

Work at Risk Projects

In the professional services world there is a euphemism called “working at risk” which means that you do not have a signed SOW or contract or even a PO. You are running a project without an agreement on scope or goals, no defined budget and no authority to expend resources or bill for them.

Before I get into talking about how this comes about and how to deal with it, let’s understand the importance of a signed document defining the project. In professional services (“PS”), we are usually talking about a Statement of Work (“SOW”). This document does several things:

  1. Defines the scope of the project.
  2. Defines the roles and responsibilities of both the receiver and the provider of services.
  3. Establishes a budget for the work and terms and conditions to control that budget.
  4. Defines the milestones at which payment is to be received and what criteria for success is needed to meet those milestones.

A document with all these things, agreed to by both parties through legally binding signatures, provide the PMO and the assigned PM the authority to perform work. It also provides guidance on the scope of the work to be performed as well as giving all parties a way of determining when a change order is required. A well written SOW is the first step in having a successful project which will result in an outcome that will provide satisfaction for all stakeholders.

With that said, why would anybody deliver services without a signed SOW? I have been thrown into this situation a number of times over the years. In my experience, this will work without major problems about half the time if certain characteristics are present. Some of them are:

  • It is a good customer that has an emergency situation and there is not time to complete the paperwork before starting the services. The paperwork comes shortly after work begins. I find this situation fairly low risk.
  • The opportunity for current and future work and sales are large and upper management from both sides have come to verbal agreements through direct contact with each other. The risk in this situation is a bit higher but you will have authorities from both sides that you can engage to help keep thing on track.

Work at risks projects that do not have at least one of these characteristics have a high degree of risk and should be avoided at all costs. You as the PM should make it known from the very beginning that proceeding is very risky and not recommended. Make sure these opinions are in writing or some other audit trail such as email. This is not only a CYA strategy, but is also your duty as a PM to let stakeholders know when you see problems with a project.

Ok, so despite all your efforts, you are assigned to a project that is a work at risk situation. What do you do about it?

The very first thing you need to do is work with the customer to define the work to be done. This will give you a scope that you can manage against and allow plans to be made. If the customer does not want to go through a planning stage or provide metrics to gauge success then you need to shut the project down until agreement is reached. Continuing to move ahead without a plan will not bring satisfaction to anyone and can do great damage to your own organization’s reputation, costing you future business.

The fact that a budget has never been established requires that you keep track of hours worked and expenses incurred and report them weekly. Make sure you negotiate a time and materials billing approach since you have no definition of billing milestones.

You will have a larger task of documenting all decisions in greater detail. Make sure your meeting minutes are more detailed and they are published to the whole team. Obtain agreement often on progress made and publish that as well. There is no such thing as over communication in a work at risk project.

Hopefully, this post will help you avoid work at risk projects or at the very least give you some strategies for dealing with them. Let me know your thoughts on this post or any of my other posts.

The Changing Role of PS in the Cloud World

IT departments are starting to change the way they provide services to their users. We are seeing more adoption of SaaS delivery of applications and moving servers and storage to offsite providers like AWS, RackSpace, Drop Box, Box, etc. The reasons revolve around economics and flexibility. Lower to non-existent up front capital costs, lower cost of ownership and the ability to expand or contract compute and storage resources as needed, quickly and easily.

All of this change will have an affect on what IT related PS is delivered and how that delivery is made.

Continue reading The Changing Role of PS in the Cloud World

What is IT Professional Services

In the world of Information Technology (“IT”), Professional Services (“PS”) generally refers to services that are delivered by a person(s) who is a specialist in a technical arena. This is a broad category, as well it should be, given the great variety of  technologies in use and how they are applied in any IT department. It is because of this great variety that there is a need for PS.
Continue reading What is IT Professional Services