Project planning fundamentals and the project life cycle
Projects, programs and the life cycle
A project is a temporary, unique endeavour undertaken to produce a defined outcome; operations are ongoing and repetitive. Candidates should distinguish projects from programs (related projects managed together) and portfolios (a collection aligned to strategy). The life cycle normally runs from initiation through planning, execution, monitoring and control, to closure, with phase gates or stage boundaries where go/no-go decisions are made. Planning is iterative, not a single event, and the project charter authorises the work and names the project manager. The classic constraints-scope, time, cost and quality-trade off against each other, while benefits, risk and stakeholder satisfaction also matter.
Traps
Questions often confuse life-cycle phases with process groups: phases are project-specific stages, whereas monitoring and controlling cuts across phases. Another trap is treating closure as optional; administrative closure, acceptance and lessons learned are part of the life cycle. Do not assume a project is successful merely because it finished on time-it must meet agreed requirements and deliver intended benefits. Also watch for “planning is finished at baseline”: baselines are controlled, but replanning through change control continues.
Worked example
A firm plans a customer portal with a fixed launch date. Initiation produces a charter and business case. Planning defines scope, schedule, budget and risks. During execution, testing reveals a security gap. The team does not silently skip testing; it raises a change request and adjusts scope or resources within the date constraint. At closure, the portal is accepted, support is handed over, and lessons are recorded. Rule of thumb: at every gate ask, “Is the business case still valid, is the next phase funded, and are key risks owned?”