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

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.Establish a shared team charter and ground rules, then coach members toward self-organization✓
• c.Introduce individual performance bonuses to motivate faster delivery
• d.Reduce the length of iterations to force quicker decisions

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

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

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.Coach the stakeholder on the intake process and reinforce the product owner's role in managing the backlog✓
• c.Instruct developers to refuse all communication with that stakeholder
• d.Add every requested feature to the current sprint to keep the stakeholder satisfied

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.Rely solely on email to avoid scheduling difficulties
• c.Establish shared communication norms, rotate meeting times fairly, and use collaborative tools for transparency✓
• d.Reduce communication to weekly written status reports only

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.Provide stretch assignments, mentoring, and opportunities to lead technical discussions✓
• b.Deny the request to avoid disrupting current assignments
• c.Promise the promotion immediately regardless of readiness
• 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.Immediately implement the change to keep the stakeholder satisfied
• b.Evaluate the change's impact on scope, schedule, cost, and risk, then route it through the change control process✓
• c.Reject the request because the baseline is already approved
• d.Add the feature only if the team has spare capacity this week

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 under budget and behind schedule
• b.The project is on budget and on schedule
• c.The project is over 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.Ignore it until it actually occurs
• b.Immediately execute a fallback plan
• c.Reassess the risk, update the risk register, and implement the appropriate response strategy✓
• d.Remove the risk from the register to avoid alarming stakeholders

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.Cost-plus-fixed-fee (CPFF)
• b.Firm-fixed-price (FFP)✓
• c.Time-and-materials (T&M)
• d.Cost-plus-incentive-fee (CPIF)

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.Commit to more points to push the team harder
• c.Stop measuring velocity to reduce pressure
• d.Extend every sprint until all committed work is done

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 slips by 4 days
• b.The critical path immediately changes to that activity
• c.The project must be crashed to recover
• d.The project end date is unaffected because float remains on 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 milestone chart to track completion
• b.A responsibility assignment matrix to reassign work
• c.A root-cause analysis such as a fishbone diagram to identify underlying causes✓
• d.A stakeholder register to log concerns

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

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

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.Continue delivering the full original scope as approved
• b.Cancel the project immediately without analysis
• c.Raise the change with the sponsor and evaluate whether to re-prioritize or adjust scope to maximize value✓
• 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 detailed work breakdown structure
• b.An organizational change management and benefits realization plan✓
• c.A more aggressive project schedule
• 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.Focus only on meeting the triple constraint
• c.Report solely on task completion percentages
• d.Regularly review the business case and project objectives against evolving strategic goals✓

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.Withhold status information so leadership cannot compare projects
• c.Immediately reduce scope without leadership discussion
• d.Compete with the other project team for resources aggressively

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

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.