The Project Management Professional (PMP) certification is a globally recognised credential that proves you can lead projects successfully, regardless of industry. It matters for your career because it validates you know the standardised language and best practices that organisations trust to deliver results on time and within budget. This chapter explains what the PMP exam actually tests and the fundamental concepts every project manager must master before they can manage anything—from building a mobile app to organising a wedding.
Jump to a section
A simple way to picture Introduction to the PMP Exam and Project Management Basics
A family road trip is a project. The destination is the project goal—getting everyone safely and happily to Grandma's house for a holiday celebration. The trip's constraints include a fixed budget for petrol and snacks, a strict timeline (arrive before dinner), and a limited scope (no detours to the Grand Canyon this time). The project manager is the designated driver and navigator. This person does not own the car (that is the sponsor, who provides the vehicle and fuel) and does not choose the destination (that is the customer, Grandma, who requested the visit). The project manager's job is to plan the route, anticipate traffic jams (risks), manage the children's competing requests for bathroom breaks and music (stakeholder expectations), and ensure the car does not run out of petrol (resources). When a sudden road closure appears (an issue), the project manager must find an alternative route, communicate the delay to everyone in the car, and adjust the arrival estimate—all while keeping the trip's budget and timeline in check. If the children argue over the radio station (a conflict between team members or stakeholders), the project manager mediates to keep the journey productive. The trip ends when the car pulls into Grandma's driveway and the family celebrates (project closure). Without this structured navigation, the family might argue, get lost, run out of fuel, or arrive days late—just as projects without management fail to deliver value.
This analogy maps precisely to the PMP framework. The project manager uses processes from the five Process Groups (Initiating, Planning, Executing, Monitoring and Controlling, Closing) to guide the trip from start to finish. The ten Knowledge Areas—like Scope (which relatives to visit), Time (the schedule), Cost (petrol budget), and Risk (potential breakdowns)—provide the checklists and tools the driver-navigator uses. A beginner studying for the PMP exam can remember this analogy: you are the driver who never owns the car but ensures the journey succeeds for everyone inside it.
Project management is the application of knowledge, skills, tools, and techniques to meet project requirements and create value for stakeholders. A project is a temporary endeavour undertaken to create a unique product, service, or result. Temporary means it has a definite beginning and end—unlike operations, which are ongoing and repetitive (like processing payroll every month). Unique means the outcome is different from anything else the organisation has produced before. This temporary, unique nature is what separates projects from business-as-usual activities.
The PMP exam tests your understanding of two key frameworks: the Process Groups and the Knowledge Areas. The five Process Groups describe the logical phases a project passes through. Initiating is where you define the project and obtain authorisation to start. Planning is where you define the scope, create the schedule, estimate costs, and plan for risks—this is the most time-consuming group because poor planning guarantees failure. Executing is where you actually perform the work described in the plan, such as developing software, constructing a building, or training staff. Monitoring and Controlling runs parallel to all other groups; it involves tracking progress, measuring performance, and making adjustments to keep the project on track. Closing is where you formally complete the project, hand over the deliverables, release resources, and document lessons learned.
The ten Knowledge Areas are specialised domains that provide the specific techniques and tools you need within each Process Group. They are:
Integration Management: Coordinates all aspects of the project, including the project charter, project management plan, and managing changes.
Scope Management: Ensures the project includes all the work required—and only the work required—to complete the project successfully.
Schedule Management: Defines activities, sequences them, estimates durations, and develops and controls the schedule.
Cost Management: Plans, estimates, budgets, finances, and controls costs so the project can be completed within the approved budget.
Quality Management: Ensures the project's deliverables meet the required standards and satisfy stakeholder needs.
Resource Management: Identifies, acquires, and manages the physical and human resources needed for the project.
Communications Management: Plans for, creates, distributes, stores, retrieves, and disposes of project information in a timely manner.
Risk Management: Conducts risk identification, analysis, response planning, and monitoring to minimise threats and maximise opportunities.
Procurement Management: Manages the purchase of products, services, or results from outside the project team.
Stakeholder Management: Identifies the people and organisations impacted by the project, analyses their expectations, and strategically engages them to ensure project success.
The project manager is not the person who does all the work. The project manager is the integrator—the person who leads the team, communicates with stakeholders, manages constraints (scope, time, cost, quality, resources, risk), and makes trade-off decisions. The exam heavily emphasises that the project manager is a facilitator, not a technical expert in the project's subject matter. For example, a project manager building a hospital does not need to be a doctor or an architect, but must know how to manage the team of doctors, architects, and contractors to deliver the hospital on time and on budget.
The PMP exam itself consists of 180 multiple-choice questions covering these Process Groups and Knowledge Areas. The questions are scenario-based, meaning they describe a realistic situation (e.g., a team member is in conflict with a stakeholder, a sudden budget cut occurs) and ask you to select the best action a project manager should take. The exam also tests your understanding of predictive (traditional waterfall) approaches and agile (adaptive) approaches, as modern project management blends both. You are expected to know that the project manager must always act ethically, follow the PMI Code of Ethics and Professional Conduct, and prioritise stakeholder satisfaction while balancing the triple constraint (scope, schedule, cost). Core concepts like the project charter (a formal document that authorises the project and gives the project manager authority), the work breakdown structure (a hierarchical decomposition of all work needed to create the deliverables), and earned value management (a technique for measuring project performance against the plan) appear frequently. Understanding these basics provides the foundation upon which all other PMP topics are built.
Identify the project and its business case
Before any work begins, someone (usually a sponsor) identifies a business problem or opportunity. The business case documents why the project is worth investing in—like a retailer needing a website to compete online. This step justifies the project's existence and secures initial approval to explore further.
Develop the project charter
The sponsor creates the project charter, which formally authorises the project, names the project manager, and grants them authority to use resources. The charter states the high-level scope, key stakeholders, and the business case. Without this document, the project manager has no legal or organisational power to proceed.
Plan the project in detail
The project manager leads the team to create a comprehensive project management plan. This includes a Work Breakdown Structure (WBS) to decompose all work into manageable tasks, a schedule with milestones, a budget, and identifies potential risks. This step is the most time-consuming because thorough planning prevents scope creep and cost overruns later.
Execute the project work and monitor progress
The team performs the work described in the plan—for example, coding the website or constructing the building. Simultaneously, the project manager tracks progress against the baseline plan, measures actual cost and schedule, and holds regular status meetings. If the team discovers a risk or the budget overruns, the project manager performs integrated change control to adjust the plan.
Close the project formally
When all deliverables are completed and accepted by the customer, the project manager leads the closing process. This includes obtaining formal sign-off from stakeholders, releasing resources (team members return to their functional departments), archiving project documents, and conducting a lessons-learned review. The final step ensures the project is formally concluded, not left in limbo.
Consider a mid-sized retail company launching a new e-commerce website. The company has no internal IT development team, so the project manager is hired specifically to oversee this project. The project's goal is to design, develop, and launch a website that allows customers to browse inventory, make purchases, and track orders. The budget is £150,000, the timeline is six months, and the key stakeholders include the marketing director (who wants a visually appealing site), the operations director (who needs integration with the existing warehouse inventory system), and the finance director (who is concerned about cost overruns).
The project manager begins by working with the stakeholders to create a project charter. This formal document authorises the project, names the project manager, and states the business case—the reason the company is investing £150,000. Without this charter, the project manager has no authority to spend money or direct people. Once the charter is approved, the project manager moves into Planning. They create a Work Breakdown Structure (WBS) that breaks the entire website into smaller, manageable pieces: design of the homepage, product pages, shopping cart, payment gateway, inventory integration, user account management, and testing. Each piece is further decomposed until the work is small enough to assign to a specific person or team. The project manager also builds a schedule using a Gantt chart, estimates costs for each deliverable (e.g., £30,000 for design, £50,000 for development, £20,000 for testing), and identifies risks.
One risk identified during planning is that the third-party payment gateway provider might delay its integration. The project manager creates a risk register, document this risk, assigns a probability (medium) and impact (high), and plans a response: if the provider is late, the team will use a backup payment gateway while continuing negotiations. This is a concrete example of risk management in action.
During execution, the project manager's daily tasks include:
Leading daily stand-up meetings with the development team to track progress.
Managing the budget by approving purchase orders for design software and hosting services.
Communicating status reports to the marketing director every week.
Resolving conflicts between the designer and the developer about page load times.
Conducting quality inspections of early prototypes against the requirements document.
When the development team discovers that the inventory integration requires an unexpected £10,000 licensing fee, the project manager does not just approve the expense. They perform an integrated change control process: they evaluate the impact on the schedule (two-week delay), budget (overrun), and scope (no change), then present the options to the change control board (a group of stakeholders). The board decides to approve the fee and adjust the schedule. The project manager updates the project management plan and communicates the change to all stakeholders.
At the end of the six months, the website is launched. The project manager leads the closing process: confirms all deliverables are accepted by the marketing director, releases the development team to other projects, archives all project documents, and conducts a lessons-learned session where the team discusses what went well (weekly stand-ups kept everyone aligned) and what could be improved (earlier engagement with the payment gateway vendor). The project manager then writes a final report summarising the project's success, including metrics like actual cost (£158,000) versus planned (£150,000) and the number of defects found during testing (12). This documentation becomes a reference for future projects in the company.
The PMP exam tests your understanding of the foundational concepts in this chapter heavily, because they are the building blocks for every other domain. Expect at least 10–15 questions out of 180 to directly assess your grasp of what a project is, what a project manager does, and the difference between projects and operations. The exam is not interested in definitions you can memorise—it wants to see if you can apply the concepts to realistic scenarios.
Question types you will encounter include:
Scenario-based 'what should the project manager do first?' questions. These test your knowledge of the logical order of Process Groups. For example: 'A project is in the planning phase. A new stakeholder requests a change. What should the project manager do?' The trap is to immediately implement the change. The correct answer is to first evaluate the impact on scope, schedule, and cost before presenting the change request to the change control board.
Questions about the distinction between projects, programmes, and portfolios. A project is a single temporary effort. A programme is a group of related projects managed together for benefits not available from managing them individually (e.g., building a hospital and training its staff as two coordinated projects). A portfolio is a collection of projects, programmes, and operational work grouped to achieve strategic objectives (e.g., all healthcare initiatives of a government).
Questions about the triple constraint. The exam loves to present a scenario where one constraint is tightened (e.g., deadline is moved up) and ask how the other constraints are affected. The correct pattern is that the triple constraint is a system: if schedule is compressed, cost typically increases or scope must decrease.
Questions about the role of the project manager. Traps include answers where the project manager personally performs the design work, approves the budget without sponsor consent, or ignores stakeholders. The correct answer always reflects the project manager as a facilitator who leads the team, communicates, and manages integrated changes.
Questions about the business case and project charter. The business case justifies the project (why it should exist). The project charter authorises the project and names the project manager. The exam will test that the project manager can be assigned before or after the charter is drafted, but they do not create the business case (that is the sponsor's job).
Key definitions to memorise verbatim:
Project: a temporary endeavour undertaken to create a unique product, service, or result.
Operations: ongoing activities that produce repetitive outputs.
Programme: a group of related projects managed in a coordinated way.
Portfolio: a collection of projects, programmes, and operational work.
Project manager: the person assigned by the performing organisation to lead the team and achieve project objectives.
Sponsor: the person or group who provides resources and support for the project and is accountable for enabling success.
Stakeholder: any individual, group, or organisation who can affect, be affected by, or perceive themselves to be affected by a project decision, activity, or outcome.
The exam also tests that you understand the relationship between Process Groups and Knowledge Areas. For instance, you might be asked: 'During which Process Group does the project manager develop the project management plan?' The answer is Planning. 'During which Process Group does the team actually build the product?' The answer is Executing. A common trap is confusing Monitoring and Controlling with Planning. Remember: planning creates the plan; monitoring and controlling tracks progress against the plan and recommends corrective actions.
Finally, the exam tests ethics indirectly. Questions may present a situation where a vendor offers a gift or a stakeholder tries to pressure the project manager to falsify a status report. The correct answer always aligns with the PMI Code of Ethics—honesty, responsibility, respect, and fairness. Do not accept gifts that could influence decisions, and do not hide bad news from stakeholders.
A project is temporary and unique, while operations are ongoing and repetitive—this distinction is tested in multiple exam questions.
The five Process Groups—Initiating, Planning, Executing, Monitoring and Controlling, and Closing—are not phases that happen in strict sequence; they overlap and repeat throughout the project.
The project manager is a facilitator and integrator, not a technical expert in the project's subject matter.
The triple constraint (scope, schedule, cost) is a dynamic system: changing one constraint inevitably impacts the other two.
The project charter formally authorises the project and grants the project manager authority; without it, the project manager has no power to proceed.
Stakeholders include anyone affected by the project—customers, team members, suppliers, regulators—and managing their expectations is a core responsibility of the project manager.
The PMP exam is scenario-based, testing your ability to apply concepts to real-world situations, not just recall definitions.
Ethical behaviour, as defined by the PMI Code of Ethics, is always the correct answer when exam questions present a moral dilemma.
A business case justifies the project's existence and precedes the charter; the project manager helps refine it but does not create it alone.
Risk management involves identifying threats and opportunities early, planning responses, and continuously monitoring—not just reacting when problems arise.
These come up on the exam all the time. Here's how to tell them apart.
Project Manager
Temporary authority limited to the project's duration and budget
Focuses on achieving project objectives (scope, time, cost, quality)
Leads a team assembled from multiple functional departments
Functional Manager
Permanent authority over a department (e.g., IT, Marketing)
Focuses on operational excellence, resource development, and career growth of staff
Manages employees in a fixed reporting structure
Project Charter
High-level document created during Initiating; authorises the project
Names the project manager and grants them authority
Contains business case, high-level scope, and key stakeholders
Project Management Plan
Detailed plan created during Planning; guides execution and control
Contains baselines (scope, schedule, cost) and subsidiary plans (risk, quality, communication)
Is updated through change control during the project
Risk (Threat)
An uncertain event that may negatively affect the project; it has not happened yet
Can be planned for with a risk response (avoid, mitigate, transfer, accept)
Documented in a risk register and monitored proactively
Issue
A problem that has already occurred and must be addressed now
Requires immediate action, which may impact schedule or budget
Documented in an issue log and resolved reactively
Work Breakdown Structure (WBS)
A hierarchical decomposition of all deliverables into smaller components
Focuses on what will be produced (outputs), not how or when
Each level represents a progressively detailed breakdown of scope
Activity List
A list of specific actions required to produce each WBS deliverable
Focuses on how the work will be done (tasks), including durations and dependencies
Used to build the project schedule and estimate resources
Predictive (Waterfall)
Requirements are defined upfront and changes are discouraged
Project runs through phases sequentially: plan, design, build, test, deliver
Best for projects with well-understood, stable requirements (e.g., bridge construction)
Agile
Requirements are expected to evolve; changes are welcomed throughout
Work is done in short iterations (sprints) with frequent feedback loops
Best for projects with uncertain or rapidly changing requirements (e.g., software app development)
Mistake
The project manager is the boss of the project team and can order people around.
Correct
The project manager leads and facilitates, but team members typically report to functional managers. The project manager has authority over the project plan and budget, but not over people's careers.
In many traditional organisations, people are assigned to projects temporarily from functional departments (e.g., IT, marketing). Beginners confuse the project manager's temporary authority with a permanent hierarchical management role.
Mistake
A project manager must be a technical expert in the project's field to succeed.
Correct
The project manager's expertise is in the process of project management, not the product. They manage scope, schedule, communication, and risk—not the technical details.
Beginners assume that managing a software project requires knowing how to code, or that managing a construction project requires being an engineer, because they have seen technical leads do double duty.
Mistake
The project manager is solely responsible for the project's success or failure.
Correct
The project manager is accountable for leading the team and managing constraints, but success depends on the team, sponsor support, stakeholder engagement, and external factors. Shared accountability is the reality.
Popular media and job descriptions often portray a 'hero' project manager who single-handedly saves a failing project. In reality, project managers have no control over market changes, supplier delays, or executive decisions.
Mistake
Once the project is planned, the project manager just follows the plan exactly.
Correct
Project management is iterative and adaptive. Plans change due to risks, stakeholder feedback, and unforeseen issues. The project manager continuously monitors, adjusts, and communicates changes.
People new to project management often mistake the plan as a rigid script. They do not realise that change requests, corrective actions, and risk responses are routine, not signs of failure.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
A project is a single temporary endeavour to create a unique product (like building one website). A programme is a group of related projects managed together to achieve benefits that would not be possible by managing them individually (like a programme to develop a new electric car, which includes separate projects for battery technology, chassis design, and charging infrastructure).
Yes, but focus on understanding the inputs, tools, and outputs of each process rather than rote memorisation. The exam tests your ability to apply the correct process in a scenario, not to list them from memory. Use mnemonic devices and practice scenario questions to reinforce recognition.
Yes, if you meet the eligibility requirements (at least 36 months of leading projects if you have a 4-year degree, or 60 months without a degree, plus 35 contact hours of project management education). The exam tests knowledge of the framework, which you can learn through study even without direct experience. Many people pivot careers by studying and then finding project coordinator roles.
Predictive (waterfall) follows a sequential plan from start to finish, ideal for projects with clear requirements (e.g., building a bridge). Agile is iterative and adaptive, ideal for projects where requirements evolve (e.g., software development). The PMP exam expects you to know both approaches and when to use each.
The exam has 180 multiple-choice questions, including some that require selecting multiple answers or dragging items into order. It is considered difficult because the questions are scenario-based and often have two plausible answers, requiring you to choose the one that aligns best with PMI's recommended practices. Most candidates need 3–6 months of focused study.
Start with the PMBOK Guide or a comprehensive study guide that explains the five Process Groups and ten Knowledge Areas. Then practise with scenario-based questions from reputable sources (e.g., PMI's sample questions, Rita Mulcahy's book). Avoid relying solely on memorising the ITTOs (inputs, tools, techniques, outputs); focus on understanding the flow of processes and the mindset of a project manager.
You've finished Introduction to the PMP Exam and Project Management Basics. Continue through the PMP study guide to build a complete picture of the exam.
Done with this chapter?