Do You Use Business Cases to Justify Your Projects?

Before a project is started, there should always be a business case. Without a business case that defines the problem(s) you are trying to solve and what success looks like, your project will start on very shaky ground.

Rule # 1 -  the business case is always written by the organization receiving the benefits.

A business case is nothing more than a story. As you begin to write your story one of the first things to define is the benefits (the value) the product(s) of the business case will bring. These value statements should be specific, brief, clear, and measurable.

Here are some basic questions that must always be answered when developing a business case. They are:

What is the problem you are trying to solve? What are the gaps between where you are and where you want to go? What are the assumptions? What will it cost?

What is the ROI (Return on Investment) and how long will it take to recoup the investment?

When did the problem first appear? How long has it been happening? What is it costing you?

Where is the problem occurring?

Who is impacted?

Why is there a problem? What is causing the problem and what is the effect? Why is a change needed now to address the problem? How big is the problem?

How will solving or minimizing the problem save money or add value? How will you measure the value?

Are the business case’s benefits worth it? Are they realistic?  Are there alternative solutions that would cost less?

There are many more questions to be answered when developing a business case, however answering the questions above will get you off to a good start.

Project Communications Planning

Project Communications Planning is a process that is continuous throughout a project. When building your initial Project Communications plan focus on the following:

Define Your Audiences - Who needs to know What, and When and How do they need to know it. Communication needs and audiences will change as the project moves forward. Plan for it.

Start from the Top and Work Your Way Down the Chain - Start your Communications with the highest levels of the organization first, then work your way down to the team members. Repeat this cycle.

Target Your Message to the Different Groups - Different groups (and sometimes individuals) may require different types of communications media (e-mail, status reports, web site, face-to-face, memo, etc.). Plan for these different types of communications vehicles up front.

Define Roles and Responsibilities - Ensure that your Project Communications Plan includes Roles and Responsibilities for key stakeholders.

Status Reports - Status Reports are a great form of Project Communication if kept short and to the point.

Repetitive Messages will be Required - The same message delivered using different mechanisms and sources will help to reinforce your message.

Anticipate Conflict - Tailor your communications to overcome Conflict before it occurs. Keep in mind that Conflict will always occur on a project. Conflict needs to be anticipated and managed continuously throughout the project.

Allow for Anonymous Feedback - Create a way for people to relay their positive and negative feedback anonymously.

Project Managers need to recognize that good communication is important because it helps to reduce conflict, increases information distribution, and helps to silence critics while reinforcing the positive aspects of your project.

Get the Right Talent on Your Team

Years ago I managed a large group of software engineers. At the time, it was very difficult to recruit software engineers from here in the United States, so we started sponsoring talent from overseas (China, Russia, India, etc.) and bringing them here to work.  When the economy recovers the IT sector may again have to look overseas to fill many software developer and IT vacancies. There just aren’t computer science majors coming out of American universities to satisfy the current and upcoming demand.

My point is corporations will either have to outsource IT jobs to other countries or look to bring in talent from other countries using an immigration lawyer if they can’t find the right talent within our own borders. The same principles apply to your project teams. If you don’t have the right talent in your company for your project team, consider looking to outside contractors or consultants to fill these roles.

I believe that outsourcing jobs overseas or bringing in workers from outside your borders shouldn’t occur except as a last resort. Having said that, I also realize that companies can’t grow if they can’t hire the right talent.  Never settle for what is available when staffing your project teams. If you can’t find what you need within your company don’t be afraid to look externally. The job you save may be your own.