Before you manage a project,
meet the field that runs on it.
Project management isn't paperwork bolted onto engineering — it's the discipline of guiding work toward an intended outcome. This chapter lays the foundation the rest of the course builds on: what PM actually is, where it came from, who does it, and the PMBOK vocabulary and 12 principles you'll be tested on and will use for the rest of the semester.
What is Project Management?
Two official framings, same idea
definition1. The application of knowledge, skills, tools, and techniques to
project activities to meet project requirements.
2. Project management refers to guiding the project work to deliver the intended
outcomes. Project teams can achieve the outcomes using a broad range of approaches (e.g.,
predictive, hybrid, and adaptive).
People PMI projects employers will need in project-management-oriented roles by 2027.
New PM employees needed each year to meet global talent demand by 2030 (PMI 2021 Talent Gap report).
Wasted per every $1 billion spent on projects, per PMI's Pulse of the Profession® report.
Projected size of Saudi Arabia's AI market by 2030 under the Smart Government Strategy — ~12.4% of GDP.
Saudi Arabia's 2025 government tech spending (SR93B) — the highest in the world, 21.7% of national spending.
Top skills employers want in new grads — team-work, problem-solving, verbal communication — all core PM skills.
From the pyramids to the PMO
A profession growing "at a very rapid pace" — understanding where it came from explains why PMI, certification, and PMOs exist today.
The pyramids and the Great Wall
Some argue that building the Egyptian pyramids was a project, as was building the Great Wall of China — massive, coordinated, goal-directed endeavors, even without the word "project management" yet.
Most-cited origin of "modern" project management
Led by Dr. Oppenheimer: a three-year, $2 billion (1946 dollars) project. It had a separate project manager and technical manager — an early split between managing the project and managing the technical work, which is still a live distinction today.
Companies start creating Project Management Offices
As the number and complexity of projects grew, organizations began forming Project Management Offices (PMOs) — organizational units responsible for coordinating the project management function across the organization.
Talent, agility, and benefits realization
Several global dynamics are forcing organizations to rethink their practices: talent development for project/program managers is a top concern, basic PM techniques are now core competencies, organizations want more agile approaches, and benefits realization is a key success metric.
The Project Management Institute (PMI) is the leading organization advancing the PM profession. PMI provides certification as a Project Management Professional (PMP®), and the number of people earning PMP® certification is increasing quickly (active holders roughly doubled from ~510K in 2012 to a peak above 1.25M around 2021–2022).
Ethics, loosely defined, is a set of principles that guide decision making based on personal values of "right" and "wrong." Project managers often face ethical dilemmas. To earn PMP® certification, applicants must agree to PMI's Code of Ethics and Professional Conduct — and several PMP® exam questions relate to professional responsibility, including ethics.
The role, the responsibilities, the competencies
What PMs are on the hook for
responsibilitiesProject managers are mainly responsible for all issues related to the software project; issues vary by scale, but the common ones are: Schedule, Budget, Quality, Delivery of products, and Locking in resources. In practice, most of a PM's time is consumed chasing and collecting the status of project tasks.
Job descriptions vary, but most include planning, scheduling, coordinating, and working with people to achieve project goals. 97% of successful projects were led by experienced project managers, who can often help influence success factors.
Skills PMs needBe comfortable with change · Understand the organizations they work in and with · Be able to lead teams to accomplish project goals.
People skills · Leadership · Listening · Integrity/ethical behavior/consistency · Building trust · Verbal communication · Building teams · Conflict resolution/management · Critical thinking/problem solving · Balancing priorities · Negotiating · Influencing the organization · Mentoring · Process and technical expertise.
Thinking/managing (5): conflict resolution, critical thinking, balancing priorities, negotiating, influencing the organization.
Craft (2): mentoring, process & technical expertise.
Better resource control
Financial, physical, and human resources.
Improved customer relations
Structured engagement with stakeholders.
Shorter dev times
Lower costs, improved productivity.
Higher quality
Increased reliability, higher profit margins.
Better internal coordination
Positive impact on meeting strategic goals.
Higher worker morale
Less stress, fewer overworked personnel.
Project Management Body of Knowledge
The reference standard the rest of this course — and this chapter's vocabulary — is built on.
Purpose of The Standard for Project Management
PMBOK v7The Standard for Project Management provides a basis for understanding project management and how it enables intended outcomes. It applies regardless of industry, location, size, or delivery approach (predictive, hybrid, or adaptive). It describes the system within which projects operate — including governance, possible functions, the project environment, and the relationship between project management and product management.
Key areas of focus that must be managed effectively to achieve successful project outcomes.
Stakeholders
Team
Development Approach & Life Cycle
Planning
Project Work
Delivery
Measurement
Uncertainty
The vocabulary PMBOK builds everything else on
An end result or consequence of a process or project. Broader than outputs/artifacts — focuses on the benefits and value the project was undertaken to deliver.
Projects, programs, subsidiary portfolios, and operations managed as a group to achieve strategic objectives. Example: a company's R&D programs, marketing campaigns, or infrastructure upgrades.
Related projects, subsidiary programs, and program activities managed in a coordinated manner to obtain benefits not available from managing them individually. Example: a company-wide digital transformation initiative.
A temporary endeavor undertaken to create a unique product, service, or result. "Temporary" means a beginning and an end to the work or a phase of it. Projects can stand alone or be part of a program or portfolio.
An artifact that is produced, is quantifiable, and can be either an end item in itself or a component item.
The person assigned by the performing organization to lead the project team, responsible for achieving the project objectives — facilitating team work and managing processes to deliver intended outcomes.
A set of individuals performing the work of the project to achieve its objectives.
The members of the project team who are directly involved in project management activities (a subset of the full project team).
A collection of strategic business activities aimed at building, sustaining, and/or advancing an organization. Portfolios, programs, projects, products, and operations can all be part of it.
The worth, importance, or usefulness of something. Different stakeholders perceive it differently: customers via features/functions, organizations via business value (benefits minus cost), and society via community or environmental contribution.
How projects actually turn into value
Provides a context for value delivery, governance, project functions, the project environment, and product management.
Creating a new product, service, or result that meets customer/end-user needs.
Creating positive social or environmental contributions.
Improving efficiency, productivity, effectiveness, or responsiveness.
Enabling changes needed for organizational transition to a desired future state.
Sustaining benefits enabled by previous programs, projects, or operations.
Value Delivery Components
nested structurePortfolios, programs, projects, products, and operations can be used individually and collectively to create value. Working together, they compose a system for delivering value aligned with the organization's strategy. Any project or program could include products, and operations can directly support/influence portfolios, programs, and projects (as well as functions like payroll, supply chain, finance, HR, customer service).
Information Flow
feedback loopA value delivery system works best when information and feedback are shared consistently among all components, keeping the system aligned with strategy and in harmony with the environment.
Senior Leadership shares strategy with Portfolios → Portfolios share desired outcomes, benefits, and value with Programs & Projects → Programs & Projects pass deliverables + support/maintenance info to Operations.
Operations feed back updates, fixes, and adjustments to Programs & Projects → Programs & Projects report performance information and progress to Portfolios → Portfolios report portfolio performance to Senior Leadership. Outcomes/benefits/value performance analysis flows the whole loop back to Senior Leadership.
Works alongside the value delivery system to enable smooth workflows, manage issues, and support decision making. A governance framework can include oversight, control, value assessment, integration among components, and decision-making capabilities — plus an integrated structure for evaluating changes, issues, and risks. Project governance is aligned with program and/or organizational governance, and includes defining the authority to approve changes.
People drive project delivery by executing functions — fulfilled by one person, a group, or combined into defined roles. Coordination can be decentralized (teams self-organize/self-manage) or centralized (a designated project manager leads) — and centralized projects can still include self-organized sub-teams for portions of the work.
| # | Function | Example |
|---|---|---|
| 1 | Provide oversight and coordination | Monitoring progress and performance |
| 2 | Present objectives and feedback | Defining success criteria and desired outcomes |
| 3 | Facilitate and support | Hosting meetings, workshops, stand-ups |
| 4 | Perform work and contribute insights | Completing assigned deliverables |
| 5 | Apply expertise | Advising on technical/domain-specific matters |
| 6 | Provide business direction and insight | Identifying market trends or customer needs |
| 7 | Provide resources and direction | Allocating budget, personnel, infrastructure |
| 8 | Maintain governance | Enforcing regulatory and internal standards |
Factors internal to the organization, arising from the org itself, a portfolio, a program, another project, or a combination. Includes artifacts, practices, and internal knowledge — e.g. process assets, governance documentation, data assets, knowledge assets, infrastructure, information technology software.
Factors external to the organization can enhance, constrain, or have a neutral influence on project outcomes — e.g. marketplace conditions, social/cultural influences, regulatory environment, commercial databases, academic research, industry standards, financial considerations, physical environment.
Where projects meet the product's life cycle
Portfolio, program, and product management are beyond the scope of the PMI standard and this course — but understanding each discipline and the relationships between them provides useful context for projects whose deliverables are products. Product management involves integrating people, data, processes, and business systems to create, maintain, and develop a product or service throughout its product life cycle.
The product life cycleA series of phases representing a product's evolution — from introduction, through growth and maturity, to retirement. Product management may initiate programs or projects at any point in the life cycle to create or enhance specific components, functions, or capabilities. The initial product may begin as a project's deliverable, and later programs/projects can add value throughout the cycle (e.g. Project 1: initial creation → Projects 2–3: more features/additions → Projects 4–6: revisions → Project 7: retirement — all under Portfolio Governance).
The 12 principles of PMBOK v7
Principles are foundational guidelines for strategy, decision making, and problem solving — but unlike laws or rules, PM principles are not prescriptive. They guide behavior; they don't dictate a single "correct" method. They're internally consistent (no principle contradicts another), though practical dilemmas can still arise, and they can overlap with general management principles.
Be a diligent, respectful, and caring steward.
- Act responsibly and ethically, with integrity, care, trustworthiness, and compliance.
- Spans responsibilities inside and outside the organization.
- Holistic view: financial, social, technical, and sustainable environmental awareness.
Create a collaborative project team environment.
- Projects are delivered by project teams.
- Teams work within organizational/professional cultures, often forming their own "local" culture.
- Collaboration aligns cultures, enables learning/development, and optimizes contribution.
Effectively engage with stakeholders.
- Stakeholders influence projects, performance, and outcomes.
- Project teams serve stakeholders by engaging with them.
- Proactive engagement advances value delivery.
Focus on value.
- Value is the ultimate indicator of project success.
- Can be realized during, at the end of, or after the project.
- Defined quantitatively and/or qualitatively; teams adapt to maximize expected value.
Recognize, evaluate, and respond to system interactions.
- A project is a system of interdependent, interacting domains of activity.
- Take a holistic view of how project parts interact with each other and external systems.
- Systems constantly change — stay responsive.
Demonstrate leadership behaviors.
- Any project team member can demonstrate leadership behaviors.
- Leadership ≠ authority.
- Effective leaders adapt style to the situation and to individual motivation, and model honesty, integrity, and ethics.
Tailor based on context.
- Each project is unique.
- Design the development approach using "just enough" process for the desired outcome, maximizing value, managing cost, and enhancing speed.
- Tailoring is iterative — continuous throughout the project.
Build quality into processes and deliverables.
- Satisfies stakeholder expectations and fulfills project/product requirements.
- Focuses on meeting acceptance criteria for deliverables.
- Ensures processes are appropriate and as effective as possible.
Navigate complexity.
- Complexity results from human behavior, system interactions, uncertainty, and ambiguity.
- Can emerge at any point in the project, introduced by scope, communications, stakeholders, risk, or technological innovation.
- Teams stay vigilant and use methods to reduce complexity's amount/impact.
Optimize risk responses.
- Risks can be positive (opportunities) or negative (threats), addressed continually.
- An organization's risk attitude, appetite, and threshold shape the response.
- Responses should be appropriate, cost-effective, realistic, agreed by stakeholders, and owned by someone.
Embrace adaptability and resiliency.
- Adaptability = ability to respond to changing conditions.
- Resiliency = ability to absorb impacts and recover quickly from a setback or failure.
- Focusing on outcomes rather than outputs facilitates adaptability.
Enable change to achieve the envisioned future state.
- A structured approach helps the transition from current to future state.
- Change can originate internally or externally; not everyone embraces it.
- Too much change too fast → change fatigue/resistance. Stakeholder engagement and motivation assist adoption.
Where students actually lose points
These are the specific mix-ups this chapter sets up — drill these before anything else.
Chapter 4, in three tables
| Term | One-line definition |
|---|---|
| Product | A quantifiable artifact produced — an end item or component. |
| Project | A temporary endeavor to create a unique product, service, or result. |
| Program | Related projects/programs managed together for benefits not available individually. |
| Portfolio | Projects, programs, subsidiary portfolios, and operations grouped for strategic objectives. |
| # | Principle | One-line gist |
|---|---|---|
| 1 | Stewardship | Act responsibly and ethically. |
| 2 | Team | Foster trust, respect, open communication. |
| 3 | Stakeholders | Involve stakeholders proactively. |
| 4 | Value | Prioritize outcomes that deliver value. |
| 5 | Systems Thinking | Understand interactions within/beyond the project. |
| 6 | Leadership | Lead with integrity, adaptability, empathy. |
| 7 | Tailoring | Adapt methods, tools, and approaches. |
| 8 | Quality | Embed quality from the start. |
| 9 | Complexity | Embrace uncertainty and complexity. |
| 10 | Risk | Identify, assess, and respond to risks. |
| 11 | Adaptability & Resiliency | Be flexible and ready to pivot. |
| 12 | Change | Support transformation and continuous improvement. |
| # | Domain |
|---|---|
| 1 | Stakeholders |
| 2 | Team |
| 3 | Development Approach and Life Cycle |
| 4 | Planning |
| 5 | Project Work |
| 6 | Delivery |
| 7 | Measurement |
| 8 | Uncertainty |
Click a question to reveal the answer
Quick self-check, separate from the Practice Lab below.
Apply the definitions to real scenarios
Same shape of question this chapter's terminology gets tested with — grounded directly in the slide definitions.