Building a Project’s Business Case
By ExecutiveBrief Staff
Forward-looking project managers realize that to avoid failure, they should build the business case for their projects by getting intimately knowledgeable about the reasons why sponsors approved their projects.
Too many projects get the axe because of the lack of business cases that justify their existence. When project sponsors begin to see projects only in terms of costs instead of potential rewards, there are higher chances that the projects would be canceled.
It is not the job of the project manager to build the business case. Ideally, project stakeholders and sponsors evaluate the business value and possible ROI from a project. If the project is seen in terms of generating income or reducing cost, the project will have the green light. This is the situation in the ideal world, but this scenario happens a lot less than one would like to believe.
Forward-looking project managers realize that to avoid failure, they should build the business case for their projects by getting intimately knowledgeable about the reasons why sponsors approved their projects. A project manager should work closely with clients, sponsors and other stakeholders, and ask the following questions:
What problems should the project address?
By interviewing project sponsors, the project manager can determine their goals and discuss the issues that the project would solve. In addition to project sponsors, the ones who are dealing with the issues at the workplace, perhaps on a daily basis, are a good source of ideas about the extent and many facets of the problem. Looking at day-to-day challenges from end-users’ point of view enables the project manager to get a better handle of the requirements of the project in terms of design and technical upgrades, as well as in terms of how it will solve end-user problems.
What are the strategic goals of the project?
Is it an easier system? Increased productivity? Better networking? Conversion to a marketable product? No matter what it the goals are, they must also come from and supported by the end-users. At the end of the day, it will all boil down to the business value of the project. And by business value, it means cost reduction, better productivity, and the possibility of selling the product or service to the wider public. Make sure that the goals are clear and the project’s objectives must reflect these goals.
What are the project’s basic requirements and what can end-users live without?
Aside from building the requirements based on the needs of its users, the project manager should also build the projects’ technical and design requirements and ask what bells and whistles it should have. The project may have a lot of feature that do not have business justifications, resulting in features that took too long to build. Separating needs from fluff allows the project manager to formulate requirements, identify scope, and allocate resources that are important in creating a working version of the project. The quicker the iteration, the better the chances are of project survival.
What is the project’s ROI?
Even at the early stage of the project, it is possible to envision ballpark ROI figures. Because all projects incur costs, a project manager should have a fair idea of when investments will be recovered and generate positive cash flow.
© ExecutiveBrief 2008
ExecutiveBrief, the technology management resource for business leaders, offers articles loaded with proven tips, techniques, and action plans that companies can use to better manage people, processes and tools – the keys to improving their business performance.
To learn more, please visit: http://www.executivebrief.com.