PMI PMP Practice Test: Current Exam

Use this PMP exam simulator page when you want one place to try realistic PMP sample questions, review detailed explanations, and move straight into the full PM Mastery experience on web, iOS, or Android for the current PMP blueprint before July 9, 2026. The goal here is not generic project-management reading. It is exam-style decision practice for people searching for a PMP mock exam, PMP practice test, or PMP simulator they can start now.

If your scheduled PMP exam date is July 9, 2026 or later, switch to PMP 2026 instead. PMI’s refresh changes the weighting enough that post-cutover candidates should practice from the separate page rather than study entirely from the current mix. If your actual goal is project controls, cost engineering, estimating, scheduling, risk, or construction claims, compare AACE before defaulting to the broad PMP route.

For official PMI references, see the current PMP certification page and the refreshed new PMP exam page .

Free diagnostic: Try the 180-question PMP full-length practice exam before subscribing. Use it only for the current PMP route before July 9, 2026; if your appointment is on or after that date, switch to PMP 2026 .

What this PMP practice page should do for you

• show you what PMP exam questions feel like before you subscribe
• give you realistic scenario-based PMP practice questions with explanations
• keep you on the current PMP blueprint if your exam date is before July 9, 2026
• make it easy to start a PMP mock exam on web immediately
• route you to the same PM Mastery subscription on App Store, Google Play, and web
• help existing subscribers continue with the same PM Mastery account across devices

What premium unlocks in PM Mastery

• the full 2,865-question PMP bank instead of the smaller free preview
• more timed mock exams and mixed review sets
• topic drills across weak areas
• progress tracking and review history
• the same PM Mastery subscription across web, iPhone, iPad, and Android

Which PMP page should you use?

PMP exam snapshot

For the latest official exam details and requirements, see: https://www.pmi.org/certifications/project-management-pmp

Source: PMP Examination Content Outline, January 2021 exam update.

• Exam version on this page: current PMP exam before July 9, 2026
• Exam time (center-based): 230 minutes
• Items: 180 total, including 5 unscored pretest items
• Breaks: 2 x 10-minute breaks after questions 1-60 and 61-120, after review
• Eligibility (summary): project management experience plus 35 contact hours of formal PM education, waived for active CAPM holders; experience must be within the last 8 years

Note (PMI): the exam reflects predictive, agile, and hybrid project environments.

Official PMP domain weights

The ECO specifies the proportion of items by domain:

Current PMP vs PMP 2026 at a glance

Current PMP decision filters

Use these filters for the current pre-refresh PMP page. They help you avoid answering from habit when the scenario is really testing tailoring, leadership, or governance.

Current PMP readiness map

PMP formulas worth recognizing under pressure

You do not need to turn PMP into a pure math exam. You do need to recognize what the common formulas mean quickly enough to make the right project decision.

The two sign checks that matter most are:

The two index checks that PMP candidates should read almost instantly are:

If the exam asks for a quick forecast and gives no special constraint, the common continuation-of-current-performance shortcut is:

Fast PMP formula readout

What good PMP practice should train

• Best next step thinking: what to do first, next, or most effectively given constraints.
• Tailoring: choosing predictive vs agile vs hybrid practices that fit uncertainty, compliance, and stakeholder needs.
• Governance realism: escalation paths, approvals, and auditability when required.
• Trade-offs: scope, schedule, cost, and quality decisions framed around value and risk.
• Stakeholder craft: influence without authority, conflict resolution, and clear communication.

Common PMP simulator mistakes

• Trying to memorize processes without understanding intent.
• Over-committing to one delivery style instead of fitting the scenario.
• Treating risk, issue, change, and defect as interchangeable.
• Doing math mechanically without interpreting what the numbers imply.

Final 7-day current PMP practice sequence

Use this sequence only if your exam date is before July 9, 2026.

When current PMP practice is enough

If you can score above 75% on several unseen mixed or timed attempts and explain the project-management logic behind misses without recognizing the question, you are likely ready for the current PMP. Repeating a large bank until familiar wording drives your score can become overtraining; the real exam rewards fresh judgment, not item memory.

24 PMP sample questions with detailed explanations

These are original PM Mastery practice questions aligned to PMP People, Process, and Business Environment decision patterns. They are not PMI exam items, are not copied from any exam sponsor, and should be used to practice scenario judgment rather than memorize exact wording. Use them to check your readiness here, then continue in PM Mastery with mixed sets, topic drills, and timed mocks.

Question 1

Topic: Domain II: Process

You are planning a predictive infrastructure upgrade project. Governance requires an approved cost baseline and monthly cost forecasts, and the sponsor wants variance reporting that compares actual performance to the plan.

Which TWO actions should you take to set up cost tracking and forecasting for this project?

• A. Time-phase the approved budget by work package to create the cost baseline and get it formally approved
• B. Include management reserve in the cost baseline to reduce the chance of negative variances
• C. Forecast remaining costs using a fixed monthly burn rate, independent of completed work and remaining scope
• D. Report only total spend versus total budget at the end of each phase to avoid unnecessary detail
• E. Define how EV and AC will be measured each period, then use CV/CPI trends to forecast EAC/ETC
• F. Rebaseline whenever actual costs differ from the plan so reports stay aligned to current spending

Best answers: A, E

Explanation: To track variances, you need an approved, time-phased cost baseline so performance can be compared period by period. To forecast credibly, you also need a defined method to measure earned value and capture actual cost at a regular cadence, then use variance and performance trends to estimate EAC/ETC. Together these establish planned performance and enable ongoing variance tracking and forecasting.

Cost performance control depends on having a time-phased cost baseline (planned value) that is approved and can be compared to actual results over time. Once execution starts, define consistent measurement for earned value (how progress is credited) and actual cost (how costs are collected), then compute cost variance and performance indices to identify trends and produce forecasts such as EAC/ETC.

A practical setup is:

• Build the cost baseline by time-phasing the authorized budget across scheduled work.
• Establish a reporting cadence for EV and AC, and use CV/CPI trends to forecast at completion.

Management reserve is not part of the baseline, and rebaselining is reserved for approved scope/baseline changes through change control.

Question 2

Topic: Domain II: Process

You are the project manager starting planning for a new solution. Review the following project charter excerpt.

Charter excerpt:
- Regulatory reporting module must meet new law by Oct 1 (non-negotiable)
- UX features for field agents are unclear; users want frequent demos
- Funding released in 3 tranches after governance board reviews
- External vendor will build reporting module under fixed-price contract

Based on the exhibit, what is the best approach to selecting the lifecycle and defining how planning and governance will operate?

• A. Use predictive; baseline all scope/schedule; CCB controls all changes.
• B. Use agile; manage everything via product backlog and sprint reviews.
• C. Keep methodology undecided; start executing and tailor governance later.
• D. Use hybrid; predictive stage-gates for compliance, agile iterations for UX.

Best answer: D

Explanation: The fixed, non-negotiable regulatory deadline and fixed-price vendor work support a predictive plan with defined governance checkpoints. At the same time, the unclear UX needs and desire for frequent demos support iterative, agile planning and delivery. A hybrid approach aligns tranche funding and governance reviews to stage-gates while enabling rolling-wave refinement for the UX backlog.

Select a hybrid lifecycle because the exhibit contains both high-certainty, compliance-driven work and high-uncertainty product discovery work. The regulatory reporting module has a fixed deadline and is being delivered via a fixed-price vendor contract, so it benefits from upfront planning, clear acceptance criteria, and governance stage-gates tied to tranche funding. The UX portion has evolving requirements and stakeholders who want frequent demos, so it should be planned and delivered iteratively with a prioritized product backlog and regular reviews.

Practical setup:

• Predictive plan/baseline and formal approvals for the regulatory module
• Agile iterations for UX with frequent demos and backlog refinement
• Governance board reviews aligned to tranche releases and integrated decisions

This tailoring creates control where constraints are tight while preserving adaptability where uncertainty is high.

Question 3

Topic: Domain III: Business Environment

A hybrid project is delivering a mobile banking app. The team uses two-week sprints for development, but the scope baseline and funding are controlled through a change control board (CCB). Midway through the current sprint, a new external regulation is announced that will require additional audit logging and customer-consent screens for compliance by the planned go-live date in 10 weeks. The sponsor says the launch date cannot move and there is no additional budget.

What is the project manager’s BEST next action?

• A. Work with product owner to assess impact and reprioritize backlog
• B. Direct the team to start building the compliance features immediately
• C. Defer the change until after launch to avoid disrupting the sprint
• D. Update the scope baseline and schedule to include the change

Best answer: A

Explanation: An external regulatory change can alter required scope, so the project manager should first perform a rapid impact assessment and translate it into prioritized scope/backlog options. Because date and budget are fixed and governance controls baselines, the next step is to collaborate with the product owner and key stakeholders to reprioritize and prepare a decision package for approval. This enables an informed trade-off decision while maintaining compliance by go-live.

The core skill is evaluating an external business environment change and prioritizing its impact on project scope/backlog before committing the team to work. A new regulation creates mandatory requirements that may displace lower-value items when time and budget are constrained.

A practical next-action sequence is:

• Confirm and clarify the regulatory requirement and deadline.
• Perform a fast impact assessment (scope, effort, risk, dependencies).
• Convert the impact into backlog/scope options and reprioritize with the product owner.
• Take the recommended option to the CCB/sponsor for approval and communicate the decision.

Starting work without alignment can waste capacity, while changing baselines without approval breaks governance; prioritization enables compliance within fixed constraints.

Question 4

Topic: Domain II: Process

A hybrid project is integrating a new billing platform with a 24/7 operations environment. Work has recently stalled twice because a critical access exception was needed within hours, but the team was unsure who could approve it and when to involve the sponsor versus the security governance board. The sponsor asks the project manager to prevent future delays by making decision authority and escalation triggers explicit.

What should the project manager create or update first?

• A. An escalation matrix defining thresholds and the escalation path
• B. A RACI chart for project deliverables and activities
• C. A change control board charter for approving scope changes
• D. The issue log with owners and due dates for each issue

Best answer: A

Explanation: The immediate gap is unclear decision authority and when to escalate time-sensitive exceptions. An escalation matrix (often part of governance/communications) defines escalation thresholds (for example, severity, time, impact) and the route and timing for escalation to the right decision makers. This directly reduces delays caused by uncertainty in urgent situations.

Defining escalation paths and thresholds is a core governance activity: it clarifies who has authority to decide at different impact levels and when an item must be elevated. In this scenario, the decisive factor is time-critical operational decisions (access exceptions) that must be made quickly and consistently across multiple governance bodies.

An effective escalation matrix typically specifies:

• Thresholds (severity, cost/schedule impact, risk, compliance, time-to-decision)
• Decision owner at each threshold (team lead, PM, sponsor, governance board)
• Escalation route and required response time (timeboxed)
• Communication channel and documentation expectations

Other artifacts may support governance, but they do not, by themselves, define escalation triggers and decision limits needed to stop urgent-work delays.

Question 5

Topic: Domain II: Process

A hybrid software project has a fixed go-live date committed to a regulator. After four iterations, the sponsor asks the project manager to provide objective evidence that the team is on track to meet the date, despite some ongoing requirement refinement.

Which metric or artifact best validates schedule progress for this context?

• A. Count of user stories currently in progress
• B. Release date forecast using historical velocity and cycle time
• C. Hours spent to date compared to the labor budget
• D. Percent complete reported against the baseline schedule

Best answer: B

Explanation: To validate whether the fixed date is still achievable, the strongest evidence is a forward-looking forecast grounded in benchmarks and actual performance. Using the team’s historical velocity/cycle time trend to project completion connects observed delivery capability to remaining scope and the target date, providing objective schedule validation.

When schedule commitment matters, validation should rely on evidence that predicts finish based on how the team has actually been performing, not on activity reporting. In hybrid/agile delivery, a release forecast derived from historical velocity (or throughput) and cycle time uses real performance data as a benchmark to estimate how much work can be completed by the committed date.

A practical validation approach is:

• Use completed iterations to establish a stable velocity/throughput range
• Convert remaining backlog to an equivalent number of iterations (or time)
• Compare the forecasted completion to the committed go-live date

This provides decision-grade schedule evidence, while simple progress tallies can hide rework, changing scope, and optimistic status reporting.

Question 6

Topic: Domain I: People

During a steering committee meeting, the executive sponsor abruptly says, “This project is slipping again-you’re wasting my team’s time,” and begins speaking faster and louder. You notice she repeatedly references a recent production outage that was unrelated to your project. You have 5 minutes left on the agenda and must leave the meeting with clear next steps and maintain the sponsor’s support.

What should the project manager do next to best address the stakeholder’s emotional needs while meeting the meeting objective?

• A. Escalate the sponsor’s behavior to the PMO after the meeting and request the PMO facilitate future steering sessions
• B. End the meeting early and send a written status update later to avoid further conflict in front of the group
• C. Acknowledge the concern, ask a brief clarifying question about what’s driving the urgency, then propose an immediate 10-minute follow-up 1:1 to align on expectations and next steps
• D. Present the latest schedule variance and corrective actions in detail to demonstrate control and rebuild confidence

Best answer: C

Explanation: The sponsor’s heightened tone and fixation on a recent outage are behavioral cues of stress and perceived risk. The best response is to first validate the concern and use a calm, curious question to uncover what is driving the emotion, then quickly secure a follow-up to finalize expectations and actions. This adapts communication to the stakeholder’s emotional state while still protecting the meeting outcome.

Emotional intelligence in stakeholder communication starts with noticing behavioral triggers (raised voice, accelerated speech, repeated references to a fear-inducing event) and responding in a way that lowers threat and restores collaboration. In the moment, the project manager should acknowledge the emotion and concern, then use a short, open question to understand what is behind the urgency (e.g., impact to the sponsor’s priorities or reputational risk). Because time is limited, the PM should also propose a near-term 1:1 to confirm expectations and agree on next steps, ensuring the sponsor feels heard while still creating a clear decision path. Data and process are useful after de-escalation; leading with them can feel dismissive when a stakeholder is emotionally escalated.

Key takeaway: address the emotion first, then align on action.

Question 7

Topic: Domain III: Business Environment

A project is developing a cloud solution for a regulated financial institution. During planning, the project manager works with the compliance office to translate regulations into measurable requirements and acceptance criteria, adds compliance-related risks and responses to the risk register, builds verification activities into the quality management plan (including planned audits), and includes required controls and documentation deliverables in vendor SOWs and contracts.

Which PM principle/governance concept does this best represent?

• A. Rely on integrated change control when regulators raise concerns
• B. Embed compliance requirements into scope, quality, risk, and procurements
• C. Transfer compliance responsibility to the vendor through the contract
• D. Defer compliance details until execution to stay agile

Best answer: B

Explanation: The described actions show proactive compliance management by converting regulatory obligations into explicit requirements and then integrating them into core planning artifacts. That includes scope/acceptance criteria, risk responses, quality verification, and procurement terms so compliance is built in and verifiable. This approach supports governance expectations and reduces late rework and audit findings.

Integrating compliance means treating legal/regulatory obligations as required project requirements, not as optional “checks” at the end. In practice, the project manager collaborates with compliance and other SMEs to define measurable compliance requirements and acceptance criteria, then plans how those requirements will be met and evidenced through quality activities (reviews, tests, audits) and procurement documents (SOW, contract deliverables, and right-to-audit/verification expectations). Compliance-driven uncertainties are also planned as risks with appropriate responses. The key idea is to build compliance into the scope baseline/backlog, risk register, quality management approach, and vendor agreements early, rather than relying on late changes or shifting accountability.

Question 8

Topic: Domain III: Business Environment

A hybrid project is in execution delivering a new customer portal. The organization announces an immediate, enterprise-wide pause on all external vendor spending until a newly formed finance committee completes a review. Your project relies on a contracted UX vendor for work scheduled to start next week, and there is no schedule contingency before the next milestone.

If the project manager takes no action, what is the most likely near-term impact to the project?

• A. Defect rates will increase because the team will cut testing
• B. Near-term milestone delays due to the paused UX vendor work
• C. The business case will be rewritten to reflect new corporate strategy
• D. The UX contract will be automatically terminated and rebid

Best answer: B

Explanation: The organizational change directly affects a critical resource the project planned to use next week. With no contingency before the next milestone, the most likely immediate consequence is schedule slippage unless the project is replanned, alternative resourcing is found, or an escalation/approval path is used.

Organizational changes (restructures, funding controls, new governance) can immediately constrain resources, approvals, or ways of working. Here, the enterprise spending pause blocks the contracted UX vendor from starting planned work, so the project’s near-term constraint is capacity and schedule, not strategy or long-range value.

A project manager should quickly assess and communicate the impact and pursue an approved path forward, such as:

• Confirm the policy details and decision timeline with governance
• Update the schedule/forecast and inform affected stakeholders
• Propose alternatives (temporary internal staffing, resequencing, or a formal exception request)

Longer-term artifacts like the business case may be revisited later, but the immediate impact is the inability to execute the planned vendor-dependent work on time.

Question 9

Topic: Domain I: People

A hybrid project is implementing a new customer onboarding process across Sales, Compliance, and IT. The teams disagree on what “done” means for onboarding, and recent meetings have ended without decisions. The sponsor wants a shared, documented agreement within two weeks, without increasing budget, and several stakeholders are remote.

What should the project manager do to best optimize reaching consensus under these constraints?

• A. Facilitate a timeboxed cross-functional workshop using a process map and user stories to visualize the end-to-end flow, then capture agreed acceptance criteria and ownership for open items
• B. Send a detailed requirements document to stakeholders and request emailed approvals to avoid scheduling challenges
• C. Meet individually with each stakeholder group to negotiate their requirements, then publish the project manager’s consolidated definition of done
• D. Escalate the disagreement to the steering committee and ask them to decide the definition of done to keep the project on schedule

Best answer: A

Explanation: A structured, timeboxed workshop that uses visual models (process map and user stories) aligns diverse stakeholders by making assumptions, handoffs, and outcomes explicit. It is efficient within a two-week window, works well with remote participation, and results in a documented agreement (acceptance criteria and ownership) rather than more discussion. This directly builds shared understanding and enables decisions.

When stakeholders can’t align on requirements or “done,” the fastest path to consensus is usually a facilitated session that makes the work visible and concrete. A process map clarifies the end-to-end workflow, handoffs, and compliance touchpoints, while user stories (and related acceptance criteria) translate those steps into testable outcomes that teams can agree to. Timeboxing keeps the effort within the two-week constraint, and capturing decisions (plus owners for unresolved items) turns conversation into a shared, actionable agreement.

A governance escalation can be necessary later, but it doesn’t build the shared understanding needed to sustain alignment as details emerge.

Question 10

Topic: Domain I: People

You are assigned to lead a newly formed, mostly remote, cross-functional team on a hybrid project with an aggressive delivery date. Several team members are new to the organization and confusion about “who decides what” is already causing delays in getting environments and approvals.

Which TWO actions should the project manager take to plan onboarding and role clarity to accelerate team formation and productivity? (Select TWO)

• A. Create a structured onboarding plan with a short checklist, access/setup steps, and a buddy for each new member
• B. Distribute the project schedule and WBS and require each member to sign that they understand it
• C. Ask functional managers for detailed skill matrices and wait for their approvals before introducing team members
• D. Introduce individual incentives tied to early deliverable completion to increase personal accountability
• E. Begin execution immediately and allow roles and decision-making to emerge naturally during delivery
• F. Facilitate a session to define and publish roles, responsibilities, and decision/approval ownership for key work

Best answers: A, F

Explanation: To accelerate team formation, remove start-up barriers and reduce ambiguity. A lightweight onboarding plan gets people productive quickly (access, tools, context, key contacts), and explicit role/decision clarity prevents delays caused by unclear ownership-especially in a remote, cross-functional environment.

The core need is faster ramp-up and fewer coordination delays. A deliberate onboarding plan addresses practical readiness (access, environments, tools, context, and key relationships) so new members can start contributing without repeated interruptions. Role clarity addresses social and process readiness by making ownership and decision rights explicit, reducing waiting, rework, and duplicated effort.

Practical implementation can be lightweight:

• Publish a first-week onboarding checklist and assign a peer buddy/mentor
• Hold a short workshop to agree on responsibilities and decision/approval owners, then share the output
• Reinforce these agreements in recurring ceremonies and communications

The goal is to shorten time-to-productivity while creating clear accountability paths for work and decisions.

Question 11

Topic: Domain III: Business Environment

A project is rolling out a new enterprise time-reporting process that will change how 600 employees submit hours. Early feedback showed strong resistance from a key department, so the project manager implemented interventions (change champions, targeted coaching, updated job aids, and manager-led Q&A sessions). Two weeks before go-live, the sponsor asks for evidence that stakeholder readiness and acceptance have improved.

Which evidence best validates progress toward engagement and acceptance?

• A. Training completion rates for all impacted employees
• B. Number of change communications sent and intranet page views
• C. A follow-up change readiness and resistance assessment comparing baseline vs. current results by stakeholder group
• D. Project status report showing milestones are on track for go-live

Best answer: C

Explanation: To validate improved engagement and acceptance, use evidence that measures readiness and resistance outcomes, not just completed activities. Repeating a structured readiness/resistance assessment and comparing it to the baseline (segmented by stakeholder group) shows whether interventions are changing adoption intent and confidence where it matters. This directly supports a go/no-go readiness conversation before deployment.

When supporting organizational change, progress is best validated by outcome evidence that indicates people are willing and able to adopt the change (readiness) and that resistance is decreasing. Because the problem was resistance in a specific department, the strongest validation is a follow-up readiness/resistance assessment that can be compared to the baseline and analyzed by stakeholder group.

Practical indicators a readiness assessment can capture include:

• Understanding of the change and its impacts
• Confidence/ability to perform the new way of working
• Willingness to adopt and perceived value
• Remaining concerns that require additional interventions

Activity outputs (training delivered, messages sent) may enable readiness but do not confirm acceptance. Schedule performance also does not demonstrate that people are prepared to adopt the new process.

Question 12

Topic: Domain II: Process

A software product team is using a Kanban board within a hybrid project to deliver a high-priority regulatory update in 6 weeks. The board shows 12 items in progress for a 6-person team, and average cycle time has increased for three consecutive weeks. Most items are waiting in testing, and stakeholders keep asking the team to start additional requests “so nothing is idle.”

What is the BEST next action for the project manager to improve flow and deliver value sooner?

• A. Extend iterations and authorize overtime to recover schedule
• B. Start more items so developers stay fully utilized
• C. Run a lessons learned workshop to identify process waste
• D. Set WIP limits and focus on clearing the testing bottleneck

Best answer: D

Explanation: The main problem is too much work started and a clear testing bottleneck, which increases queues and cycle time. The best next step is to limit WIP and shift team focus to finishing work by addressing the constraint (testing) before pulling in new items. This directly improves flow and accelerates delivery of the regulatory update.

Improving flow means optimizing for completed work, not maximum utilization. With many items in progress and most waiting in testing, the system is overloaded and the bottleneck is creating queues (waste) that stretch cycle time. A practical next action is to set explicit WIP limits per workflow state and enforce a pull approach, then swarm/cross-skill to clear the testing constraint and remove blockers. This reduces multitasking and handoff delays, shortens cycle time, and increases throughput of done items-critical when urgency and a near-term deadline drive value.

The key takeaway is to stop starting and start finishing by constraining WIP around the bottleneck.

Question 13

Topic: Domain I: People

You are managing a hybrid product implementation with a distributed delivery team. Recently, work has been re-opened late in the iteration and decisions are being revisited.

Exhibit: Working agreement excerpt (current)

Done = code complete and merged
Acceptance = Product owner reviews "when available"
Decisions = made asynchronously in chat
Meetings = daily standup optional for remote members
Conflicts = escalate to project manager

Based on the exhibit, what should the project manager do next to restore predictable delivery?

• A. Rebaseline the schedule to reflect ongoing rework
• B. Escalate to the sponsor to mandate attendance and approvals
• C. Add more status meetings to catch issues earlier
• D. Facilitate updating the agreement with DoD and decision rules

Best answer: D

Explanation: The exhibit shows weak and ambiguous working agreements: “done” is defined only as code merged, acceptance timing is undefined, and decision-making has no clear rule. The best next step is to facilitate a team session to refine and gain commitment to working agreements (including Definition of Done, acceptance/validation, meeting norms, and decision rules) to reduce rework and churn.

Working agreements are meant to create shared, explicit norms that enable consistent execution. In the exhibit, “done” excludes acceptance, the product owner’s availability is undefined, decisions can be reversed because there is no decision rule (e.g., who decides, quorum, and timebox), and optional standups for remote members increases information gaps.

The project manager should facilitate the team (including the product owner) to:

• Define a robust Definition of Done that includes validation/acceptance steps
• Establish decision rules (roles, quorum, timebox, and how to document)
• Set meeting norms that support a distributed team

This addresses the root cause rather than treating the symptoms with more reporting or schedule changes.

Question 14

Topic: Domain I: People

You are taking over as project manager for a hybrid product team with members in three time zones. The sponsor complains that “sprints keep slipping” because completed stories often return for rework after the review. Team members disagree on whether work is truly finished.

Before proposing new team ground rules, what should you clarify first?

• A. What additional budget is available to add testers immediately?
• B. What penalties does the sponsor want for missed sprint commitments?
• C. What is each developer’s utilization and velocity trend?
• D. What is the current Definition of Done and who agreed to it?

Best answer: D

Explanation: The most direct way to restore predictable delivery is to confirm whether the team has a shared, documented Definition of Done and who has agreed to it. If “done” means different things to different people, work will repeatedly fail acceptance or quality expectations and cycle back as rework. Clarifying the current Definition of Done is the right first step before changing norms or decision rules.

Working agreements create predictability by making expectations explicit (for example, meeting norms, decision rules, and a Definition of Done). In the scenario, the recurring problem is that work thought to be complete returns for rework after reviews, which strongly suggests misalignment on completion/acceptance and quality criteria.

The first clarification should establish the current baseline:

• Whether a Definition of Done exists
• Where it is documented and used (planning, reviews, acceptance)
• Who agreed to it (team, product owner, key stakeholders)

Once the current Definition of Done is understood, the team can update it (and related norms/decision rules) to reduce rework and improve delivery predictability. Resource or accountability discussions come after clarifying the shared standard for “done.”

Question 15

Topic: Domain I: People

Which artifact is primarily used to clarify team roles/responsibilities and working agreements to speed up onboarding and team formation?

• A. Team charter
• B. Requirements traceability matrix
• C. Procurement management plan
• D. Stakeholder engagement plan

Best answer: A

Explanation: A team charter is created to help the team quickly align on how they will work together. It typically captures roles and responsibilities, decision-making and communication norms, and other working agreements that support faster onboarding and higher early productivity.

The core concept is using a team charter to intentionally create role clarity and onboarding alignment. A team charter documents how the team will operate (for example, roles and responsibilities, ground rules, communication norms, and escalation/decision practices). By making expectations explicit early, the project manager reduces confusion and conflict, supports quicker integration of new members, and helps the team move faster from initial formation into productive delivery.

Question 16

Topic: Domain II: Process

A hybrid project is preparing a regulated product release. For the third time in a month, the integration test environment fails after a vendor library update, causing two days of rework and missed iteration goals. The compliance submission date cannot move, and there is no budget for additional staff.

What should the project manager do to best prevent recurrence while meeting the constraints?

• A. Escalate the issue to the sponsor to request additional funding and specialists
• B. Switch vendors immediately to eliminate future library update risks
• C. Facilitate root cause analysis and implement corrective and preventive actions
• D. Add extra end-of-cycle testing to catch integration failures earlier

Best answer: C

Explanation: Recurring environment failures indicate an underlying cause that must be identified and eliminated. Facilitating a cross-functional root cause analysis and then implementing corrective and preventive actions addresses both the immediate fix and the systemic prevention. This approach fits the constraints because it focuses on process and control changes rather than adding staff or moving the compliance date.

When the same issue repeats, treating symptoms (rework, extra testing, ad hoc fixes) consumes time and threatens delivery. The project manager should drive a structured root cause analysis with the right people (team, vendor, DevOps/QA, compliance as needed) to find the true source-such as versioning practices, change notification gaps, environment configuration drift, or missing acceptance criteria for vendor updates.

Then implement CAPA:

• Corrective action: stabilize the environment (e.g., pin versions, rollback criteria, verified configuration).
• Preventive action: add controls (e.g., vendor update intake checklist, automated compatibility smoke tests on a staging environment, change control/approval for dependency updates).
• Track the actions in the issue log, assign owners/dates, and verify effectiveness with monitoring over subsequent updates.

This reduces recurrence while staying within fixed deadline and staffing constraints.

Question 17

Topic: Domain I: People

You are assembling a team for a customer-facing digital service enhancement. Senior leadership wants “rapid value delivery,” but the sponsor has not confirmed whether requirements are expected to change significantly or how often releases must occur. Functional managers are asking whether you need more deep specialists (e.g., performance, security) or more cross-functional generalists.

What should you ask/verify first before deciding the mix of specialist and generalist skills?

• A. Whether the budget allows hiring additional full-time resources
• B. How stable the requirements are and the expected iteration/release cadence
• C. Which team members prefer specialist versus generalist roles
• D. Which tools and technologies the organization mandates for the solution

Best answer: B

Explanation: The right balance of specialists and generalists depends on how uncertain the work is and how frequently the team must deliver. High uncertainty and short cadences typically benefit from more cross-functional, T-shaped capabilities to reduce handoffs and quickly adapt. More stable scope and predictable cadence can justify staffing more deep specialists for efficiency and quality.

Team composition is a tailoring decision: match skills to the level of uncertainty and the delivery cadence. If requirements are likely to evolve and the team must release frequently, more cross-functional generalists (with sufficient breadth to swarm and reduce dependencies) improve flow and responsiveness. If requirements are stable and work can be planned in longer horizons, you can lean more on specialists to optimize quality and efficiency in specific domains.

A useful first clarification is:

• How much change/unknowns to expect in requirements and solution discovery
• How often increments must be produced and integrated (cadence)

Once those are clear, you can decide where deep expertise is essential versus where broad, flexible capacity will best support the delivery rhythm.

Question 18

Topic: Domain I: People

A project manager takes over an experienced, cross-functional agile team that has become disengaged after months of directive task assignments and escalations. The team says they want more autonomy and shared decision-making. The project manager decides to shift to a more collaborative (servant-leadership) approach and wants objective evidence that team engagement is improving.

Which metric or artifact best validates that this leadership change is working?

• A. Number of team members attending daily standups
• B. A newly signed team charter and working agreements
• C. Trend of results from an anonymous team engagement/health check survey
• D. Increase in sprint velocity over the last two iterations

Best answer: C

Explanation: Because the team is experienced and requesting autonomy, a collaborative/servant-leadership style is appropriate. The most valid way to confirm that this shift is improving engagement is to use direct measures of engagement from the team, gathered consistently over time. An anonymous engagement/health check trend provides evidence tied to the desired outcome rather than activity or performance side effects.

The core decision is matching leadership style to the team’s needs and then validating the intended outcome. An experienced agile team asking for autonomy is best led with a collaborative/servant-leadership approach that empowers shared ownership and decision-making. To validate whether that leadership change is effective, use evidence that directly measures engagement (sentiment, safety, motivation) and can be trended.

An anonymous team engagement/health check survey provides:

• Direct feedback from the people affected
• A repeatable measure to show improvement or decline over time
• Signal on engagement, not just compliance or output

By contrast, activity counts and delivery metrics can change for reasons unrelated to engagement, so they are weaker validation for a leadership-style change.

Question 19

Topic: Domain II: Process

While integrating the subsidiary plans for a predictive infrastructure project, the sponsor requests a new mandatory safety-training deliverable with no additional budget. To keep planning on schedule, the project manager immediately updates the scope baseline and tells the team they will “analyze schedule and cost impacts later,” without collecting updated estimates, resource availability, or critical-path data.

What is the most likely near-term impact of this decision?

• A. The procurement contract is terminated due to nonperformance
• B. Baselines and subsidiary plans become misaligned, delaying plan approval
• C. The customer rejects the final deliverable during project acceptance
• D. Regulatory penalties are incurred during operations after project closure

Best answer: B

Explanation: Integrated planning depends on using current data (estimates, resource availability, dependencies) to align scope, schedule, cost, and other subsidiary plans. Adding scope without analyzing impacts typically creates internal conflicts in the project management plan and prevents finalizing realistic baselines. The immediate consequence is rework and delays in getting the integrated plan approved and communicated.

When integrating project planning activities, the project manager uses data to ensure the scope change is reflected consistently across the schedule, cost, resource, risk, and communications components of the project management plan. If scope is updated without collecting and analyzing updated estimates, capacity, and dependency/critical-path information, the plan will quickly show contradictions (for example, new work with no time or cost allowance). In the near term, those inconsistencies surface during baseline review/approval and coordination with functional managers and stakeholders, forcing replanning and delaying commitment to a credible integrated baseline. The other impacts are plausible outcomes of poor planning, but they are longer-term and not the most immediate consequence in this situation.

Question 20

Topic: Domain II: Process

You are managing a project that depends on shared operational maintenance windows and deliverables from two other projects. You need a schedule artifact that consolidates multiple schedules and shows cross-project dependencies so the work can be coordinated and tracked at an integrated level.

What is this artifact called?

• A. Release roadmap
• B. Integrated master schedule (IMS)
• C. Project schedule network diagram
• D. Milestone chart

Best answer: B

Explanation: An integrated master schedule combines schedules from multiple projects (and often key operational activities) into one coordinated view. It explicitly includes interdependencies, making it suitable for coordinating shared constraints such as maintenance windows and external deliverables.

The key concept is using the right schedule artifact to manage dependencies beyond a single project. An integrated master schedule (IMS) is a consolidated schedule that brings together multiple related project schedules (and relevant operational activities when needed) and highlights cross-project interfaces and dependencies. This enables coordinated planning, sequencing, and tracking when work must align with other projects’ deliverables or operational constraints like outage windows.

By contrast, single-project schedule views (like a network diagram or milestone chart) help plan and communicate within one project but do not inherently integrate multiple projects’ timelines and dependencies into a single control view.

Question 21

Topic: Domain I: People

A distributed scrum team is missing quality targets, and tension is growing in daily standups. As the project manager, you review the issue log excerpt below.

Issue ID: ISS-22
Owner: Dev lead (Ravi)
Impact: 3 of last 4 stories returned from QA
Detail: Rework due to missing acceptance criteria checks
Observation: Ravi interrupts peers in standup when defects discussed
Constraint: Team is remote; next sprint planning is in 2 days

What is the best feedback approach to address this situation?

• A. Hold a private 1:1, use specific examples, and coach improvements
• B. Email the issue log to Ravi and copy functional management
• C. Address Ravi’s behavior in the next daily standup
• D. Wait for the formal performance review cycle to give feedback

Best answer: A

Explanation: The exhibit shows both a performance gap (rework) and a team-dynamics problem (interruptions), with an imminent planning event. The best approach is timely, private, and specific feedback that focuses on observable behavior and impact, then shifts to coaching and agreement on next steps to support team performance.

Effective feedback for supporting team performance should be timely, specific, and focused on observable behavior and its impact, delivered in a way that preserves psychological safety. The issue log provides concrete examples (stories returned from QA, interruptions during standup) and a near-term constraint (planning in 2 days), so delaying action increases risk.

A practical approach is:

• Schedule a private 1:1 quickly.
• Describe facts and impact (rework, team tension) and invite Ravi’s perspective.
• Collaboratively agree on changes (e.g., Definition of Done/AC checks, communication norms) and follow-up.

Public or escalatory feedback can reduce trust and worsen team dynamics; the goal is corrective coaching that improves outcomes and collaboration before the next planning event.

Question 22

Topic: Domain I: People

Which term describes a team climate where members feel safe to speak up, ask for help, and admit mistakes without fear of embarrassment or punishment-supporting higher commitment and engagement?

• A. Psychological safety
• B. Team charter
• C. Mutual trust
• D. Avoidance conflict strategy

Best answer: A

Explanation: Psychological safety is the condition where people feel safe to voice concerns, share ideas, and acknowledge errors without negative interpersonal consequences. This enables the project manager to use influence and motivation effectively because team members remain engaged and willing to commit, rather than staying silent to protect themselves.

Psychological safety is a team-level climate in which individuals believe they can take interpersonal risks-such as challenging assumptions, raising issues early, or admitting mistakes-without fear of humiliation or retaliation. In that environment, motivation and influence techniques (recognition, coaching, collaborative problem-solving, and inviting dissenting views) work better because people participate honestly and commit to decisions they helped shape.

A practical indicator is that the team:

• Raises risks and impediments early
• Asks clarifying questions without hesitation
• Treats mistakes as learning opportunities

Related concepts like trust and team working agreements help, but they are not the term that specifically describes this “safe to speak up” climate.

Question 23

Topic: Domain II: Process

Which term describes planning the near-term schedule in detail while keeping future work at a higher level, then updating the schedule as more information becomes available (often used in hybrid or predictive projects with uncertainty)?

• A. Progressive elaboration
• B. Backlog refinement
• C. Schedule compression
• D. Rolling wave planning

Best answer: D

Explanation: Rolling wave planning is the technique of detailing the schedule for imminent work and keeping later work at a higher level until it is better understood. As uncertainty reduces, the schedule is updated with more detail, aligning planning effort to the project’s methodology and information maturity.

Rolling wave planning is a schedule planning technique used when the full set of activities cannot be planned at a detailed level early in the project. The team plans and baselines (or otherwise commits to) detailed activities for the near term, while representing future work more broadly (for example, as summary activities or planning packages). As the project progresses and uncertainty decreases, the team elaborates the future work into detailed activities and updates the schedule accordingly. This supports tailoring across methodologies: predictive projects use it to handle evolving detail, and hybrid approaches use it to plan detailed upcoming work while leaving later increments flexible. The key idea is staged detailing and ongoing schedule updates driven by improved information, not simply speeding up work.

Question 24

Topic: Domain II: Process

You are asked to recommend an approach for a new customer portal project before detailed planning begins.

Exhibit: Project intake summary (excerpt)

Constraints: fixed regulatory go-live date (9 months)
Requirements: expected to evolve based on user feedback
Deliverables: core compliance reporting + customer-facing features
Vendors: 2 integrations under fixed-price contracts
Stakeholders: product group available for biweekly reviews
Technical: new cloud platform; unknown performance risks

Based on the exhibit, what is the best recommendation?

• A. Use a fully agile approach and avoid phase gates until release readiness
• B. Use a fully predictive approach with detailed baselines before execution
• C. Adopt a hybrid approach with predictive governance and iterative delivery
• D. Delay selecting the approach until after all requirements are finalized

Best answer: C

Explanation: The exhibit shows mixed needs: a hard regulatory date, compliance deliverables, and fixed-price vendor integrations alongside evolving requirements and technical uncertainty. A hybrid approach lets the team maintain necessary governance and contractual control while delivering customer-facing value iteratively and incorporating feedback throughout the project.

Assessing project needs, complexity, and magnitude means matching uncertainty and change rate to an appropriate delivery approach while honoring constraints. Here, evolving requirements, frequent stakeholder feedback, and technical unknowns favor iterative discovery and incremental delivery. At the same time, a fixed regulatory go-live date, compliance reporting, and fixed-price vendor integrations typically require more upfront definition, clear interfaces, and governance checkpoints. A hybrid approach fits best by combining predictive practices for compliance and vendor work with agile/iterative practices for the customer-facing features.

Key takeaway: choose an approach that explicitly addresses both high-uncertainty work and high-control constraints rather than forcing a single-method extreme.

PMP current exam decision map

Use this map after the sample questions to connect individual items to people, process, business environment, predictive, agile, hybrid, risk, stakeholder, and value-delivery decisions these PM Mastery samples test.

    flowchart LR
	  S1["Project leadership scenario"] --> S2
	  S2["Identify approach role and constraint"] --> S3
	  S3["Assess people process and business impact"] --> S4
	  S4["Choose servant leadership or governance action"] --> S5
	  S5["Adapt plan backlog risk or stakeholder response"] --> S6
	  S6["Deliver value and capture lessons"]

Quick Cheat Sheet

Mini Glossary

• Predictive approach: Planning approach that defines scope and baselines early and manages changes formally.
• Agile mindset: Adaptive approach emphasizing value, feedback, collaboration, and continuous learning.
• Hybrid approach: Combines predictive and adaptive practices based on delivery context and risk.
• Stakeholder engagement: Identifying, analyzing, communicating with, and involving people affected by the work.
• Value delivery: Creating outcomes that matter to customers, users, sponsors, and the organization.

Need concept review first?

If you want concept-first reading before heavier simulator work, use the companion PMP Study Guide on PMExams.com. Then return here for timed mocks, topic drills, explanations, and the full PM Mastery practice route.

Focused sample questions

Use these child pages when you want focused PM Mastery practice before returning to mixed sets and timed mocks.

• Free PMP Full-Length Practice Exam
• PMP: People
• PMP: Process
• PMP: Business Environment

In this section

• PMP: People
  Try 10 focused PMP questions on People, with answers and explanations, then continue with PM Mastery.
• PMP: Process
  Try 10 focused PMP questions on Process, with answers and explanations, then continue with PM Mastery.
• PMP: Business Environment
  Try 10 focused PMP questions on Business Environment, with answers and explanations, then continue with PM Mastery.
• Free PMP Full-Length Practice Exam: 180 Questions
  Try 180 free PMP questions across the exam domains, with answers and explanations, then continue in PM Mastery.