1 Project Foundations and Chartering
Learn how projects differ from operations, how to define objectives and success criteria, and how a project charter establishes purpose, boundaries, roles, and authority.
Projects and ongoing
A is a temporary effort to create a unique product, service, or result. It has a defined purpose and concludes when its work is completed, cancelled, or otherwise formally ended.
are ongoing, repeatable activities that sustain an organization. Running a service desk and processing routine orders are examples. A might create a new service-desk system; operating and maintaining that system afterward is ongoing work. Some projects improve , but the change effort and the continuing work are distinct.
Objectives and
A states the outcome the is intended to achieve. Make it specific enough to guide decisions and, where practical, measurable and time-bound. “Improve appointment booking” is vague; “launch online appointment booking for the clinic by September 30” names an outcome and deadline.
are the people or groups who carry out, approve, use, fund, influence, or may be affected by the . Identify them early and clarify their interests and decision roles. For a booking-system , they might include the sponsor, lead, clinic staff, patients, IT and security teams, and system vendor. Different may define value differently, so discuss expectations rather than assuming they agree.
Defining success
specify how authorized decision-makers will judge whether the and its result are acceptable. Agree on measures before execution, identify how each will be verified, and name who accepts the result. Criteria may address:
Delivery: The agreed features are completed and accepted.
Schedule and cost: Delivery meets approved date and budget limits.
Quality: Testing meets stated requirements, such as accessibility and security checks.
Intended outcome: The result achieves a measurable benefit, such as reducing booking calls.
A finished deliverable is not automatically a successful outcome: a team may deliver a system that users still find difficult to use. Separating deliverable acceptance from intended benefits makes expectations clearer.
The
A is a concise, high-level document that authorizes a , connects it to a business need, and establishes initial direction and authority. It is not the detailed plan; detailed schedules and execution methods are developed later. The charter is useful when the sponsor and key agree on its purpose, boundaries, measures, and approval.
A practical charter typically records:
Purpose and need: The problem or opportunity that justifies the work.
Objectives and deliverables: The outcomes and major outputs expected.
Scope boundaries: What is included and explicitly excluded.
and roles: Who sponsors, leads, contributes, uses, and approves.
: The measurable evidence that demonstrates acceptance and value.
High-level constraints and assumptions: The limits or conditions shaping the work.
Milestones, budget, and major risks: The key boundaries and uncertainties.
Authorization: Who approves the and what authority is granted to its lead.
Applying the charter to a clinic booking
For a clinic online appointment-booking , the need is that patients currently book by phone, creating avoidable call volume and delays. The objective is to launch an online booking service for routine appointments by September 30. The deliverable is a tested booking page connected to the clinic’s appointment system, plus staff guidance.
The scope includes booking, confirmation, and cancellation for routine appointments. It excludes replacing the clinic’s medical records system or adding telehealth. The are the clinic director as sponsor, the manager as lead, patients and clinic staff as users, and IT and security as reviewers.
The example are that the sponsor accepts the tested service by September 30, total cost stays at or below $40,000, accessibility and security checks pass, and at least 80% of surveyed patients rate booking as easy during a four-week pilot. The constraints and risks are a fixed budget, staff availability for testing, and possible launch delays from integration defects. The clinic director approves the charter and gives the lead authority to coordinate approved staff and vendor work.
These figures are example targets, not universal standards. The sponsor and affected should confirm that measures are meaningful, feasible, and supported by a reliable way to collect evidence.