1 Project Management Foundations
Learn how projects differ from ongoing operations, how life cycles and delivery approaches organize project work, and how governance and project managers support delivery and oversight.
Projects and organizational aims
A is a temporary, organized effort with a beginning and an end, undertaken to create a distinct product, service, or result. Its deliverable may continue to be used after the ends. This distinguishes a from , which are ongoing activities that sustain an organization. Designing a new customer portal is a ; operating and maintaining it after launch is generally ongoing work.
applies knowledge, skills, tools, and techniques to activities to achieve intended objectives and value. It brings people and work together while balancing scope, time, cost, quality, benefits, and risk. The methods used depend on the ’s context; no single life-cycle model suits every .
Projects may be undertaken on their own or within a or . A coordinates related work to achieve broader benefits, while a groups and prioritizes initiatives in support of organizational strategy. connects delivery of a particular with these wider organizational aims.
Organizing work through a life cycle
A is the sequence of phases a passes through from start to completion. Phases organize related work, provide opportunities to review progress and confirm direction, and support decisions about whether to proceed. Common phase names include feasibility, design, delivery, and closure, but organizations tailor phase structures to the work’s type and complexity.
A simple life cycle may include these broad activities:
Initiation: Clarify the need or opportunity, intended outcomes, and initial feasibility; authorize the and establish its leadership.
Planning: Develop an approach for delivering the work, including objectives, responsibilities, schedule, resources, and controls.
Delivery: Carry out and coordinate planned work, monitor progress, address issues, and manage approved changes.
Closure: Confirm acceptance of deliverables, complete handover, close remaining work, and capture useful learning.
These activities are not necessarily a rigid sequence. Planning and delivery may overlap or repeat, and phases can be divided into stages. At a , authorized people review evidence and decide whether to continue, revise, pause, or stop the work. The life cycle therefore helps structure both delivery and oversight.
Choosing how to deliver
A describes how the solution is developed and delivered; the life cycle describes how work is organized over time. The approach should be chosen to fit the rather than applied as a universal rule.
A defines much of the work in advance. It is useful when requirements are stable and major changes are costly.
An develops the solution through repeated feedback and adjustment. It can help when needs are uncertain or likely to evolve.
Iterative and incremental approaches refine or add to a solution in cycles.
Hybrid approaches combine practices from different models.
A construction may use a largely because design, safety, and procurement decisions must be coordinated before building. A team developing a new digital service may deliver small usable increments and refine features using feedback. Both still need clear objectives, accountable decisions, and appropriate oversight.
Governance and decision authority
is the framework of roles, decision rights, and processes that directs and oversees a . It establishes who can authorize work and resources, who makes key decisions, how progress and risks are reviewed, and how significant changes or problems are escalated. Governance should fit the organization and : too little clarity can leave important decisions unresolved, while unnecessary controls can slow delivery.
Governance commonly connects several roles:
Sponsor or senior responsible owner: Provides senior-level direction and accountability for the ’s rationale, continued justification, and intended outcomes. The precise title and duties vary by organization.
Steering group or governing body: Makes or reviews significant decisions, monitors progress, and resolves issues beyond delegated authority.
: Leads day-to-day within the authority and limits assigned through governance.
team: Performs and coordinates the work needed to produce the deliverables.
Governance may be documented in a charter, role descriptions, decision rules, reporting arrangements, and approval gates. For example, a might be authorized to coordinate work and resolve routine issues, while a proposed increase in funding requires sponsor or board approval. Clear governance makes the escalation path understandable before a major decision is needed.
Leading and coordinating the
The leads the team responsible for achieving the objectives and integrates the ’s work. This includes clarifying what is to be achieved, organizing plans and responsibilities, coordinating contributors, monitoring progress, communicating status, and bringing issues and decisions to the appropriate people. The manager also helps the team adapt when evidence, risks, or circumstances change.
The is not necessarily the sponsor, the technical expert, or the ultimate decision-maker. Authority depends on organizational arrangements, so it is good practice to make clear what the manager may decide, what requires approval, and what must be escalated. The manager is accountable for effective coordination and reporting, while governance assigns some decisions and accountabilities to other roles.
Effective combines structure with judgment. A plan provides a basis for coordination and measurement, but does not guarantee that conditions will remain unchanged. The manager keeps work aligned with its purpose, surfaces important information promptly, and supports informed decisions throughout the life cycle.