4.1 Business Case, Feasibility & Project Charter

The initiation phase of a project is the critical starting point where an idea is transformed into a formal undertaking. It's the phase where organizations decide whether a project is worth the investment of time, money, and resources. Rushing or skipping this phase is a common cause of project failure, leading to misaligned objectives, cost overruns, and ultimately, a cancelled project. During initiation, the groundwork is laid that will dictate the trajectory of the entire lifecycle.

The Business Case

A Business Case is a formal document that provides the justification for undertaking a project, program, or portfolio. It answers the fundamental question: Why are we doing this? Because organizations have finite resources, every potential project must compete for funding and executive support. The business case evaluates the benefit, cost, and risk of alternative options and provides a rationale for the preferred solution.

Components of a Business Case typically include:

• Problem or Opportunity Statement: Clearly defines the business problem that needs solving or the opportunity that can be capitalized on. It sets the context for why action is needed now.
• Strategic Alignment: Demonstrates how the proposed project aligns with the organization's overarching strategic goals and vision. If a project does not align with the company's long-term objectives, it should not be approved, regardless of how profitable it might seem.
• Analysis of Alternatives: Details the various options considered, including the 'do-nothing' baseline scenario, to prove that the recommended approach is the optimal one.
• Cost-Benefit Analysis: The financial justification comparing the expected costs against the anticipated benefits over a specified period.

Feasibility Metrics

To truly evaluate the financial viability of a project within the business case, project managers and business analysts rely on specific feasibility metrics. For PK0-005, return on investment is explicitly named; other financial measures below provide useful comparison context.

• Return on Investment (ROI): A performance measure used to evaluate the efficiency of an investment. It is calculated by dividing the net profit of the investment by its cost. A higher ROI indicates a more profitable project.
• Net Present Value (NPV): This is the difference between the present value of cash inflows and the present value of cash outflows over a period of time. NPV accounts for the time value of money, meaning a dollar today is worth more than a dollar tomorrow due to inflation and investment potential. Rule of thumb: If the NPV is positive, the project is generally considered financially acceptable. When choosing between multiple projects, a higher NPV is generally preferred when NPV is the stated decision criterion and assumptions are comparable.
• Payback Period: The amount of time required for an investment to generate cash flows sufficient to recover its initial cost. For example, if a project costs $100,000 and generates $25,000 a year in savings, the payback period is four years. Generally, organizations prefer shorter payback periods, as they represent less risk and a quicker return of capital.
• Internal Rate of Return (IRR): The discount rate that makes the NPV of all cash flows from a particular project equal to zero. You don't need to calculate IRR on the exam, but you must know that a higher IRR is generally preferred when the projects have comparable risk and IRR is the stated criterion.

Exam Trap: Pay close attention to the wording in scenario questions. If a question asks which project to choose based on financial metrics, apply the metric named in the question while also respecting stated risk, compliance, and strategic constraints. If deciding based on Payback Period, select the project with the shortest time frame.

Feasibility Studies (TELOS)

While financial metrics determine if a project makes monetary sense, a Feasibility Study determines if the project is practically achievable. The TELOS framework is a highly effective way to assess overall feasibility across multiple dimensions:

The Project Charter

If the business case and feasibility studies are approved, the project moves to formal authorization via the Project Charter. This is a foundational document issued by the project sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.

Without a signed project charter, a project does not officially exist, and the project manager has no formal authority to spend money or assign tasks. It is the PM's mandate.

Key Components of the Project Charter:

• Project Purpose or Justification: A high-level summary of the business case.
• High-Level Scope and Objectives: Broad statements defining what the project will achieve. Detailed scope, WBS, and requirements come later in the planning phase.
• High-Level Requirements: The essential conditions or capabilities that must be met for the project to be considered successful.
• High-Level Risks: Initial assumptions and major threats that could impact the project early on.
• Summary Milestone Schedule: A very high-level timeline showing major deliverables and their estimated completion dates.
• Pre-approved Financial Resources: The initial budget allocation committed to the project.
• Project Manager Assignment and Authority Level: Explicitly names the project manager and defines their decision-making authority, staffing authority, and budget management limits.
• Sponsor Approval: The signature of the project sponsor, who champions the project and provides the funding.

The Project Sponsor vs. Project Manager

Understanding the distinct roles of the sponsor and the PM during initiation is highly testable. The Project Sponsor is typically an executive or senior manager with a vested interest in the project's success. They authorize the charter, secure funding, champion the project to other executives, and act as an escalation point for issues beyond the PM's control.

The Project Manager is responsible for the day-to-day execution, leading the team, and achieving the project objectives. The charter formally authorizes the project and the project manager's use of organizational resources. If a PM starts executing tasks before the charter is signed, they are acting outside of their authority and risking organizational resources on an unapproved endeavor.

In summary, the initiation phase establishes the "why" and "what" of a project. The business case provides the critical justification, comprehensive feasibility studies prove it can realistically be done, and the project charter formally authorizes the work to begin. Skipping these essential steps leads to inevitable scope creep, budget overruns, and widespread stakeholder dissatisfaction.

Discovery and Concept Artifacts

Before initiation, compare the current state with the desired future state and quantify the reason for change. A business case may use ROI, but it also needs the objective, benefits, assumptions, risks, and strategic fit.

Discovery may begin with a prequalified vendor, a predetermined client, or preexisting contracts. Read the client statement of work (SOW) and terms of reference (TOR) before inventing new scope: they may already define deliverables, authority, constraints, and acceptance expectations. Identify whether spending is capital expenditure (CapEx) for an asset with longer-term value or operational expenditure (OpEx) for ongoing consumption or service; cloud and subscription choices can change that classification under the organization’s accounting policy.

Initiation Activities Beyond the Charter

Initiation also identifies and assesses stakeholders, creates a RAM such as RACI, establishes accepted communication channels, and develops a records-management plan for project data and documents. Define access requirements using least privilege, review existing artifacts rather than duplicating them, determine the initial solution design, and conduct an appropriate kickoff. The charter’s objectives, success criteria, and preliminary scope guide these activities, but detailed planning follows after authorization.