Project Management Professional (PMP) — All Questions

During daily standups, two developers repeatedly clash over the technical approach, and the tension is starting to slow the team. As a servant-leader project manager, what should you do first?

• a.Make the technical decision yourself so the team can move forward quickly
• b.Escalate the conflict to their functional managers for a performance discussion
• c.Assign the two developers to separate workstreams so they no longer interact
• d.Bring the two together privately to understand each perspective and help them reach a collaborative resolution✓

A servant-leader addresses conflict directly at the lowest level by facilitating open dialogue and helping the parties collaborate on a solution. Separating them or making the decision unilaterally avoids the root issue and undermines team ownership, while escalating prematurely skips the collaborative step that keeps the team empowered.

A newly formed agile team is unsure of its goals, members are deferring to the project manager for every decision, and productivity is low. Which action best helps the team mature?

• a.Wait passively until the team self-organizes on its own
• b.Reduce the length of iterations to force quicker decisions
• c.Establish a shared team charter and ground rules, then coach members toward self-organization✓
• d.Introduce individual performance bonuses to motivate faster delivery

An early-stage (forming) team needs clarity and structure; co-creating a team charter and ground rules builds shared purpose and gradually enables self-organization. Simply waiting provides no guidance, individual bonuses can undermine collaboration, and shortening iterations does not address the underlying lack of alignment.

A key team member will be unavailable for two sprints due to a family emergency, threatening a critical deliverable. What is the most effective leadership response?

• a.Remove the deliverable from scope without consulting stakeholders
• b.Work with the team to redistribute the work, support the member, and adjust the plan transparently with stakeholders✓
• c.Replace the member permanently to protect the schedule
• d.Insist the member complete the work remotely despite the emergency

Emotionally intelligent leadership balances empathy for the individual with responsibility to the project by supporting the member, reallocating work, and communicating impacts honestly. Forcing the member to work, silently cutting scope, or permanently replacing them damages trust and ignores stakeholder transparency.

Team velocity has dropped for three consecutive sprints, and the team seems disengaged during retrospectives. What should the project manager do to re-energize the team?

• a.Take over facilitation and dictate improvement actions
• b.Set a stretch goal and publicly compare each member's output
• c.Facilitate an open retrospective to surface impediments and let the team own the improvement actions✓
• d.Skip retrospectives to save time for delivery

Declining velocity and disengagement signal impediments the team must surface and address themselves; a psychologically safe retrospective lets them identify root causes and own improvements. Public comparison harms safety, dictating actions removes ownership, and skipping retrospectives eliminates the very mechanism for continuous improvement.

A stakeholder frequently bypasses the product owner and asks developers directly to add features mid-sprint. How should the project manager address this?

• a.Allow the requests since the stakeholder is important
• b.Instruct developers to refuse all communication with that stakeholder
• c.Add every requested feature to the current sprint to keep the stakeholder satisfied
• d.Coach the stakeholder on the intake process and reinforce the product owner's role in managing the backlog✓

Protecting the team from disruption while respecting stakeholders means coaching on the proper channel and reinforcing that the product owner prioritizes the backlog. Blindly accepting requests destabilizes the sprint, cutting off communication harms the relationship, and injecting work mid-sprint breaks the team's commitment.

A distributed team spanning several time zones reports feeling disconnected and misaligned on priorities. Which approach best improves team cohesion and shared understanding?

• a.Require everyone to attend meetings during one region's business hours
• b.Reduce communication to weekly written status reports only
• c.Rely solely on email to avoid scheduling difficulties
• d.Establish shared communication norms, rotate meeting times fairly, and use collaborative tools for transparency✓

Virtual teams thrive on agreed communication norms, equitable meeting scheduling, and transparent collaboration tools that keep everyone aligned. Forcing one region to always accommodate others breeds resentment, and reducing to email or weekly reports lowers the interaction needed for cohesion.

A team member consistently delivers high-quality work but wants to grow into a technical lead role. What is the best way for a servant-leader to support this?

• a.Deny the request to avoid disrupting current assignments
• b.Promise the promotion immediately regardless of readiness
• c.Provide stretch assignments, mentoring, and opportunities to lead technical discussions✓
• d.Ignore the request since delivery is already strong

Servant-leaders support individual growth by removing barriers and creating development opportunities such as stretch assignments and mentoring that build readiness. Denying or ignoring the request stifles motivation, while promising an unearned promotion sets false expectations and can harm the team.

Midway through a predictive project, a stakeholder submits a formal request to add a significant new feature. What should the project manager do first?

• a.Add the feature only if the team has spare capacity this week
• b.Evaluate the change's impact on scope, schedule, cost, and risk, then route it through the change control process✓
• c.Immediately implement the change to keep the stakeholder satisfied
• d.Reject the request because the baseline is already approved

Integrated change control requires assessing the full impact of a requested change and submitting it for approval before any action. Implementing immediately bypasses governance, outright rejection ignores potential value, and acting on spare capacity skips formal impact analysis and authorization.

An EVM report shows a project with CPI = 0.85 and SPI = 1.05. What does this indicate about project performance?

• a.The project is on budget and on schedule
• b.The project is over budget and behind schedule
• c.The project is under budget and behind schedule
• d.The project is over budget but ahead of schedule✓

CPI below 1.0 means the project is spending more than the value earned, so it is over budget, while SPI above 1.0 means more value has been earned than planned, so it is ahead of schedule. Recognizing that CPI addresses cost efficiency and SPI addresses schedule efficiency is essential to interpret combined performance correctly.

A hybrid project uses predictive planning for hardware and agile delivery for software. The software backlog keeps changing, disrupting hardware milestones. What is the best approach?

• a.Define clear integration points and coordinate cadences so software iterations align with hardware milestones✓
• b.Force the software team to adopt a fixed, unchangeable scope
• c.Abandon the predictive approach for the hardware component
• d.Let each team work independently with no synchronization

Hybrid delivery succeeds when teams establish integration points and synchronize cadences so evolving work aligns with fixed milestones. Freezing software scope defeats agility, converting hardware to pure agile may not fit its constraints, and removing synchronization guarantees misalignment.

During execution, the project manager notices that a risk previously logged as low probability now appears likely to occur. What should be done?

• a.Remove the risk from the register to avoid alarming stakeholders
• b.Reassess the risk, update the risk register, and implement the appropriate response strategy✓
• c.Immediately execute a fallback plan
• d.Ignore it until it actually occurs

Risk monitoring is continuous; when a risk's probability changes, the project manager reassesses it, updates the risk register, and triggers the planned response. Waiting until it occurs forfeits proactive control, jumping to a fallback skips analysis of the primary response, and deleting the risk hides critical information.

A project manager is planning procurement for specialized components with well-defined specifications and a stable market. Which contract type best transfers cost risk to the seller?

• a.Time-and-materials (T&M)
• b.Cost-plus-fixed-fee (CPFF)
• c.Cost-plus-incentive-fee (CPIF)
• d.Firm-fixed-price (FFP)✓

A firm-fixed-price contract sets a fixed total price for well-defined work, placing the cost risk on the seller since overruns are the seller's responsibility. Cost-reimbursable and T&M contracts leave more cost risk with the buyer and are better suited to uncertain or evolving scope.

An agile team consistently completes fewer story points than committed each sprint, eroding stakeholder trust. What should the project manager coach the team to do?

• a.Use empirical velocity to forecast commitments and refine backlog estimates during planning✓
• b.Extend every sprint until all committed work is done
• c.Stop measuring velocity to reduce pressure
• d.Commit to more points to push the team harder

Agile forecasting relies on empirical data; using actual historical velocity and refining estimates produces realistic, sustainable commitments that rebuild trust. Over-committing worsens the gap, dropping velocity removes a key feedback metric, and stretching sprint length breaks the fixed-cadence principle.

A project's schedule shows the critical path has zero float, and a non-critical activity has 6 days of float. An unexpected delay consumes 4 days of that activity's float. What is the schedule impact?

• a.The project end date is unaffected because float remains on that activity✓
• b.The project must be crashed to recover
• c.The project end date slips by 4 days
• d.The critical path immediately changes to that activity

Float is the amount of delay an activity can absorb without affecting the project finish date; consuming 4 of 6 days of float still leaves 2 days, so the end date is unaffected. Only when a delay exceeds available float does it affect the critical path or the project completion date.

Quality inspections reveal a recurring defect in a deliverable. The project manager wants to prevent recurrence rather than just fix the symptom. Which tool is most appropriate?

• a.A responsibility assignment matrix to reassign work
• b.A stakeholder register to log concerns
• c.A milestone chart to track completion
• d.A root-cause analysis such as a fishbone diagram to identify underlying causes✓

Preventing recurrence requires identifying underlying causes, and a cause-and-effect (fishbone) diagram or the 5 Whys systematically uncovers root causes. Milestone charts, RAMs, and stakeholder registers serve tracking and assignment purposes, not defect-cause analysis.

At the start of an iteration, the product owner reprioritizes the backlog so a high-value feature moves to the top. How should the team respond during iteration planning?

• a.Pull the reprioritized high-value items into the iteration based on capacity and definition of ready✓
• b.Complete the previous order first, then address the new priority next iteration
• c.Split the team so half works on old priorities and half on new
• d.Refuse the change because the backlog was already set

Agile embraces changing priorities between iterations; the team pulls the newly prioritized, ready items into the upcoming iteration according to its capacity. Refusing the change ignores value delivery, deferring high-value work delays benefits, and splitting the team fragments focus and reduces flow.

A project must comply with a new data-privacy regulation that takes effect before go-live. What is the project manager's best course of action?

• a.Proceed as planned and address compliance only if audited
• b.Delay the project indefinitely until all regulations stabilize
• c.Assess compliance requirements, incorporate them into the plan, and monitor for regulatory changes✓
• d.Assume the legal team will handle compliance without project involvement

Managing compliance means proactively identifying applicable requirements, integrating them into the project plan, and continuously monitoring for changes. Ignoring compliance risks penalties and rework, delegating blindly abdicates the PM's integration role, and indefinite delay forfeits business value.

During delivery, a shift in market conditions reduces the expected business value of the project's remaining scope. What should the project manager do?

• a.Raise the change with the sponsor and evaluate whether to re-prioritize or adjust scope to maximize value✓
• b.Cancel the project immediately without analysis
• c.Continue delivering the full original scope as approved
• d.Hide the information to avoid destabilizing the team

Projects exist to deliver business value, so a material change in value should be surfaced to the sponsor and used to reassess scope and priorities. Blindly delivering obsolete scope wastes resources, canceling without analysis is premature, and concealing information violates transparency and stewardship.

A project delivers an output, but the organization struggles to adopt the new process, so expected benefits are not realized. What was most likely missing?

• a.A more aggressive project schedule
• b.An organizational change management and benefits realization plan✓
• c.A detailed work breakdown structure
• d.A larger project budget

Benefits are realized only when the organization adopts the change, which requires organizational change management to prepare people and a benefits realization plan to track outcomes. A WBS, schedule, or budget govern delivery of outputs but do not ensure adoption or sustained benefits.

A project manager wants to ensure the project stays aligned with organizational strategy throughout its life cycle. Which practice best supports this?

• a.Freeze the business case at initiation and never revisit it
• b.Regularly review the business case and project objectives against evolving strategic goals✓
• c.Focus only on meeting the triple constraint
• d.Report solely on task completion percentages

Strategic alignment is maintained by continually revisiting the business case and objectives to confirm they still support organizational goals as conditions change. A frozen business case, a pure constraint focus, or task-only reporting can leave a project delivering outputs that no longer serve the strategy.

A new competing priority causes leadership to consider reallocating resources away from your project. How can you best protect the project's standing?

• a.Demonstrate the project's business value and benefits with data, and engage leadership on strategic impact✓
• b.Immediately reduce scope without leadership discussion
• c.Compete with the other project team for resources aggressively
• d.Withhold status information so leadership cannot compare projects

When priorities compete, articulating the project's quantified business value and strategic contribution helps leadership make informed portfolio decisions. Withholding information erodes trust, unilaterally cutting scope is premature, and aggressive competition damages relationships and organizational agility.

An organization is transitioning toward greater business agility. As a project manager, how can you best support organizational change?

• a.Wait for a formal mandate before adjusting any practices
• b.Adopt every agile framework simultaneously to accelerate the transition
• c.Insist teams retain their existing predictive processes unchanged
• d.Model agile mindset behaviors, share knowledge, and help teams adapt practices to their context✓

Supporting organizational agility means role-modeling an agile mindset, transferring knowledge, and helping teams tailor practices to fit their context. Clinging to old processes resists the change, waiting for a mandate is passive, and forcing all frameworks at once creates confusion rather than sustainable adaptation.

A project charter has just been approved, but stakeholders keep debating what the project will and will not deliver. What should the project manager do next to establish a shared understanding of the work?

• a.Ask the sponsor to make all scope decisions unilaterally
• b.Begin executing the highest-value work immediately to build momentum
• c.Freeze scope discussions until the schedule baseline is set
• d.Collect requirements from stakeholders and develop a scope statement and WBS✓

Defining scope is the foundation for planning: the PM collects requirements, writes a clear scope statement, and decomposes the work into a WBS so everyone shares the same boundaries. Executing before scope is defined, deferring scope, or centralizing all decisions ignores the requirements-gathering step that prevents later rework.

During execution of a predictive project, a team member completes work that was never requested, believing it would add value. The extra work delayed an approved deliverable. What does this situation represent?

• a.A legitimate change that requires no documentation
• b.Gold plating, which should be prevented by controlling scope to the baseline✓
• c.Scope creep initiated by the customer that must be accepted
• d.Progressive elaboration of the requirements

Adding unrequested extras that were not authorized is gold plating, and controlling scope means delivering exactly what was approved, no more and no less. Scope creep comes from uncontrolled stakeholder changes, progressive elaboration refines defined work, and any real change must go through change control.

A project has BAC = $200,000. At the status date, work is 40% complete, PV was planned at $100,000, and AC is $90,000. What is the cost variance (CV)?

• a.-$20,000
• b.$20,000
• c.-$10,000✓
• d.$10,000

EV = 40% of BAC = 0.40 x $200,000 = $80,000, and CV = EV - AC = $80,000 - $90,000 = -$10,000. A negative CV means the project has spent more than the value earned and is over budget; PV is used for schedule variance, not cost variance.

Using the same data (EV = $80,000, PV = $100,000), what is the schedule performance index (SPI), and what does it mean?

• a.1.25, meaning the project is ahead of schedule
• b.0.89, meaning the project is over budget
• c.1.11, meaning the project is on schedule
• d.0.80, meaning the project is behind schedule✓

SPI = EV / PV = $80,000 / $100,000 = 0.80, and an SPI below 1.0 means less value has been earned than planned, so the project is behind schedule. Cost efficiency is measured by CPI (EV/AC), not SPI.

A project has BAC = $500,000, EV = $200,000, and AC = $250,000. Assuming current cost performance continues, what is the estimate at completion (EAC)?

• a.$450,000
• b.$500,000
• c.$550,000
• d.$625,000✓

CPI = EV/AC = 200,000/250,000 = 0.80, and when current performance is expected to continue, EAC = BAC/CPI = 500,000/0.80 = $625,000. This formula projects the final cost by extrapolating the cost efficiency observed so far.

A network diagram has two paths to completion: Path A (Start-B-D-End) totals 15 days and Path B (Start-C-E-End) totals 12 days. What is the total float of activity C on Path B?

• a.12 days
• b.15 days
• c.3 days✓
• d.0 days

The critical path is the longest path at 15 days, so Path B has 15 - 12 = 3 days of total float shared across its activities. Activity C can slip up to 3 days without delaying the project; only critical path activities have zero float.

The sponsor wants the project finished two weeks earlier and has approved additional budget. The PM decides to add resources to critical path activities. Which schedule compression technique is this?

• a.Resource leveling
• b.Fast tracking
• c.Crashing✓
• d.Rolling wave planning

Crashing shortens the schedule by adding resources to critical path activities, typically increasing cost. Fast tracking overlaps activities that were planned in sequence, resource leveling adjusts for resource constraints, and rolling wave is a progressive planning technique.

To recover schedule without extra cost, a PM decides to begin design of module two before design of module one is fully complete, accepting some rework risk. Which technique is being used?

• a.Monte Carlo simulation
• b.Fast tracking✓
• c.Crashing
• d.Critical chain buffering

Fast tracking performs activities in parallel that were originally scheduled in sequence, compressing the schedule at the cost of increased risk and potential rework. Crashing adds resources and cost, while the other options are analysis or buffering techniques, not compression by overlap.

During sprint planning, the team and product owner disagree on how much work fits in the upcoming iteration. What is the best basis for the team's commitment?

• a.The team's recent average velocity and current capacity✓
• b.The maximum output the team achieved in its single best sprint
• c.A fixed number of story points mandated by management
• d.The product owner's desired scope for the release

Sustainable, realistic commitments are based on empirical average velocity and the team's actual capacity for the iteration. Using a single best sprint, a management mandate, or the product owner's wish list ignores real capacity and undermines predictability and trust.

A stakeholder requests a change during execution. The change control board has not yet met. A team member asks if they can start the change now to save time. What should the PM say?

• a.No; the change must be evaluated and approved through integrated change control before work begins✓
• b.No; because every change request should simply be rejected outright to protect the approved baseline from any disruption
• c.Yes, because responding quickly to stakeholders is always the priority
• d.Yes, as long as the change is small enough to fit in the current period

Integrated change control requires that a requested change be assessed for impact and formally approved before any implementation. Starting early bypasses governance, blanket rejection ignores value, and change size does not exempt a request from the approval process.

A project is halfway through, and the customer indicates requirements are likely to keep evolving as they learn from early deliverables. Which delivery approach is most appropriate for the remaining work?

• a.A fully predictive approach with a locked scope baseline
• b.An adaptive (agile) approach delivering in short increments with feedback✓
• c.No planning at all, letting the team decide day to day
• d.A single big-bang delivery at the very end

High requirement uncertainty and the need to learn from early results favor an adaptive approach that delivers increments and incorporates feedback each cycle. A locked predictive baseline resists change, a single big-bang delivery defers all learning, and no planning provides no direction.

A newly identified risk could severely impact the project, but its response would be expensive. The PM decides to purchase insurance to shift the financial consequence to a third party. Which risk response strategy is this?

• a.Accept
• b.Avoid
• c.Transfer✓
• d.Mitigate

Transferring shifts the impact and ownership of a threat to a third party, commonly through insurance, warranties, or contracts. Mitigation reduces probability or impact directly, avoidance eliminates the threat, and acceptance takes no proactive action.

A risk with high probability and high impact is identified early. The PM changes the project plan to eliminate the condition that gives rise to the risk entirely. Which response strategy is this?

• a.Transfer
• b.Accept
• c.Avoid✓
• d.Escalate

Avoidance eliminates a threat by removing its cause, for example by changing scope, approach, or plan so the risk can no longer occur. Transfer shifts impact to another party, acceptance takes no action, and escalation moves a risk outside the project's authority.

During procurement, the buyer's requirements are not fully defined and the level of effort is uncertain. Which contract type is generally most appropriate?

• a.Fixed-price with economic price adjustment
• b.Firm-fixed-price
• c.Cost-reimbursable or time-and-materials✓
• d.Fixed-price-incentive-fee with a hard ceiling

When scope is uncertain and effort is hard to estimate, cost-reimbursable or T&M contracts fit because they do not require a fully defined deliverable up front. Fixed-price variants require well-defined scope and place cost risk on the seller, which is unsuitable when requirements are unclear.

A key stakeholder has high power and high interest but is currently resistant to the project. What is the most appropriate engagement approach?

• a.Avoid contact to prevent conflict
• b.Manage them closely with proactive, tailored engagement to move them toward support✓
• c.Keep them informed with periodic updates only, treating a resistant high-power stakeholder as a lower priority
• d.Monitor them with minimal effort

High-power, high-interest stakeholders should be managed closely, and a resistant one needs proactive, tailored engagement to shift them toward support. Minimal monitoring or merely keeping them informed underuses engagement, and avoiding contact allows resistance to grow unchecked.

A project has 6 stakeholders now, and 3 more will join next month. Using the communication channels formula, how many additional channels are created when the team grows from 6 to 9?

• a.15
• b.21✓
• c.36
• d.3

Channels = n(n-1)/2, so 6 people give 15 channels and 9 people give 36 channels; the increase is 36 - 15 = 21 additional channels. The formula shows communication complexity grows faster than headcount, which is why larger teams need deliberate communication planning.

A defect is discovered during quality control inspection late in the project. The PM wants to understand where in the process the defect was introduced and stop it from recurring. Which tool best supports this?

• a.A histogram of measurement values
• b.A cause-and-effect (fishbone) diagram to trace root causes✓
• c.A control chart showing whether the process is stable
• d.A Pareto chart ranking defect frequencies

To trace the underlying cause of a defect and prevent recurrence, a cause-and-effect (Ishikawa/fishbone) diagram systematically explores potential root causes. Control charts show stability, Pareto charts rank frequency, and histograms show distribution, but none isolate root cause the way a fishbone does.

The project manager wants to distinguish between quality assurance and quality control. Which statement correctly describes quality assurance?

• a.It focuses on improving and auditing processes to build quality in✓
• b.It inspects deliverables to detect defects after they occur
• c.It is performed only at the end of the project during closeout
• d.It measures whether individual outputs meet specifications

Quality assurance is process-focused and proactive, auditing and improving processes so quality is built into deliverables. Quality control is product-focused and inspects specific deliverables to detect defects, which is a reactive, output-level activity.