PMBOK Project Definition and Key Characteristics
PMBOK Definition and Core Characteristics of a Project
Definition (PMBOK Guide, Project Management Institute):
"A project is a temporary endeavour undertaken to create a unique product, service, or result."
Projects are undertaken by all levels of an organization and may include several departments, divisions, or business units.
Projects can be undertaken by an individual, a group, or a team.
Break down of the definition into parts with added clarifications:
Temporary
Unique product, service, or result
Drive change and enable business value creation
Temporary: key feature
Has a specific start and end date; timeframe can be short (e.g., one month) or long (months/years), but it is not perpetual.
Examples of temporary endeavours:
Building the Pyramids of Giza
Hosting the Olympic Games
Developing a new all-electric commercial airplane
Creating a new software or mobile application
Planning and executing a wedding
Building an apartment building
Adding on to a house
Contrasted with ongoing production: an assembly line producing potato chips 24/7 is production, not a temporary project.
Important nuance: temporary does not imply short duration; some projects span years.
End-of-project criteria (PMBOK): a project ends when one or more criteria are realized:
The project's objectives have been achieved
The objectives will not or cannot be met
The project's funding is exhausted or no longer available
The need for the project no longer exists
Human or physical resources are no longer available
The project is terminated for legal cause or convenience
Unique product, service, or result
Output(s) or deliverables that are unique to the project
If an output or outcome is not unique and repeatable (e.g., bags of chips from an assembly line, apps downloaded to a device), its creation does not qualify as a project
Projects are undertaken to fulfill objectives by producing deliverables (outputs that contribute to a strategic aim)
Objective vs deliverable terminology
Objective: an outcome toward which work is directed; a strategic position to be attained, a purpose to be achieved, a result to be obtained, a product to be produced, or a service to be performed
Deliverable: any unique and verifiable product, result, or capability to perform a service required to complete a process, phase, or project
Distinction:
Deliverable = what is produced
Objective = why we are doing the work
Deliverables: tangible vs. intangible
Tangible deliverables have a physical existence (e.g., a new consumer product, a new manufacturing process)
Intangible deliverables do not have a physical existence (e.g., a patent or a marketing campaign)
Deliverables aligned with an organization's strategic objective
Examples of tangible deliverables that fulfill strategic objectives:
A unique product or component (e.g., a new electric motor to be installed in Tesla vehicles) – component of a larger item
A new version of autonomous driving software for Tesla automobiles – an enhancement/correction to an item
A Tesla Model 3 as a completed end-item (the most affordable Tesla at the time)
Examples of unique services:
Services provided to the organization or community (charitable endeavors) – fundraisers, coat drives, awareness campaigns
Cloud storage services and music streaming services offered by Google, Apple, etc. – these represent unique deliverables
A unique result (output, outcome, or document):
Example: a company changes its corporate culture following an ethical scandal; an improvement program may entail several projects to change management and employee behavior and public perception
Another example: multidisciplinary research leading to a published paper that dispels norms and establishes new findings and practices for society
A unique combination of products, services, or results may also be a deliverable that fulfills a strategic objective
Example: a utility patent filed by Uber to improve process that verifies driver/passenger identity, increasing safety and accountability
Another example: an ERP and CRM system initiative that saves time/money, improves customer experience, and drives growth; deliverables include configuration/installation (product deliverables) and training (service deliverables), while the change management initiative (business change) is a separate deliverable (also a result)
Outputs vs outcomes (importance of value creation)
Output: the installed/configured work product (e.g., ERP/CRM system installed and configured on time, on budget, to spec) – a deliverable that may not create value by itself
Outcome: achieved when the system is actively and productively used by employees and customers realize the benefits; the real value is realized through adoption and resulting transformational change
Timeframe example: a successful ERP/CRM implementation’s outcome may be realized over the next ~ for the initiative
Practical examples tying deliverables to value
ERP/CRM rollout: installation/configuration (output) vs benefits realization (outcome)
Training programs for departments (service deliverable) and the organizational change management to communicate benefits (policy/behavioral change deliverable)
The transformation is achieved when employees use the system as intended and the organization achieves its strategic objectives
Perspective on uniqueness and repetition
Some projects can reuse common resources, suppliers, or processes across multiple efforts (e.g., a custom home builder using the same suppliers/systems) but each project remains unique due to location, environment, preferences, and regulatory constraints
This is a key reason why project management remains valuable: it applies to complex, unique combinations of factors even when some components are reused
Drive change and business value creation
Projects drive organizational change by moving from one state to another to achieve a specific objective
Business value = net quantifiable benefit derived from a business endeavor; can be tangible or intangible
The goal of a project is to create business value
Tangible vs intangible business value (examples)
Tangible value examples:
Monetary currency
Stock/equity
Utility
Fixtures
Tools
Market share
Intangible value examples:
Trademarks
Goodwill
Reputation
Brand recognition
Public benefits
Strategic alignment
Additional project characteristics (beyond the basics)
Multidisciplinary and complex
Conflict is common due to competing interests, funding, resources, and schedules
Projects are often part of a larger program or portfolio; programs may consist of multiple projects
Uncertainty and risk are inherent in all projects
Cross-disciplinary requirements and specialized expertise are common in complex projects (e.g., software, mechanical, civil, electrical engineering; environmental consulting; cybersecurity; structural/fire protection)
The line between project and non-project is blurry; absence/presence of multiple disciplines and complexity helps distinguish programs from standalone projects
Example of scale and complexity: Alice, an electric-powered mini airliner, would be a program with multiple integrated projects (e.g., motor development, batteries, airframe, interior, mechanical systems)
Disciplines and experts required for complex projects may include:
Environmental consultants and auditors (in highway infrastructure/planning)
Structural engineers and fire protection consultants (high-rise towers)
Cybersecurity consultants for IT projects
Program, portfolio, and project structure (conceptual overview)
A program is a group of related projects managed in a coordinated way to obtain benefits that would not be available if managed individually
A portfolio is a collection of projects, programs, and other work that are grouped to facilitate effective governance and alignment with strategic objectives
The transcript notes that portfolios, programs, and projects will be addressed in more detail in later sections (Section 1.5)
Practical example: an electric-powered mini airliner (Alice) may be managed as a program with several sub-projects (motor, batteries, airframe, interior, mechanical systems) to deliver a final aircraft
Conflict and stakeholder engagement
Projects inherently promote change, which can provoke fear and resistance
Effective project management emphasizes people and communication with stakeholders
Stakeholders include individuals, departments, business units, executives, external consultants, investors, suppliers, and customers
More than one person with different personalities, priorities, and schedules increases potential for conflict
Managing stakeholder expectations and balancing competing interests is a central PM responsibility
Risk, uncertainty, and knowledge evolution
Risk definition: an uncertain event or condition that, if it occurs, has a positive or negative effect on one or more project objectives
Uncertainty cannot be eliminated, but risk can be reduced and managed
All projects exist in an environment of uncertainty; examples include Tesla’s electrification/mobility initiatives, autonomous driving, AI projects, and COVID-19 vaccine development
Knowledge vs uncertainty over project life cycle:
At the start, there is more uncertainty than knowledge about the future
As the project progresses through initiation, planning, and execution, knowledge increases and risks become better understood
Some risks are resolved or become inactive as the project moves forward
Even after project completion, remaining unknowns may affect long-term success of the outcome
The visualization concept (Figure 1.3: Project Risk vs Knowledge) illustrates this trajectory: more unknowns early, gradually more knowledge, risk exposure changes over time
Quick reference to practical criteria and examples
Short examples of tasks vs. projects: building a birdhouse or fixing a car are often considered tasks, even if unique, due to limited multidisciplinary complexity
A high-profile program example: development of a new electric aircraft (Alice) would likely be a program with multiple interdependent projects, each delivering components and systems that must be integrated for the final outcome
Summary takeaways
A project is temporary, unique, and aimed at delivering value through a set of deliverables
Deliverables can be tangible or intangible and may be outputs or outcomes depending on their value realization
Projects are a vehicle for change and value creation, often requiring multidisciplinary expertise and stakeholder collaboration
Understanding the differences among outputs, outcomes, deliverables, and strategic objectives is essential for effective project management
Risk and uncertainty are inherent but manageable through planning, governance, and adaptive responses
Key terms to remember (quick glossary)
Project: a temporary endeavor to create a unique product, service, or result
Deliverable: a unique and verifiable product, result, or capability required to complete a process, phase, or project
Output: a deliverable that by itself may not provide value
Outcome: the realized value when a deliverable is actually used to achieve strategic objectives
Business value: net quantifiable benefit from a business endeavor, tangible or intangible
Multidisciplinary: involving multiple disciplines or areas of expertise
Risk: uncertain event/condition with potential impact on objectives
Uncertainty: lack of knowledge about future states; cannot be eliminated entirely
Program: a group of related projects managed together to achieve benefits not possible individually
Portfolio: a collection of projects/programs aligned with strategic objectives
Quick example recap for recall
Tesla’s motor and software developments as components of a broader electric vehicle program
Uber’s safety patent as a deliverable that enhances a service and contributes to strategic value
ERP/CRM implementation as a program consisting of product deliverables (software), service deliverables (training, deployment), and change-management deliverables (communication and adoption)
A birthday party: a simple project with limited disciplines and relatively low complexity; a highway reconstruction project: large, multidisciplinary, high complexity, requiring formal PM standards