PMP : Process (Domain 2)
PMI – PMP : Certified Project Management Professional - Domain II - Process
The Project Management Professional (PMP) examination underwent a paradigm shift on July 9, 2026, aligning with the release of the PMBOK® Guide – 8th Edition. Within this new framework, Domain II: Process stands as the most substantial component of the assessment, accounting for 41% of the total examination weight. This domain evaluates a candidate’s ability to navigate the technical aspects of managing a project from initiation through closure, emphasizing value-based delivery, methodological tailoring, and strategic integration.
Project leadership in 2026 requires more than technical fluency; it demands a situational mindset capable of balancing predictive (waterfall), agile, and hybrid approaches. This guide synthesizes the core tasks of the Process domain, providing the analytical depth and strategic formulas necessary to master the complex situational scenarios that characterize the modern exam.
1. Methodological Tailoring and Project Life Cycles
The foundation of the Process domain is the selection and integration of project management methodologies. In the 2026 standards, the exam does not favor one approach over another; instead, it tests a leader’s ability to choose the correct framework based on project context. Approximately 60% of the exam features agile or hybrid scenarios, while 40% focuses on predictive models.
Predictive (Waterfall) Frameworks
Predictive methodologies are used when requirements are well-defined and the scope is stable. These projects emphasize structured control and adherence to established baselines. Key indicators in an exam scenario include references to a Project Charter, Change Control Board (CCB), or the Critical Path Method. Leadership in this context involves rigorous planning and formal variance analysis to ensure the project remains within the defined scope, schedule, and budget.
Agile (Adaptive) Frameworks
Agile methodologies are preferred for projects with high uncertainty or rapidly changing requirements. The focus is on iterative delivery, servant leadership, and maximizing customer value through frequent feedback. Scenario indicators include terms like Sprint, Product Owner, Backlog Refinement, or Velocity. Leaders in agile environments act as facilitators who remove impediments and empower self-organizing teams.
Hybrid Frameworks
The 2026 ECO places significant emphasis on hybrid models, where components of both predictive and agile are blended. A common hybrid scenario involves a “Hardware Stream” managed predictively due to procurement lead times and physical constraints, and a “Software Stream” managed agily to allow for iterative user interface development. Leaders must be able to synchronize these two streams, ensuring that the iterative progress of software development remains aligned with the rigid milestones of physical infrastructure.
2. Scope Management: Defining and Protecting the Project Boundary
Scope management ensures that the project includes all the work required—and only the work required—to complete the project successfully. Under the 8th Edition standards, scope is no longer a static document but a dynamic boundary that must be protected against “scope creep” while remaining flexible enough to incorporate high-value changes.
The Work Breakdown Structure (WBS) and Backlog
In predictive environments, the WBS serves as the primary tool for decomposing the total scope of work into manageable work packages. In agile environments, the Product Backlog serves a similar purpose but remains fluid, prioritized by the Product Owner based on business value.
Scope Validation vs. Quality Control
It is critical to distinguish between these two processes. Quality control is primarily concerned with the correctness of the deliverables and meeting technical requirements (inspection). Scope validation, conversely, is the process of obtaining formal acceptance of the completed project deliverables from the customer or sponsor. Validation typically occurs after quality control, ensuring that what was built is what the customer actually wanted.
Managing Scope Creep
Unmanaged changes are a primary driver of project failure. The 2026 exam tests the leader’s ability to route all changes through a controlled, transparent approach. Even “small” requests from high-level stakeholders must be evaluated for their impact on the project’s triple constraints—scope, schedule, and cost—before being approved and integrated into the plan.
3. Advanced Schedule Management and Pacing Strategy
Schedule management involves defining activities, sequencing them, and estimating durations to create a viable project timeline. The 2026 exam utilizes the “Eighty-Second Rule,” which dictates that candidates have an average of 80 seconds per question to navigate the 180-item assessment within the 240-minute window.
Critical Path and Float
The Critical Path is the longest sequence of activities in a project network diagram and determines the shortest possible project duration. Any delay in a critical path activity directly impacts the project finish date. Float (or Slack) represents the amount of time a non-critical task can be delayed without affecting the project end date. The formula for calculating float is:
- Total Float = Late Start (LS) – Early Start (ES) or Late Finish (LF) – Early Finish (EF).
Duration Estimation: PERT
For activities with high uncertainty, the Program Evaluation and Review Technique (PERT) provides a weighted average estimate:
- PERT Estimate = (Optimistic + 4 × Most Likely + Pessimistic) ÷ 6
Schedule Compression Techniques
When a project falls behind, leaders must choose between two primary compression methods:
- Crashing: Adding resources to critical path tasks to shorten duration. This increases costs and may introduce resource conflict.
- Fast-Tracking: Performing critical path activities in parallel that were originally planned in sequence. This increases risk and the potential for rework.
4. Financial Stewardship and Earned Value Management (EVM)
The Process domain requires leaders to demonstrate competence in budgeting, cost estimation, and financial performance measurement. Earned Value Management (EVM) is the primary methodology used to integrate scope, schedule, and resource measurements to assess project performance.
Essential EVM Formulas
| Metric | Formula | Interpretation |
|---|---|---|
| Cost Variance (CV) | EV – AC | Negative is over budget; Positive is under budget. |
| Schedule Variance (SV) | EV – PV | Negative is behind schedule; Positive is ahead. |
| Cost Performance Index (CPI) | EV ÷ AC | > 1.0 is under budget; < 1.0 is over budget. |
| Schedule Performance Index (SPI) | EV ÷ PV | > 1.0 is ahead of schedule; < 1.0 is behind. |
| Estimate at Completion (EAC) | BAC ÷ CPI | Forecasted total cost based on current performance. |
| Estimate to Complete (ETC) | EAC – AC | How much more money is needed to finish? |
| Variance at Completion (VAC) | BAC – EAC | The projected budget surplus or deficit. |
Budget Reserves
Leaders must distinguish between Contingency Reserves, which are allocated for “known-unknowns” (identified risks) and are within the project manager’s control, and Management Reserves, which are for “unknown-unknowns” and require sponsor approval to access.
5. Quality Management: Excellence through Prevention
Quality in the 2026 standards is defined by the degree to which a set of inherent characteristics fulfills requirements. The exam prioritizes prevention over inspection, emphasizing that quality must be planned in, not inspected in.
The PDCA Cycle and Continuous Improvement
The Plan-Do-Check-Act (PDCA) cycle forms the basis for quality improvement. In agile environments, this is manifested through Retrospectives, where the team evaluates their processes and identifies incremental improvements for the next iteration.
Cost of Quality (COQ)
COQ includes all costs incurred over the life of the product by investing in preventing non-conformance, appraising the product for conformance, and failing to meet requirements.
- Conformance Costs: Prevention (training, equipment) and Appraisal (testing, inspections).
- Non-conformance Costs: Internal Failure (rework, scrap) and External Failure (liabilities, warranty claims, lost business).
6. Resource Management and Team Optimization
Task 5 of the Process domain focuses on the acquisition, management, and development of physical and human resources. Project leaders must move beyond simple task allocation to fostering an environment of accountability and high performance.
Responsibility Assignment Matrix (RACI)
The RACI chart is the standard tool for clarifying roles and responsibilities. It ensures that for every task, there is exactly one person Accountable, while others are Responsible, Consulted, or Informed.
Resource Histograms and Leveling
A resource histogram is a bar chart showing the amount of time a resource is scheduled to work over a series of time periods. If a resource is over-allocated, the leader may use Resource Leveling, which adjusts the schedule to balance resource demand but often results in a delayed project end date. Alternatively, Resource Smoothing adjusts activities within their float to avoid affecting the critical path.
Team Development: Tuckman’s Ladder
Leaders must recognize the stages of team development to apply the appropriate leadership style:
- Forming: Team meets; focus on roles.
- Storming: Conflict arises as members test boundaries.
- Norming: Members begin to work together and adjust habits.
- Performing: Team functions as a unit; high productivity.
- Adjourning: Project ends; team disbands.
7. Procurement Strategy and Vendor Management
Procurement management involves purchasing goods or services from outside the project team. The project manager is responsible for ensuring that the procurement process remains transparent and that vendor performance aligns with project objectives.
Contract Types and Risk Allocation
The choice of contract type determines which party—the buyer or the seller—carries the most risk.
- Fixed-Price (FFP): Seller carries the highest risk. The price is set regardless of the seller’s costs.
- Cost-Reimbursable (CPFF): Buyer carries the highest risk. Buyer pays for all legitimate costs plus a fee.
- Time and Materials (T&M): Shared risk. Best for small-dollar, quick-start projects where the scope is not fully defined.
Procurement Closure
Procurement closure must occur before administrative project closure. It involves verifying that all work was completed satisfactorily, all deliverables were accepted, and final payments were made.
8. Value-Based Delivery: Outcomes Over Outputs
A core tenet of the PMBOK® Guide 8th Edition is the shift from measuring “outputs” (what we built) to “outcomes” (the value created). This requires the project leader to remain aligned with the business environment and organizational strategy.
Delivering Incremental Value
In agile and hybrid projects, value should be delivered incrementally. Rather than waiting until the end of a multi-year project to realize benefits, the team focuses on delivering a Minimum Viable Product (MVP) or functional increments that the customer can use immediately. This approach allows for earlier Return on Investment (ROI) and provides a mechanism for continuous feedback.
Benefits Realization
Leaders must track whether the project is still on track to deliver the benefits outlined in the business case. If market conditions change or a competitor releases a disruptive technology, the project manager must facilitate a review of the project vision with stakeholders to confirm that the project still provides organizational value.
9. Risk Management: Proactive Uncertainty Control
Risk is an uncertain event that, if it occurs, has a positive (opportunity) or negative (threat) effect on project objectives. The PMP exam favors a proactive approach: identifying risks before they become issues.
The Risk Management Flow
- Identify: Documentation in a Risk Register.
- Qualitative Analysis: Assessing probability and impact to prioritize risks.
- Quantitative Analysis: Numerical modeling of the combined effect of risks on project objectives.
- Response Planning:
- Threats: Avoid, Mitigate, Transfer, Accept.
- Opportunities: Exploit, Enhance, Share, Accept.
- Monitor: Tracking triggers and the effectiveness of responses.
Issues vs. Risks
An issue is a risk that has already occurred. Once a risk event takes place, it must be moved from the Risk Register to the Issue Log, where it is managed as a present problem requiring immediate attention.
10. Project Integration and Formal Closure
Integration management is the “glue” that binds all other processes together. It involves making trade-offs among competing objectives and managing the interdependencies among the project management knowledge areas.
The Change Control Process
In predictive projects, all changes to baselines must follow the formal integrated change control process:
- Analyze the Impact: Evaluate how the change affects scope, time, cost, and risk.
- Submit a Change Request: Formal documentation of the proposed change.
- CCB Review: Approval, deferral, or rejection by the governing body.
- Update Documents: Revise the project management plan and baselines.
- Communicate: Inform stakeholders of the decision.
Administrative Closure
Administrative closure is the final task in the Process domain. It involves:
- Confirming the project has met the requirements for formal completion.
- Transferring the final product, service, or result to the customer.
- Collating lessons learned and updating organizational process assets.
- Archiving project records and releasing the project team.
11. PMP Exam Mastery: Situational Decision Formulas
Success on the 2026 PMP exam depends on applying a consistent decision-making system. Candidates should utilize the following “If-Then” formulas to navigate situational questions.
Formula 1: Pause → Diagnose → Act
Use this when something goes wrong (a delay, a defect, or a stakeholder complaint).
- If an issue arises, then do not immediately “fix” it. Instead, determine the root cause, evaluate the impact on project constraints, and choose the action that prevents recurrence.
Formula 2: Align Stakeholders → Then Decide
Use this when there is conflict or unclear requirements.
- If stakeholders disagree, then facilitate a meeting to create a shared understanding of success criteria before making any commitments or technical decisions.
Formula 3: Risk First
Use this when uncertainty is introduced (a new regulation or a potential supplier issue).
- If a threat is identified, then update the risk register and analyze the impact before escalating or changing the plan. Proactive management is always preferred over reactive “heroics.”
Formula 4: Empower the Team
Use this in agile scenarios regarding team performance or internal conflict.
- If the team is struggling with productivity, then act as a servant leader. Facilitate a conversation to resolve conflict or remove the impediment rather than using a “command-and-control” approach.
Knowledge Assessment: Domain II Short-Answer Questions
1. Question: A project manager is leading a hybrid project where the server installation is managed predictively. The Earned Value (EV) is $900,000, and the Planned Value (PV) is $1,200,000. What is the current schedule status?
- Answer: The project is behind schedule.
- Explanation: The Schedule Variance (SV) is -$300,000 (900k - 1,200k), and the SPI is 0.75, both indicating that the work completed is less than what was planned for this date.
2. Question: In an agile project, a key stakeholder requests a new feature during a sprint. What is the project manager’s best next step?
- Answer: Direct the stakeholder to the Product Owner to have the feature evaluated and prioritized in the backlog.
- Explanation: In agile, the Product Owner is responsible for the backlog; the PM should not disrupt the current sprint or approve scope changes personally.
3. Question: What is the difference between crashing and fast-tracking a project?
- Answer: Crashing adds resources to save time (increasing cost), while fast-tracking performs tasks in parallel (increasing risk).
- Explanation: Both are compression techniques used when a project is behind schedule, but they carry different trade-offs regarding budget and risk.
4. Question: A project has 10 stakeholders. How many communication channels exist?
- Answer: 45 channels.
- Explanation: Using the formula [N × (N-1)] ÷ 2, we calculate [10 × 9] ÷ 2 = 45.
5. Question: When encountering a conflict between two team members regarding a technical solution, what should a project manager do first?
- Answer: Facilitate a private meeting between the two members to help them reach a collaborative resolution.
- Explanation: Conflict resolution should be handled at the lowest level possible, and private discussions prevent public embarrassment and team disruption.
6. Question: Which document should be consulted first if there is a dispute regarding the quality standards of a specific deliverable?
- Answer: The Quality Management Plan.
- Explanation: This plan defines the quality standards and metrics the project must adhere to, providing an objective basis for resolving disputes.
7. Question: A risk has occurred and is now delaying the project. Where should this be documented?
- Answer: The Issue Log.
- Explanation: Once a risk event occurs, it is no longer a “potential” threat but a “present” problem (issue) that must be tracked to resolution.
8. Question: In a predictive project, a stakeholder requests a change that will significantly improve the product but will increase the cost. What is the PM’s first step?
- Answer: Perform an impact analysis of the change on all project constraints.
- Explanation: Before submitting a change request to the CCB, the PM must understand how the change impacts schedule, cost, risk, and quality.
9. Question: What is the primary focus of “Servant Leadership” in an agile environment?
- Answer: Removing impediments for the team and shielding them from outside distractions.
- Explanation: A servant leader focuses on the needs of the team to enable high performance rather than directing their specific tasks.
10. Question: Why is the “Business Environment” domain weight increased to 26% in the 2026 ECO?
- Answer: To reflect the increased importance of strategic alignment, compliance, and delivering business value in modern project management.
- Explanation: Projects today must navigate complex external forces like AI and sustainability, requiring PMs to understand the broader organizational context.
Open-Ended Design Questions
- Scenario Analysis: You are managing a $10 million hybrid project for a global retail chain. The “Digital Experience” (Agile) and “Store Infrastructure” (Predictive) streams are interdependent. The Predictive stream is currently reporting a CPI of 1.1 and an SPI of 0.85. The Agile stream has a backlog of 500 story points with a velocity of 50 points per sprint. There are 6 sprints remaining before the holiday launch. Design a comprehensive status report for the steering committee that addresses the timeline risks and proposes a corrective action plan.
- Methodology Tailoring: A pharmaceutical company is developing a new drug (highly regulated, predictive) but needs to develop a mobile app for patient trial tracking (high uncertainty, agile). Design a project life cycle that integrates these two methodologies, specifically detailing how the Change Control Board will interact with the Agile team’s sprint cycles.
- Resource Conflict Resolution: You have a “Storming” team where a senior developer (predictive background) and a lead designer (agile background) are in constant conflict over the “definition of done.” Design a facilitation plan to move this team into the “Norming” stage, including specific artifacts you would use to clarify roles and expectations.
- Procurement Crisis: During a construction project, your primary steel supplier files for bankruptcy. This risk was identified and mitigated in your risk register with a secondary supplier and a $100,000 contingency reserve. However, the secondary supplier’s current prices are 30% higher than your original budget. Design a negotiation and communication strategy to present this to your project sponsor while maintaining the project’s financial integrity.
- Quality vs. Budget: Your quality team identifies a minor deviation in a product prototype that does not affect current functionality but may lead to maintenance issues in three years. Your project is already at its budget limit. Propose a decision-making framework to determine whether to fix the issue now using management reserves or to document it as a “known issue” for the operations team.
Glossary of Key Terms
- Agile: An iterative and incremental project management approach focused on flexibility, team collaboration, and delivering customer value.
- Backlog: A prioritized list of work for an agile team, typically managed by a Product Owner.
- Baseline: The approved version of a work product (scope, schedule, or cost) used as a basis for comparison to actual results.
- Change Control Board (CCB): A formal group responsible for reviewing, evaluating, approving, deferring, or rejecting changes to the project.
- Critical Path: The sequence of activities that represents the longest path through a project, determining the shortest possible duration.
- Earned Value Management (EVM): A methodology that combines scope, schedule, and resource measurements to assess project performance and progress.
- Hybrid: A combination of predictive and adaptive (agile) project management methodologies.
- Impediment: An obstacle that prevents an agile team from completing its work; a servant leader’s primary job is to remove these.
- Issue Log: A project document where all current problems, gaps, or conflicts are recorded and tracked.
- Mindset Fingerprint™: A diagnostic tool used in modern PMP prep to identify the wrong instincts (e.g., early escalation) that lead to incorrect situational answers.
- Minimum Viable Product (MVP): The smallest version of a product that allows the team to collect the maximum amount of validated learning with the least effort.
- Outcome: The actual result or benefit achieved through a project, as opposed to the “output” or deliverable itself.
- PERT (Program Evaluation and Review Technique): A statistical tool used to estimate the duration of a project task based on optimistic, pessimistic, and most likely scenarios.
- Predictive: A traditional, linear project management approach where the scope is defined at the beginning (also known as Waterfall).
- RACI Matrix: A chart that identifies who is Responsible, Accountable, Consulted, and Informed for various project tasks.
- Retrospective: An agile meeting held at the end of an iteration to discuss what went well and what can be improved in the next cycle.
- Risk Register: A document that serves as a central repository for all identified project risks, their analysis, and planned responses.
- Servant Leadership: A leadership style that prioritizes the growth and well-being of the team members and the removal of work obstacles.
- Sprint: A time-boxed iteration in agile (typically 2–4 weeks) during which a specific set of work is completed.
- Velocity: A measure of the amount of work an agile team can complete during a single sprint, used for forecasting future delivery dates.
Leaderboard
No scores saved yet. Be the first!
25 Questions — PMI – PMP : Certified Project Management Professional - Domain II - Process
Expand any question to reveal the correct answer and explanation.
-
1 A project manager is overseeing a hybrid development where the hardware components follow a predictive path and software follows agile sprints. A major vendor delay has occurred on the hardware side. What is the most appropriate action according to the 2026 Process domain standards?
Consider how integration management functions when different life cycles must meet at specific milestones.
Identify and coordinate the dependencies between the delayed hardware workstreams and the agile software sprints.
Effective hybrid management requires maintaining visible coordination points and managing dependencies across different methodologies to ensure overall project integration.
-
✗ Instruct the agile team to accelerate their sprints to compensate for the hardware delay.
This approach ignores the fundamental nature of the bottleneck and risks team burnout without addressing the technical dependency.
-
✗ Transition the entire project to a predictive methodology to ensure tighter control over the schedule.
Changing the entire delivery approach mid-project is a drastic measure that may not suit the software development needs and ignores the benefits of the hybrid model.
-
✗ Maintain separate schedules for both workstreams to prevent the agile team from being discouraged by waterfall delays.
Siloed scheduling prevents the project manager from identifying critical integration risks and impacts on the final delivery date.
-
-
2 While monitoring a project, you determine that the cumulative $CPI$ is $0.78$ and the $SPI$ is $1.25$. Which statement best describes the current health of the project?
Recall the meaning of index values relative to the baseline of $1.0$.
The project is significantly over budget but ahead of the planned schedule.
A $CPI$ below $1.0$ indicates poor cost efficiency, while an $SPI$ above $1.0$ indicates progress is faster than originally planned.
-
✗ The project is under budget and ahead of the planned schedule.
This misinterprets the $CPI$, as a value less than $1.0$ signifies that for every dollar spent, less than a dollar's worth of work was actually earned.
-
✗ The project is over budget and behind the planned schedule.
While the $CPI$ interpretation is correct, an $SPI$ of $1.25$ indicates the project is performing better than the schedule baseline.
-
✗ The project is under budget but behind the planned schedule.
This is the inverse of the actual performance metrics provided by the $CPI$ and $SPI$ values.
-
-
3 An agile team is currently tracking their progress using a burndown chart. If the 'Work Left' line is consistently positioned above the 'Ideal Burndown' line, what does this indicate about the sprint status?
Analyze the relationship between remaining work and the time elapsed in a burndown visualization.
The team is behind schedule and may not complete all committed story points.
On a burndown chart, a actual line above the ideal line indicates more work remains than was planned for that point in time.
-
✗ The team is ahead of schedule and will likely take on more items from the backlog.
This would only be true if the actual 'Work Left' line was below the ideal burndown line.
-
✗ The project velocity is increasing beyond the initial estimates.
A line above the ideal burndown suggests that velocity is actually lower than what is required to finish on time.
-
✗ The scope of the sprint has been reduced through backlog refinement.
Reducing scope would typically cause a sharp drop in the 'Work Left' line, bringing it closer to or below the ideal line.
-
-
4 You are managing a predictive project where the current $BAC$ is no longer viable due to a major unplanned event. Which formula should be used to calculate the $EAC$ if the current variances are expected to continue for the remainder of the project?
Look for the forecasting method that factors in current cost efficiency as a constant trend.
$EAC = BAC / CPI$
This formula is the standard projection when the current cost performance is expected to persist through the end of the project.
-
✗ $EAC = AC + (BAC - EV)$
This formula assumes that the remaining work will be performed at the originally planned rate, not the current rate of variance.
-
✗ $EAC = AC + Bottom\text{-}up\ ETC$
While valid for new estimates, this is typically used when the original assumptions are flawed, not necessarily to project current trends.
-
✗ $EAC = [AC + (BAC - EV)] / (CPI \times SPI)$
This formula is used when both cost and schedule performance impact the remaining work, which is a more complex projection than required.
-
-
5 In a predictive project environment, a project manager needs to shorten the schedule without increasing costs. Which technique is most appropriate?
Focus on the technique that relies on overlapping phases rather than adding manpower.
Fast tracking
Fast tracking involves performing activities in parallel that were originally planned in sequence, which increases risk but does not typically add direct costs.
-
✗ Crashing
Crashing involves adding resources to the critical path, which directly increases project costs to shorten the duration.
-
✗ Resource leveling
Resource leveling often extends the project schedule by balancing resource demand against limited supply.
-
✗ Resource smoothing
Smoothing adjusts activities within their float and does not change the critical path or overall project duration.
-
-
6 A project manager is working on a high-risk initiative where the scope is significantly undefined at the start. Which contract type provides the most protection for the buyer while allowing for flexibility?
Identify the arrangement most often used for staff augmentation or projects where the effort cannot be clearly estimated.
Time and Materials (T&M)
T&M contracts are suitable when the scope is not well-defined, allowing for flexibility as requirements emerge, though they require close monitoring by the buyer.
-
✗ Firm Fixed Price (FFP)
FFP contracts require a very well-defined scope to be effective; otherwise, they lead to high risk for the seller and potential disputes.
-
✗ Cost Plus Fixed Fee (CPFF)
While cost-reimbursable, these are often less flexible for quick changes than T&M and may encourage the seller to inflate costs if not managed.
-
✗ Fixed Price Incentive Fee (FPIF)
This contract still relies on a determined price ceiling and specific performance targets that are difficult to set when scope is undefined.
-
-
7 According to the 2026 PMP pacing model, what is the recommended elapsed time to complete the first 60 questions of the 180-question exam?
Calculate the time based on an average allocation of 80 seconds per question.
80 minutes
The structured pacing model suggests finishing the first section by the 80-minute mark to stay on track for the 240-minute total window.
-
✗ 60 minutes
Attempting to finish in 60 minutes leaves only 60 seconds per question, which may lead to errors in complex scenario analysis.
-
✗ 100 minutes
Taking 100 minutes for the first section would create a significant time deficit for the remaining 120 questions.
-
✗ 120 minutes
This would use half of the total testing time on only one-third of the questions, making it impossible to finish the exam without rushing.
-
-
8 A project manager is using three-point estimating to determine the duration of a critical task. If the optimistic time is 4 days, the pessimistic time is 16 days, and the most likely time is 7 days, what is the PERT weighted average?
Apply the Beta distribution formula which gives more weight to the most likely scenario.
8 days
The PERT formula is $\frac{O + 4M + P}{6}$, which in this case is $\frac{4 + (4 \times 7) + 16}{6} = 8$.
-
✗ 9 days
This result comes from the simple triangular distribution $(\frac{O+M+P}{3})$, not the weighted beta distribution (PERT).
-
✗ 7 days
This is simply the 'most likely' value and ignores the potential impact of the optimistic and pessimistic extremes.
-
✗ 10 days
This is an incorrect calculation that does not follow the standard weighting rules for duration estimates.
-
-
9 Under Domain II, Task 3 of the July 2026 ECO, what is a primary responsibility of the project manager regarding value-based delivery?
Think about how a project manager proves that the project is actually achieving its intended business purpose.
Verify that a measurement system is in place to track realized benefits.
Task 3 explicitly requires project managers to ensure that benefit tracking systems are active to validate business value.
-
✗ Independently decide which features provide the most value without stakeholder input.
Value must be identified and prioritized in collaboration with key stakeholders, not determined in isolation.
-
✗ Focus exclusively on predictive delivery to ensure the full scope is met at once.
Value-based delivery encourages examining opportunities to deliver value incrementally through agile or hybrid methods.
-
✗ Defer all value assessments to the project sponsor during the closing phase.
Business value must be examined throughout the project lifecycle, not just at the very end.
-
-
10 When managing a Kanban-based project, which metric should the project manager analyze to measure the total time from when a work item is added to the backlog until it is completed?
Distinguish between the total customer-facing wait time and the internal processing time.
Lead time
Lead time measures the full duration from the moment a request is entered into the system until it is fully delivered to the customer.
-
✗ Cycle time
Cycle time only measures the time a work item spends 'In Progress' once the team actually starts working on it.
-
✗ Throughput
Throughput measures the number of items completed in a specific timeframe, rather than the duration for a single item.
-
✗ Velocity
Velocity is a Scrum metric used to track the volume of work completed per sprint, whereas lead time is a specific flow metric.
-
-
11 A project manager is faced with a critical resource abdicating mid-project. According to the 'if-then' situational logic, what should the PM do first?
Consider the core PMI principle of investigation before implementation.
Analyze the impact of the loss on project objectives before taking action.
The first step in any project problem is to analyze the situation to understand the depth of the impact on scope, schedule, and cost.
-
✗ Immediately request a replacement from the functional manager.
Requesting a replacement without an impact analysis may lead to acquiring the wrong skillset or overreacting to a manageable gap.
-
✗ Update the project schedule to reflect a delay.
Adjusting the schedule is a reactive measure that should only occur after a thorough assessment and change request process.
-
✗ Inform the customer that certain features must be removed to meet the deadline.
Reducing scope is a significant change that should be a last resort after exploring other resource optimization techniques.
-
-
12 The project's $TCPI$ based on the $BAC$ is $1.21$, while the current $CPI$ is $0.92$. What does this indicate about the project's future work?
Compare the efficiency required to finish the project to the efficiency achieved thus far.
The project must become significantly more efficient to finish within the original budget.
A $TCPI$ higher than $1.0$ (and specifically higher than the current $CPI$) means the team must work harder/more efficiently than they have to date.
-
✗ The project is performing well and will likely finish under budget.
A $CPI$ below $1.0$ and a $TCPI$ above $1.0$ are indicators that the project is currently overspending and facing a difficult recovery.
-
✗ The remaining work is less complex and can be handled with current efficiency.
The $TCPI$ does not measure task complexity; it measures the required efficiency rate relative to what is left in the budget.
-
✗ The project manager should lower the $BAC$ to make the goal more attainable.
Lowering the $BAC$ would actually increase the required $TCPI$ even further, making the target even harder to reach.
-
-
13 Which component is included in the Scope Baseline of a predictive project?
Think of the three specific documents that together define exactly what work must be performed.
WBS Dictionary
The Scope Baseline consists of the Project Scope Statement, the WBS, and the WBS Dictionary.
-
✗ Project Charter
The Project Charter is an initiating document that authorizes the project but is not part of the finalized scope baseline.
-
✗ Resource Management Plan
This is a separate subsidiary plan within the Integrated Project Management Plan and does not define the scope work packages.
-
✗ Product Backlog
The Product Backlog is used in agile methodologies, whereas the Scope Baseline is a concept from predictive project management.
-
-
14 During a sprint, the Product Owner requests the team to add a critical new feature that was not part of the sprint planning. How should the team respond?
Reflect on how agile protectively manages the team's capacity and focus during an active iteration.
Advise the Product Owner to add the item to the Product Backlog for prioritization in the next sprint.
In agile, the sprint backlog is generally fixed during the sprint to maintain focus; new items must go to the product backlog for future consideration.
-
✗ Add the feature immediately and work overtime to ensure the sprint goal is met.
This violates agile principles of sustainable development and disrupts the team's commitment to the current sprint goal.
-
✗ Stop the current sprint and start a new one that includes the new feature.
Canceling a sprint is a drastic measure only taken if the sprint goal becomes obsolete, which is not necessarily the case with a new request.
-
✗ Wait for the Daily Scrum to ask the Scrum Master for permission to change the scope.
The Daily Scrum is for coordination, not for making scope changes or seeking permissions for backlog adjustments.
-
-
15 You are assessing project quality and want to include the new 2026 sustainability focus. Which activity aligns with 'Plan and optimize quality' under Domain II, Task 7?
Consider how the definition of 'quality' has expanded to include the total lifecycle and broader impact of deliverables.
Incorporate Cost of Quality (CoQ) analysis that factors in long-term environmental impacts.
The 2026 update specifically expands Task 7 to include sustainability and optimization through a more comprehensive view of quality costs.
-
✗ Remove quality checks to reduce the project's carbon footprint.
Sustainability should enhance quality standards, not compromise them by removing necessary verification steps.
-
✗ Focus exclusively on meeting minimum regulatory requirements to save resources.
Optimization implies going beyond mere compliance to deliver better value and more sustainable outcomes.
-
✗ Assign a separate team to handle sustainability so the project team can focus on technical quality.
Sustainability is now an integrated part of the process domain and should be handled by the core project management team.
-
-
16 A project manager is coordinating multiple workstreams. If they decide to use 'Resource Leveling' on the critical path, what is the most likely outcome?
Consider the trade-off made when you prioritize not overworking your staff over meeting a specific date.
The project completion date will likely be delayed.
Resource leveling often results in the critical path changing or lengthening because it prioritizes resource availability over schedule constraints.
-
✗ The project risk will decrease significantly without schedule changes.
While leveling can reduce resource-related risk, it almost always impacts the project timeline.
-
✗ Costs will be reduced by utilizing lower-skilled resources.
Leveling is about timing and availability of existing resources, not about changing the resource type to save money.
-
✗ The schedule will be compressed to meet a new aggressive deadline.
Leveling is the opposite of compression; compression (crashing/fast-tracking) tries to shorten the schedule, while leveling usually lengthens it.
-
-
17 When a sponsor requests a deliverable that is significantly outside the approved scope without a formal request, what is the PM's first procedural step according to the 'Process' domain?
Think about the necessary step between 'hearing a request' and 'taking formal action'.
Meet with the sponsor to clarify the request and document the gap against the baseline.
The first step is always to gather more information and define the specific difference between the current plan and the new request.
-
✗ Submit a change request immediately to show the sponsor you are being proactive.
A change request should only be submitted after the PM has clarified the need and understood the potential impact.
-
✗ Inform the team to start planning the change since the sponsor has the authority.
Work should not begin on out-of-scope items until the formal change control process has been completed and approved.
-
✗ Reject the request because it was not made through the formal change control board.
Outright rejection is unprofessional; the PM must facilitate the process by which the request can be evaluated.
-
-
18 In a project using the Delphi technique for cost estimation, how are the expert opinions gathered to ensure the best results?
Identify the method used to minimize the influence of dominant personalities on a group decision.
Anonymously through multiple rounds to prevent groupthink.
The core principle of the Delphi technique is anonymity to ensure experts provide unbiased opinions without being influenced by others.
-
✗ In a face-to-face workshop to encourage open debate.
Face-to-face meetings can lead to peer pressure or the 'loudest voice' dominating, which the Delphi technique explicitly tries to avoid.
-
✗ By averaging the highest and lowest estimates without further discussion.
Simple averaging does not capture the refinement and consensus-building that defines the iterative Delphi process.
-
✗ By using historical data to override current expert opinions.
The Delphi technique is used to gather current expert judgment, not to validate historical records.
-
-
19 A project is 40% complete. $PV = \$100,000$, $EV = \$80,000$, and $AC = \$90,000$. What is the current Cost Variance ($CV$)?
Calculate the difference between the value of the work performed and the actual money spent.
$\text{-}\$10,000$
$CV = EV - AC$, which is $\$80,000 - \$90,000 = \text{-}\$10,000$.
-
✗ $\$10,000$
This ignores the fact that actual costs were higher than the earned value, which should result in a negative variance.
-
✗ $\text{-}\$20,000$
This calculation incorrectly uses the $PV$ ($EV - PV$) which would give the Schedule Variance, not the Cost Variance.
-
✗ $\$20,000$
This is an incorrect calculation that does not represent any standard EVM variance metric.
-
-
20 Domain II, Task 9 of the July 2026 ECO focuses on 'Evaluating project status'. Which of the following is a new key emphasis in this consolidated task?
Consider the importance of project 'paperwork' and records in proving the current health of the project.
Continually assessing the effectiveness of artifact management.
Task 9 now includes the ongoing review of how artifacts are created, updated, and made accessible throughout the project.
-
✗ Focusing solely on the final deliverable and ignoring intermediate artifacts.
Evaluating status requires managing and reviewing artifacts throughout the project lifecycle, not just at the end.
-
✗ Automating all status reporting so the project manager does not have to review data.
The task requires the PM to collect and analyze data to make informed decisions, which cannot be entirely delegated to automation.
-
✗ Ensuring that only predictive metrics are used to maintain consistency.
Status evaluation must include metrics appropriate for the delivery approach, whether it's predictive, agile, or hybrid.
-
-
21 An agile team is struggling with work items getting stuck in the 'In Progress' column. Which Kanban principle should the project manager recommend to improve the flow of value?
Think about the rule that stops a team from starting too many things at the same time.
Limit Work in Progress (WIP).
Limiting WIP prevents bottlenecks by forcing the team to finish existing tasks before starting new ones, thereby improving overall flow.
-
✗ Increase the number of staff in the development team.
Adding staff to a bottleneck often increases communication overhead and may not resolve the underlying process issue.
-
✗ Extend the duration of the sprint.
Kanban typically does not use fixed-length sprints, and extending time does not address the inefficiency in work transitions.
-
✗ Schedule more frequent status meetings to track each item.
More meetings usually reduce the time available for actual work and do not fix the structural problem of too many active tasks.
-
-
22 A project manager is performing 'Manage closure' under Task 10 of the Process domain. What is the final activity they should perform after transferring the deliverables to the operational team?
Identify the step that ensures the company learns something from the project's experience.
Update organizational process assets (OPAs) with lessons learned.
Final closure requires capturing knowledge and updating the organization's database to benefit future projects.
-
✗ Release the project team immediately after the product is handed over.
The team should not be released until administrative closing, including lessons learned and final reporting, is complete.
-
✗ Start the procurement process for the next project phase.
Closure focuses on finishing the current project/phase, not initiating new work elsewhere.
-
✗ Conduct a final audit to find out who was responsible for project defects.
Closure should be a constructive process focused on improvement and celebration, not a punitive search for blame.
-
-
23 Task 1 of the Process domain now explicitly includes 'sustainability' in what specific way?
Think about the planning stage where the project manager decides what data is necessary to track.
Determining critical information requirements related to sustainability.
The 2026 ECO requires project managers to identify sustainability data as a core part of the integrated project management plan.
-
✗ Mandating that every project must have a zero-carbon footprint.
The ECO requires management and planning for sustainability, but it does not dictate specific environmental results for every project.
-
✗ Replacing the business case with a sustainability case.
Sustainability is an added dimension of the project requirements, not a replacement for the financial and strategic business case.
-
✗ Outsourcing all sustainability reporting to an external agency.
The PM is responsible for recommending the execution strategy and creating the plan, which includes these requirements.
-
-
24 A project has a total budget ($BAC$) of $\$500,000$. Currently, the project is $50\%$ complete, but the actual costs incurred ($AC$) are $\$300,000$. What is the current $CPI$?
Divide the value of the work actually achieved by the total amount spent so far.
$0.83$
$EV = 50\% \times \$500,000 = \$250,000$. $CPI = EV / AC$, so $\$250,000 / \$300,000 = 0.833$.
-
✗ $1.20$
This result comes from $AC / EV$, which is the inverse of the Cost Performance Index.
-
✗ $0.60$
This calculation incorrectly uses the entire $BAC$ or another unrelated ratio.
-
✗ $1.66$
This is an incorrect calculation that does not reflect any standard performance index.
-
-
25 A project manager is creating a project schedule. According to Domain II, Task 8, which of the following is an expected activity when using an adaptive approach?
Identify the estimation unit commonly used by teams to measure relative effort rather than calendar time.
Estimating project tasks using story points.
Task 8 specifically mentions estimating milestones, dependencies, and story points based on the selected development approach.
-
✗ Creating a detailed Gantt chart for the entire two-year project duration.
Adaptive approaches use rolling wave planning or iterative backlogs rather than highly detailed long-term sequential charts.
-
✗ Ensuring no changes are allowed to the schedule after the baseline is set.
Adaptive schedules are designed to be flexible and evolve based on continuous feedback and reprioritization.
-
✗ Assigning specific dates to every individual task in the product backlog.
Product backlog items are prioritized by value and pulled into sprints; they typically do not have fixed start/stop dates until committed.
-