Business Case and Feasibility Analysis in IT Project Governance
CISA · Information Systems Acquisition, Development and Implementation · By Super Admin
Learn how business cases and feasibility analyses are developed, evaluated, and used to govern IT project decisions throughout the project lifecycle.
The Purpose of a Business Case in IT Projects
Before any IT project is permitted to begin, a business case for the project is developed. The purpose of a business case is to explain the benefits to the business that will be realized as a result of the project. This requirement reflects the foundational principle that IT exists in support of business objectives, meaning every IT project should directly or indirectly result in tangible business benefits, regardless of how technical or abstract the project may be.
The development of a business case will normally follow a feasibility study. A feasibility analysis defines the business problem and describes potential solutions. It is possible, however, that none of the solutions will result in a benefit for the business — for example, each may be too costly or may incur excessive risk. The business case should go beyond the feasibility analysis in terms of business benefits and include actual figures for costs and benefits, making it a more complete and actionable document.
Components of a Typical Business Case
A typical business case is a written document that includes several defined components. The business problem section provides a description of the business problem in qualitative and quantitative terms. The feasibility analysis results section includes the results of the feasibility analysis if one was performed. A high-level project plan is also included, covering a timeline and the number of persons required to execute the project.
Additional components include a budget that covers the cost to execute the project as well as costs associated with the solution, and a metrics section that describes how business benefit will be measured, along with expected before-and-after measurements. Estimates in the metrics section should be backed up by examples of the benefits of similar projects in the organization or in other organizations. The business case also includes a risks section that describes any risks that may occur and how those risks can be mitigated, including market risks or financial risks.
Objectivity and Ongoing Evaluation of the Business Case
Some organizations make the development of a business case the first phase in the actual project; however, this arrangement may be self-serving, as the project team may take the point of view of justifying the continuation of the project instead of focusing on whether the project will actually benefit the business. The development of a business case should be performed in an objective manner by persons who do not benefit from the result. This separation of interest is a key governance control that auditors should look for when reviewing project initiation processes.
The start of a project is not the only time to assess the project's business case. At key milestones throughout the project, the business case should be reevaluated. As a project unfolds, situations often develop that could not be anticipated earlier, and these situations sometimes result in added risks, costs, or other changes. For this reason, the business case should be reconsidered throughout the project so that senior management can determine whether or not the project should continue.
Decision-Making Authority and Stakeholder Objectivity
Decisions on whether to continue a project should be made not only by those people who benefit from the project, but also by other stakeholders who can be more objective. Otherwise, there is a risk that projects will be continued for their own sake instead of for the good of the business. This principle underscores the importance of broad stakeholder involvement in project governance decisions, particularly at major milestones where continuation decisions are made.
If key metrics are not being measured at the time a project begins, those measurements should begin as soon as possible so that the organization will have enough before-and-after metrics to determine whether the project has benefited the organization. An organization that does not agree on key metrics is in danger of setting self-fulfilling metrics later on as a way of justifying the project, regardless of whether it actually benefits the organization. This risk of post-hoc justification is a governance failure that auditors are specifically positioned to identify and flag.
Key takeaways
- A business case must be developed before any IT project begins, explaining the business benefits that will be realized.
- A feasibility analysis defines the business problem and describes potential solutions, and the business case should go beyond it to include actual cost and benefit figures.
- The business case should be reevaluated at key milestones throughout the project, not just at the start.
- Business case development should be performed by persons who do not benefit from the result to ensure objectivity.
Discussion (0)
No discussion on this article yet — be the first to comment.
Please sign in to join the discussion.