Elements in common

Operational plans all have the key components in common:

 

Top

 

The basic model

  1. Define what it is you are supposed to achieve in the project. Mention specific deliverables.
  2. List the main stages of the project.
  3. List the Key Performance Indicators for each stage of the project.
  4. Write a Gantt chart:
    • Show dependencies
    • Show the critical paths
    • Show any float times
  5. Write a list of stakeholders (e.g. clients, area managers, etc.) and say how you will communicate with each one during the planning phase and the project. (Some will be day to day oral reports, some will be phone calls, some will have to be written.) Hint: It might be helpful to make a list of things to need to communicate with each one about.
  6. Make a list of resources you'll need to buy in, whether outsourced services, finance, or things to buy. To do this, you'll have to talk to colleagues who are responsible for each area, or suppliers.
  7. Get costings for each resource and firm them up as much as you can (e.g. use price-list from preferred/contracted suppliers, get written quote, shop around to compare).
  8. Write up a cost schedule (i.e. when you will actually have to pay for things during the project)
    Note: The budget will comprise mostly of firm costings and your cost schedule.
  9. Do a risk management exercise for each stage of the whole project:
    1. Make a list of things what could go wrong
    2. Consider the probability of occurrence
    3. Consider the amount of harm
    4. Assess/calculate the risk
    5. Develop contingency plans for any significant risks
      Note: Keep an eye on risks while the project is running. You may need to develop other contingency plans as you go.
  10. Write up the proposal on a word processor. It needs to be in good English, succinct, and practical. However you may need to include other necessary information (e.g. budget, time estimates, expertise estimates, technical data, etc.) Ask for specialized help if you need it for this information.
  11. Check that any colleagues and work teams understand their role in the plan.
  12. Submit your plan to your supervisor or client for approval. As getting approval is a requirement to continue, you might have to revise the plan and resubmit it to get approval.

See a simple form for an operational plan, and a risk management template.

Top

 

 

A similar model

This one is almost the same as above:

  1. Determine the objective of project
  2. Define the scope of the project (i.e. what's included and what's not)
  3. Define tasks to be done
  4. Identify vulnerable points
  5. Define Critical Success Factors (i.e. things you must get right for the project to succeed)
  6. Execute the plan
  7. Review

 

Top

 

Incoming Information

This one allows for the project manager to continually update the plan according to new information. It presumes that some aspects are outside his/her control:

1. Determine objective of project

New information

2. Define the scope of the project (i.e. what's included and what's not)

New information

3. Define tasks to be done

New information

4. Identify vulnerable points

New information

5. Define Critical Success Factors (I.e. Thing you must get right for the project to succeed)

New information

6. Execute the plan

New information

7. Review

New information

 

Top

 

Multi-site operational plan

A multi-site operational plan is similar but is much more complex because it involves liaison and coordination between the project manager and different site managers all doing different things on their own sites. This kind of plan is important in large building and engineering projects.

 

Annual or monthly plan

Some organizations have an annual operational plan to meet the year's objectives of its strategic business plan.

Some organizations have a monthly operational plan to meet short-term goals that add up to a set of annual goals. This is most common in sales organizations.

 

A flow chart operational plan

A flow chart operational plan allows for choices in case the project manager must make decisions later down the track. It allows for lots of "what if?" situations.

 

Scenario-based plan

This particular plan allows for a particular scenario to arise before taking action. For example, you might not be able to act until you have a forecast of fine weather for a period of five days.

Trigger

Preconditions

Action

Intended outcome

Resources

Top