Project Initiation and Business Environment
Project Initiation and Business Environment
This domain tests why a project exists, how it is authorized, and how organizational and external factors shape it. Expect questions on business cases, benefits, charters, governance, and enterprise environmental factors.
Core rules
- The business case justifies the investment by linking expected benefits to cost, risk, and strategic objectives. A project output is not the same as a benefit; benefits are realized after delivery.
- The project charter authorizes the project and names the project manager. It includes purpose, measurable objectives, high-level scope, risks, milestones, budget, and approval requirements.
- Governance defines decision rights, stage gates, and escalation paths. It keeps the project aligned with strategy and compliance.
- Enterprise environmental factors are external and internal conditions such as regulations, market conditions, culture, and systems. Organizational process assets are plans, templates, procedures, and lessons learned.
- Benefits realization requires an owner, measures, and a handover plan beyond project closure.
Worked example
A project costs $400,000 and promises $120,000 per year for four years. At a 10% discount rate, the present value of benefits is about $380,000, so NPV ≈ −$20,000. The sponsor still wants to proceed for regulatory compliance. Reasoning: the financial case alone is negative, but a mandatory compliance driver can justify the project; the charter should state that driver and the compliance success criterion.
Traps that cost marks
- Starting work before the charter is approved.
- Treating a delivered system as a realized benefit.
- Ignoring regulatory or environmental factors that can invalidate the plan.
- Confusing organizational process assets with enterprise environmental factors.