Process: Managing the Technical Work of the Project
Process is the largest domain on the PMP exam at roughly half of all questions, and it covers the technical craft of turning objectives into delivered value. It spans how you choose and tailor a delivery approach, then how you plan and control integration, scope, schedule, cost, quality, risk, procurement, communications, and stakeholders. The exam does not test rote formulas so much as judgment: given a situation, what should a project manager do to keep the work aligned to value while responding to change in a disciplined way? Work through each section below, and pay special attention to the worked schedule and earned-value math, which appears in a predictable form.
Selecting and Tailoring the Delivery Approach
Before planning anything, the project manager chooses where the work sits on a continuum from predictive (plan-driven) to adaptive (agile), and then tailors the practices to the specific project. Predictive approaches fit stable, well-understood scope where requirements can be defined up front and change is costly, such as construction or regulated hardware. Adaptive approaches fit high-uncertainty work where requirements emerge and fast feedback reduces risk, such as new software or product discovery. Hybrid approaches deliberately combine both, for example planning a physical build predictively while developing its software in iterations. The right choice depends on the degree of uncertainty, the frequency of expected change, stakeholder availability for feedback, regulatory constraints, and team experience. Tailoring means keeping the ceremonies and artifacts that add value and dropping those that only add overhead, always with the goal of delivering value rather than following a framework for its own sake.
Integration and Integrated Change Control
Integration is the project manager's unique job: no one else unifies scope, schedule, cost, quality, and stakeholders into one coherent whole. It starts with a project charter that authorizes the project and names the project manager, and it continues through directing the work, managing knowledge, and monitoring performance against the plan. The heart of integration is integrated change control: every requested change is captured, evaluated for its impact on all baselines, and formally approved or rejected before it is implemented. A project manager never quietly absorbs a scope change; the correct response on the exam is almost always to assess the impact, take it through the change control process, and update the plan and baselines once approved. This discipline is what prevents scope creep and keeps the plan credible. When change is approved, the baselines are updated so that future performance is measured against reality, not against an outdated plan.
Managing Scope
Scope management defines and controls what is and is not part of the project. In predictive work, the team collects requirements, writes a scope statement, and decomposes the work into a work breakdown structure (WBS), where the lowest level is a work package and the smallest planned unit of work overall is an activity. The WBS creates a shared, exhaustive picture of the deliverables and prevents both gaps and gold-plating (adding unrequested extras). Requirements are validated with stakeholders, and completed deliverables are formally accepted through the validate-scope process, which is about customer acceptance, distinct from quality control's focus on correctness. In adaptive work, scope lives in a prioritized product backlog that is continuously refined, so the fixed variable becomes time and cost while scope flexes. Scope creep is uncontrolled change; the countermeasure is a clear baseline plus change control, not simply saying no to stakeholders.
Managing the Schedule: Critical Path and Float
Scheduling sequences activities, estimates durations, and builds a model that predicts the finish date. The critical path is the longest path of dependent activities through the network, and it determines the shortest possible project duration; any delay on it delays the whole project. Float (or slack) is how long an activity can slip without delaying the project (total float) or without delaying its successor (free float), and activities on the critical path have zero total float. Worked example: suppose Start leads to A (4 days) then C (3 days), and also Start leads to B (2 days) then C. Path A→C is 4 + 3 = 7 days and path B→C is 2 + 3 = 5 days, so the critical path is A→C at 7 days. Activity B has total float of 7 − 5 = 2 days, meaning B can slip up to 2 days before it starts to push the project. To recover a slipping schedule you can crash it (add resources to critical activities, which usually adds cost) or fast-track it (run activities in parallel that were planned in sequence, which usually adds risk). Choosing crash versus fast-track is a classic exam judgment call: fast-track when you cannot spend more money, crash when you cannot accept more risk.
Managing Cost and Earned Value (EVM)
Cost management estimates, budgets, and controls spending against a cost baseline, and earned value management (EVM) is how the exam measures whether you are on budget and on schedule using one integrated set of numbers. Three inputs drive everything: planned value (PV, the budgeted cost of work scheduled), earned value (EV, the budgeted cost of work actually completed), and actual cost (AC, what you truly spent). Worked example with a budget at completion (BAC) of $100,000: you planned to be 50% done so PV = $50,000, you are actually 40% done so EV = $40,000, and you have spent AC = $45,000. Cost variance CV = EV − AC = 40,000 − 45,000 = −$5,000, and schedule variance SV = EV − PV = 40,000 − 50,000 = −$10,000; negative is bad in both cases, so you are over budget and behind schedule. The cost performance index CPI = EV ÷ AC = 40,000 ÷ 45,000 = 0.89, and the schedule performance index SPI = EV ÷ PV = 40,000 ÷ 50,000 = 0.80; an index below 1.0 signals unfavorable performance. If current cost efficiency will continue, the estimate at completion EAC = BAC ÷ CPI = 100,000 ÷ 0.89 = $112,360, and the estimate to complete ETC = EAC − AC = 112,360 − 45,000 = $67,360. Memorize the pattern: variances are subtractions (EV first, negative is bad), indexes are divisions (EV on top, below 1.0 is bad).
Managing Quality
Quality management ensures the project's deliverables meet requirements and are fit for use, and the exam's core principle is that prevention is preferred over inspection: it is cheaper to design defects out than to catch and rework them later. Plan quality by defining the standards and metrics that matter, then manage quality (the process focus, sometimes called quality assurance) by auditing whether the processes themselves are sound and improving them. Control quality is the product focus: inspecting and testing actual deliverables to confirm they meet the standards, using tools such as checklists, control charts, and root-cause analysis with cause-and-effect (fishbone) diagrams. The cost of quality includes prevention and appraisal costs (conformance) versus internal and external failure costs (non-conformance), and investing in conformance almost always beats paying for failures found by the customer. When a recurring defect appears, the exam-correct move is to find and eliminate the root cause, not just fix the symptom or add more inspection.
Managing Risk and Response Strategies
Risk management is continuous, not a one-time event: you identify risks, analyze them qualitatively (probability and impact) and sometimes quantitatively, plan responses, implement them, and monitor throughout. Every identified risk lives in the risk register with an owner and a planned response. For threats (negative risks) the strategies are avoid (eliminate the cause), transfer (shift the impact to a third party, for example via insurance or a fixed-price contract), mitigate (reduce probability or impact), escalate (hand a risk outside the project's authority to the right level), and accept (take no proactive action, often with a contingency reserve). For opportunities (positive risks) the mirror strategies are exploit, share, enhance, escalate, and accept. Contingency reserves cover known risks that you have identified, while management reserves cover unknown-unknowns and typically require management approval to use. When a risk's probability or impact changes, reassess it, update the register, and trigger the planned response rather than reacting ad hoc.
Managing Procurement and Contracts
Procurement management brings in outside sellers and, above all, chooses a contract type that allocates risk appropriately between buyer and seller. Firm-fixed-price (FFP) contracts set a single price for well-defined scope and put cost risk on the seller, which is ideal when requirements are clear. Cost-reimbursable contracts (such as cost-plus-fixed-fee or cost-plus-incentive-fee) pay the seller's costs plus a fee and put more cost risk on the buyer, which suits work whose scope cannot be pinned down in advance. Time-and-materials (T&M) contracts are a hybrid used for staff augmentation or small, uncertain efforts where you pay hourly rates plus materials. As uncertainty in the scope rises, you move from fixed-price toward cost-reimbursable and T&M. The procurement life cycle runs from planning and soliciting bids, through selecting a seller and administering the contract, to formally closing it. In agile and collaborative environments, teams often prefer flexible arrangements and master service agreements that allow scope to evolve without renegotiating the whole contract.
Managing Stakeholders and Communications
Most project problems trace back to communication, so the project manager invests heavily in identifying stakeholders, understanding their interests and influence, and keeping them appropriately engaged. Stakeholders are analyzed on grids such as power/interest, and each is assessed on an engagement scale from unaware to resistant to neutral to supportive to leading, with a plan to move them where the project needs them. A communications management plan answers who needs what information, in what format, how often, and through which channel, matched to each audience: executives want concise status and decisions, while the team needs detailed, frequent, transparent updates. A useful exam fact is that the number of potential communication channels in a group grows as n(n − 1) ÷ 2, so a team of 6 has 6 × 5 ÷ 2 = 15 channels, which is why larger teams need deliberate communication structure. The bias on the exam is toward proactive, face-to-face or high-bandwidth communication and toward addressing concerns directly rather than ignoring or over-escalating them.
Agile Ceremonies, Artifacts, and Hybrid Delivery
Adaptive delivery replaces big up-front plans with short, timeboxed iterations and empirical feedback. In Scrum, the ceremonies are sprint planning (commit to the sprint's work), the daily standup (a short synchronization where the team, not a manager, coordinates), the sprint review (demonstrate the increment to stakeholders and gather feedback), and the retrospective (inspect and improve the team's own process). The core artifacts are the product backlog (the prioritized master list of everything that could be built), the sprint backlog (what the team committed to this iteration), and the increment (the potentially shippable output). Kanban instead visualizes flow on a board and limits work in progress to expose bottlenecks and improve throughput. Progress is shown with burndown or burnup charts and forecast with velocity, and value is maximized by keeping the backlog ordered so the team always pulls the highest-value ready work first. In hybrid delivery you blend these with predictive planning, for instance using a milestone plan for fixed regulatory dates while running the build in sprints, and you define clear integration points so the two cadences stay synchronized.