📘 Introduction to Project Management
Study Notes — Page 1 | ClearPMPExam.com | Written by a PMP passer, for you.
1. What is a Project?
A project is a temporary effort undertaken to create a unique product, service, or result.
Two words make a project a project: Temporary and Unique. Let’s break both down in plain English.
Temporary — It has an end date
Every project has a start date and a finish date. It ends when the goal is achieved — or when the project is cancelled.
Temporary does NOT mean short. A 10-year metro rail construction project is still a project — because it will eventually end. Duration doesn’t matter. The fact that it ends matters.
Unique — The output is one-of-a-kind
Even if two projects look similar, they are unique because of differences in users, location, features, or context. Building the same mobile app for two different clients = two different projects.
“Projects are like fingerprints — no two are exactly alike, and every one has an expiry.”
2. Project vs Operations — The Most Common Exam Trap
The PMP exam loves to test this. The question gives you a scenario and asks: is this a project or operations? Here is the simple rule:
🏗️ Project
- Has a start & end date
- Output is unique
- Done when goal is met
- Example: Creating a new pharma campaign
- Example: Building a hospital
- Example: Launching a mobile app
⚙️ Operations
- Ongoing — no end date
- Repetitive and continuous
- Produces same output
- Example: Running daily ads
- Example: Monthly hospital reporting
- Example: Processing daily insurance claims
If the work is ongoing and repetitive → Operations. If the work is temporary and unique → Project. When you see “daily,” “monthly,” “routine” in a question — think Operations.
3. What is Project Management?
Project Management is the application of knowledge, skills, tools, and techniques to meet project requirements and achieve objectives — while managing stakeholders and balancing constraints.
The 5 Things a Project Manager Manages
Every project has five constraints. Change one, and the others are affected. This is also called the Triple Constraint (Scope, Time, Cost) — expanded to five in modern PM.
Scope
What work is included
Time
Deadlines & schedule
Cost
Budget & spending
Quality
Standards must be met
Risk
What might go wrong
Real example: A pharma campaign project — Scope = videos + app + website. Time = launch before World Health Day. Cost = stay within ₹10 lakh. Quality = medical accuracy. Risk = vendor delays.
PM does NOT jump into execution first. The very first step is always: define scope → identify stakeholders → plan.
4. Project, Program, Portfolio & PMO — How They Relate
Think of these as three levels of scale. Projects sit inside Programs, which sit inside Portfolios. The PMO is the governance body that oversees them.
Portfolio
A collection of projects & programs aligned to business strategy. Focus: decision-making, not execution. Example: A pharma company decides which diseases to invest in — diabetes campaign, cardio app, oncology research.
Program
A group of related projects managed together for greater benefit. Example: Launching a new medicine = website project + mobile app project + webinar project — together they form a program.
Project
A single temporary effort to create a unique output. Example: Building the website for the new medicine launch.
A Program is NOT a “big project.” It is a group of related projects managed together for synergy. The key word is related.
PMO — Project Management Office
The PMO is a centralized body that standardizes how projects are managed across an organization. There are three types — and the exam loves to test which is which:
Supportive PMO
Provides templates, best practices, and guidance. Low control. Like a library — you take what you need.
Controlling PMO
Enforces compliance with frameworks and standards. Medium control. Checks that you’re following the rules.
Directive PMO
Directly manages and controls projects. Project managers report to the PMO. High control. The PMO is the boss.
Supportive = suggests. Controlling = checks. Directive = decides. (S → C → D = Low → Medium → High control)
5. The 5 Process Groups — WHEN Things Happen
Process Groups answer the question: WHEN does this happen in the project? They are the five phases every project goes through — in order.
Initiating
Should we do this? Authorize the project.
Planning
How will we do it? Build the roadmap.
Executing
Do the work. Build the product.
Monitoring & Controlling
Track progress. Fix problems.
Closing
Finish. Hand over. Lessons learned.
Key Documents for Each Phase
| Process Group | Goal | Key Output / Document |
|---|---|---|
| Initiating | Authorize the project | Project Charter, Stakeholder Register |
| Planning | Plan how it will be done | PM Plan, Scope Baseline, Schedule, Budget |
| Executing | Do the actual work | Deliverables, Change Requests |
| Monitoring & Controlling | Track and correct | Performance Reports, Change Requests |
| Closing | Formally finish | Final Acceptance, Lessons Learned |
Most PMP exam questions come from Planning and Monitoring & Controlling. Know these two process groups inside out.
Special exam note: Corrective actions and preventive actions are identified in Monitoring & Controlling — but they are implemented in Executing. This distinction appears frequently in exam questions.
6. The 10 Knowledge Areas — WHAT You Manage
Knowledge Areas answer the question: WHAT are you managing? Each area is a domain of expertise a PM must handle.
Process Group = WHEN (the phase). Knowledge Area = WHAT (the domain). Combine both = the complete PMP framework. Every PMP question fits into one of these two dimensions.
Integration
Everything works together. Owns change control. The glue of the project.
Scope
What work is in and out of the project. Prevents scope creep.
Schedule
Timelines, deadlines, critical path. When does work happen?
Cost
Budget planning and spending control. EVM lives here.
Quality
Meeting standards, no rework. Prevention over inspection.
Resource
People, equipment, materials. Team management lives here.
Communication
Right info, right person, right time. n(n-1)/2 formula.
Risk
Identify and handle uncertainties before they become problems.
Procurement
External vendors and contracts. Outsourcing work.
Stakeholder
Manage expectations of everyone affected by the project.
7. Organisational Structures — Where Does the PM Stand?
The type of organisation you work in determines how much authority the PM actually has. The exam tests this often — usually by describing a scenario and asking what kind of structure it is.
| Structure | PM Authority | Who Controls Resources? | Real Example |
|---|---|---|---|
| Functional | Low ❌ | Functional Manager (Head of IT, HR, Finance) | A bank where IT staff report to Head of IT. PM must request resources. |
| Weak Matrix | Low–Medium | Mostly Functional Manager | PM coordinates but has limited say on team assignments. |
| Balanced Matrix | Medium ⚖️ | Shared — both PM and Functional Manager | Software company: developer reports to both Engineering Head and PM. |
| Strong Matrix | Medium–High | Mostly PM | PM has more authority but still has functional managers in background. |
| Projectised | High ✅ | Project Manager — full control | A construction firm where teams form per project. PM is the boss. |
If the question says “PM must request resources from department heads” → Functional. If “PM has full authority over the team” → Projectised. If “dual reporting” → Matrix.
Functional = Functional manager wins. Projectised = PM wins. Matrix = they share (and sometimes fight).
🎯 Practice Q&A — Test Yourself
Read the question. Think of your answer. Then click to reveal.
✅ Page 1 complete. Next up: Page 2 — Scope Management — the 6-step scope process, WBS, scope creep, and more.