8.1 Project Fundamentals, Governance & Life Cycle
Key Takeaways
A project is a temporary endeavor undertaken to create a unique product, service, or result, fundamentally distinct from ongoing, repetitive operational processes.
Project management includes Initiating, Planning, Executing, Monitoring and Controlling, and Closing process groups; monitoring overlaps delivery rather than following it as a separate sequential life-cycle phase, governed by formal stage-gates to prevent sunk cost escalation.
The Triple Constraint (Iron Triangle) balances Scope, Time, and Cost bounded by Quality; altering any single parameter inevitably forces trade-offs among the remaining dimensions.
Robust enterprise project governance establishes explicit accountabilities across the Project Sponsor (business case ownership and funding), Steering Committee (strategic oversight), Project Manager (operational execution), and Project Management Office (PMO standards and assurance).
8.1 Project Fundamentals, Governance & Life Cycle
In strategic management accounting (SMA), projects are the primary vehicle for executing capital investments, organizational change, and competitive strategy. Management accountants evaluate business cases, design stage-gate governance, monitor cost baselines, and ensure capital creates enterprise value.
Defining Projects vs. Ongoing Operations
A core distinction in management accounting exists between capital projects and ongoing operations:
- Project: A temporary endeavor undertaken to create a unique product, service, or result, with defined start and completion dates, a dedicated budget, a cross-functional team, and specific strategic deliverables.
- Ongoing Operations: Repetitive activities sustaining baseline business functionality, organized along permanent functional lines and focused on process standardization, operational efficiency, and marginal cost control.
| Dimension | Capital Projects | Ongoing Operations |
|---|---|---|
| Objective | Drive strategic change, capability, or asset creation | Sustain baseline revenue and process efficiency |
| Timeframe | Temporary with finite start and completion dates | Continuous, indefinite, and cyclical |
| Work Structure | Unique, cross-functional project teams | Repetitive, standardized functional silos |
| Risk Profile | High uncertainty, assumption sensitivity, volatility | Predictable routines, lower operational volatility |
| Accounting | Project expenditure capitalised only when recognition criteria are met; other expenditure is expensed | OpEx expensed as incurred in current period |
| Control Focus | Stage-gate reviews, EVM, formal scope controls | Variance analysis against budgets and forecasts |
The Project Life Cycle and Stage-Gate Governance
One useful predictive management structure uses the following process groups, with execution and control overlapping. Project-specific life-cycle phases may differ and can be governed by Stage-Gate Reviews—formal executive checkpoints where forward-looking viability is evaluated:
- Initiation: Articulates strategic rationale, designates Sponsor and PM, and issues the authorized Project Charter.
- Planning: Defines the baseline blueprint: Work Breakdown Structure (WBS), schedules, cost baselines, risk registers, and procurement strategies in the Project Management Plan (PMP).
- Execution: Directs teams and vendors to build deliverables, consuming the majority of project CapEx and labor.
- Monitoring & Controlling: Tracks baseline progress using EVM metrics (Cost Variance , Schedule Variance ), enforcing change controls when variances breach tolerances.
- Closure: Secures client handover, archives contracts, releases staff, and conducts a Post-Implementation Review (PIR) at a timing chosen to observe the intended benefits to audit realized benefits.
Important
Stage-Gate Authority: At each gate, the executive committee possesses four options: Go (advance with funding), Kill (terminate project), Hold (pause pending clarity), or Recycle (rework deliverables). Stage-gates prevent the sunk cost fallacy, ensuring unrecoverable past outlays do not justify ongoing capital misallocation.
The Triple Constraint and Scope Creep
Every project is bounded by the Triple Constraint: Scope, Time, and Cost, enclosing Quality. These parameters are strictly interdependent:
- Compressing delivery (Time) requires adding overtime (Cost rises) or removing features (Scope falls).
- Expanding features (Scope expands) requires deadline extensions (Time rises), budget expansion (Cost rises), or compromised testing (Quality falls).
Mitigating Scope Creep
Scope Creep is the unauthorized addition of features without adjustments to time, cost, or resources. Caused by vague specifications, executive whims, or developer "gold plating," scope creep derails schedules and destroys returns. Management accountants enforce formal Change Control Procedures (CCPs):
- Modifications require a written Project Change Request (PCR).
- The accountant and PM model incremental cost, schedule delay, and risk.
- The Steering Committee approves or rejects the change; approved changes update official cost and schedule baselines.
Project Governance Framework and Roles
Project governance separates operational execution from strategic oversight and capital allocation:
| Governance Role | Core Responsibilities | Decision Authority | Strategic Focus |
|---|---|---|---|
| Project Sponsor | Owns business case, secures capital funding | Approves charter, funding, phase transitions | Value creation and benefits realization |
| Steering Committee | Cross-functional oversight, resolves conflicts | Approves scope/budget changes beyond tolerances | Strategic alignment and corporate risk |
| Project Manager | Directs daily execution, manages vendors | Manages tasks and budget within baselines | Delivering approved scope on time and budget |
| PMO | Sets methodologies, governance assurance | Enforces reporting standards and audits | Methodology rigor and portfolio visibility |
Core Project Documentation
- Project Charter: Authorized by the Sponsor, establishing the project mandate and granting the PM authority to deploy resources.
- Business Case: Foundational justification articulating strategic fit, options appraisal, risk analysis, financial metrics (NPV, IRR), and the Benefits Realization Plan (BRP).
- Project Management Plan (PMP): Master baseline integrating subsidiary plans: scope (WBS), schedule, cost baseline, risk register, and quality assurance.
Corporate Application: Orion HealthTech Enterprise ERP Implementation
Orion HealthTech Ltd approved a $4,500,000 budget and 14-month schedule for an enterprise ERP system. At Month 7, functional heads submitted 68 custom modification requests directly to software vendors. Consultants projected these customizations would add $1,800,000 in costs and 7 months in schedule delays.
The management accountant and PMO intervened via stage-gate change control:
- Mandatory Regulatory Filter: 8 requests addressed mandatory Therapeutic Goods Administration (TGA) tracking compliance. Cost: $220,000; schedule impact: 1 month.
- Cosmetic Convenience Filter: 60 requests were non-essential cosmetic changes requested by staff resisting standardized workflows. Cost: $1,580,000; schedule impact: 6 months.
The Steering Committee approved the $220,000 regulatory change (setting baseline to $4,720,000 and 15 months) and rejected the 60 cosmetic requests. Orion successfully deployed the ERP on schedule, preserving $1,580,000 in cash.
Exam Watch & Strategic Traps
Warning
Sponsor vs. Project Manager Accountability: The Project Manager is accountable for delivery within approved baselines. The Project Sponsor retains ultimate accountability for the business case and commercial benefits realization.
Note
The Sunk Cost Trap: In stage-gate reviews, historical expenditures are irrecoverable sunk costs. Governance decisions must evaluate only forward-looking incremental cash flows and strategic relevance.
A project team faced with an unnegotiable completion deadline and a fixed budget is asked by senior management to incorporate significant additional software functionalities. According to the Triple Constraint (Iron Triangle), what is the most likely consequence if neither time nor budget is expanded?
Project risks will decrease due to higher functional utilization
Total project costs will automatically decline through economies of scale
Project quality will deteriorate as testing, architectural rigor, and verification are compromised
The project will transition automatically into ongoing operational status
In a formal enterprise project governance structure, who retains ultimate commercial accountability for the project business case and the realization of intended strategic benefits?
The Project Sponsor
The Project Manager
The Project Management Office (PMO) Director
The Lead Technical Systems Architect
During a stage-gate review at the end of the Planning phase, a steering committee discovers that market conditions have deteriorated significantly, making the remaining discretionary investment’s NPV negative relative to cancellation, after including all exit costs and strategic consequences; there is no legal or safety obligation to continue. Sunk initiation costs already stand at $800,000. What is the strategically sound governance action?
Authorize execution immediately to prevent the $800,000 initiation expenditure from being wasted
Terminate the project immediately, recognizing the $800,000 as an irrecoverable sunk cost that should not influence forward-looking resource allocation
Capitalize the $800,000 as an intangible asset and extend the project timeline to delay reporting the loss
Transfer the project to the PMO to remove financial oversight requirements
Sections you finish are checked off in the contents.