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.

A project sponsor asks you to describe your leadership style for a newly chartered cross-functional team. Which description best reflects a servant-leadership approach?

• a.Set aggressive stretch targets and evaluate members mainly by comparing their individual output against each other
• b.Direct each task in detail and personally approve every decision before the team is allowed to proceed
• c.Focus on removing impediments, developing team members, and enabling the team to self-organize around shared goals✓
• d.Delegate all responsibility to the team and stay uninvolved until the final deliverable is due for review

Servant leadership centers on serving the team: clearing obstacles, growing people, and creating the conditions for self-organization toward a shared purpose. Command-and-control direction, output-ranking, and total disengagement all conflict with the servant-leader's enabling role.

As you begin leading a team, several members from different functions have never worked together. What should you prioritize first to lead them effectively?

• a.Begin tracking each person's individual productivity metrics from the very first day of the project
• b.Assign detailed individual tasks to each member before discussing the overall goals of the effort
• c.Rank the members by seniority and experience to establish a clear internal chain of command
• d.Establish a shared vision of the project's purpose and how each person contributes to it✓

Leading a team starts with a shared vision so members understand the common purpose and their contribution; alignment precedes task assignment. Establishing hierarchy, jumping to task lists, or measuring output first fails to build the shared direction a new team needs.

A high-performing team has matured and now makes most decisions on its own. How should the project manager's leadership style adapt?

• a.Introduce stricter approval gates on their decisions to preserve consistency across the deliverables
• b.Reduce nearly all communication with the team so that you do not accidentally interfere with their flow
• c.Shift toward delegating and supporting, intervening mainly to remove obstacles✓
• d.Return to closely directing individual tasks in order to maintain firm control over the outcomes

Situational leadership calls for adapting style to team maturity; a capable, motivated team benefits from a delegating and supporting style. Reverting to directing, adding approval gates, or going silent would undermine the autonomy the team has earned.

During a project kickoff, the team looks to you to define how decisions will be made. What is the most effective leadership action?

• a.Tell the team to simply decide everything themselves without offering any structure or guidance on boundaries
• b.Clarify which decisions the team owns, which you own, and which require escalation✓
• c.Postpone establishing any decision-making rules until an actual conflict forces the issue into the open
• d.Reserve all significant decisions for yourself so that you can personally ensure their quality and consistency

Effective leaders make decision authority explicit so the team knows what it can decide and when to escalate, which builds both autonomy and accountability. Centralizing all decisions, abdicating entirely, or leaving authority undefined creates confusion and slows the team.

You are leading a team where a few vocal members dominate discussions while quieter members disengage. What should you do to lead more inclusively?

• a.Let the most confident and vocal members drive the discussions since they clearly contribute the most ideas
• b.Reduce the frequency of team meetings so that fewer differing opinions need to be managed at once
• c.Facilitate participation techniques that give every member a voice, such as round-robin or written input✓
• d.Require the quieter members to publicly justify why they are choosing not to speak up in the meetings

Inclusive leadership deliberately draws out all perspectives using facilitation techniques that balance participation and surface diverse input. Deferring to dominant voices, pressuring quiet members, or cutting meetings ignores the value of full team engagement.

A team member challenges your decision in front of the whole team during a planning session. What is the best leadership response?

• a.Ignore the challenge entirely and continue moving through the planned agenda as if nothing was said
• b.Acknowledge the concern respectfully and invite the member to explain their reasoning so it can be discussed✓
• c.Assert your positional authority and instruct the member not to question your decisions in front of others
• d.Immediately reverse your decision on the spot to avoid appearing rigid or defensive to the team

Psychologically safe leadership welcomes dissent as input; acknowledging the concern and exploring the reasoning models openness and improves decisions. Shutting down the challenge harms safety, ignoring it dismisses potential insight, and reflexively reversing course signals you lack conviction.

Leadership has given you a team but limited formal authority over its members, who report to functional managers. How can you best lead them?

• a.Avoid asking anything of the members that you cannot formally compel them to do through your position
• b.Demand that the functional managers formally grant you full authority over their people before you begin
• c.Escalate to senior leadership every single time a team member does not immediately comply with a request
• d.Build influence through trust, clear goals, and consistent support rather than relying on positional power✓

In a matrix or weak-authority setting, leaders rely on influence, relationships, and trust rather than positional power to mobilize the team. Demanding authority, escalating constantly, or avoiding requests all fail to build the interpersonal influence such environments require.

You notice that team members are hesitant to raise bad news, fearing blame. What leadership behavior best changes this over time?

• a.Handle all significant issues yourself so that individual members never have to be the bearer of bad news
• b.Consistently respond to problems with curiosity and support instead of blame, and thank people for surfacing issues✓
• c.Ask members to report only fully confirmed problems rather than early concerns to reduce false alarms
• d.Institute clear penalties for reporting problems late in order to enforce more disciplined transparency

A blameless culture is built by consistently rewarding transparency and treating problems as improvement opportunities, which makes people safe to speak up. Penalties, raising the reporting threshold, or absorbing all issues yourself reinforce fear and reduce the information you receive.

A team that recently formed is experiencing frequent disagreements about roles and approach, and progress feels chaotic. Which stage of team development is this, and what should you do?

• a.Forming; simply wait a while longer because the members are still politely getting acquainted with each other
• b.Storming; coach the team through conflict toward agreed norms and clarified roles✓
• c.Performing; step back entirely and let the self-sufficient team continue without any further involvement
• d.Adjourning; begin releasing members and closing out the team since its useful work is essentially over

Frequent friction over roles and approach is classic storming; the leader helps the team work through conflict and establish norms. Misreading it as forming, performing, or adjourning would lead to inaction or premature disbandment instead of the active coaching storming requires.

Your team has developed strong norms and is delivering consistently with little intervention. To sustain high performance, what should you focus on?

• a.Reassign members frequently between tasks and teams in order to spread their expertise more widely
• b.Increase your oversight and check-ins to make sure the team does not become complacent about its success
• c.Reduce the team's feedback loops and retrospectives now that it is clearly performing well on its own
• d.Protect the team from disruption, keep removing impediments, and support continued growth✓

A performing team is sustained by shielding it from churn, clearing obstacles, and continuing development, preserving the stability that enables flow. Frequent reassignment, added oversight, or fewer feedback loops disrupt the very conditions that produce high performance.

You want to measure whether your team is improving over time. Which approach best supports team development?

• a.Rely on a single detailed annual performance review for each member to assess how they are progressing
• b.Track team-level metrics and hold regular retrospectives to identify and act on improvements✓
• c.Measure only the final delivery dates of milestones and nothing about the work in between them
• d.Rank individuals against one another on a public leaderboard to drive competitive improvement

Team development is driven by team-level measures and frequent retrospectives that turn learning into action. Individual ranking pits members against each other, annual reviews are too infrequent to steer improvement, and tracking only end dates provides no in-flight feedback.

A newly assigned member has strong skills but is unfamiliar with the team's processes and is slowing the team down. What is the best development action?

• a.Exclude the member from the important work until they manage to learn the processes entirely on their own
• b.Assign the member only trivial low-impact tasks indefinitely so their unfamiliarity cannot disrupt delivery
• c.Pair the member with an experienced teammate and provide onboarding to build shared context quickly✓
• d.Report the slowdown the member is causing to their functional manager for a performance discussion

Onboarding plus pairing accelerates a capable newcomer's integration by transferring team context and norms. Isolating the member, restricting them to trivial work, or escalating to a manager wastes their skills and neglects the leader's development responsibility.

Your team keeps repeating the same mistakes across iterations even though retrospectives generate ideas. What is the most likely gap and best fix?

• a.The team is holding too many retrospectives and should stop running them in order to save delivery time
• b.Only the project manager should decide on the improvement actions rather than involving the whole team
• c.Improvement actions are not being assigned owners and tracked; make them specific, owned, and reviewed each cycle✓
• d.The team should quietly hide its recurring mistakes so that morale is not damaged by dwelling on them

Retrospectives create value only when actions are concrete, owned, and followed up; without accountability, insights evaporate and mistakes recur. Canceling retrospectives, concealing errors, or centralizing improvements would remove the team's own continuous-improvement loop.

You want to build the team's collective capability so it depends less on any single expert. Which practice best achieves this?

• a.Concentrate each critical skill in its single strongest expert so that quality on that skill stays highest
• b.Encourage knowledge sharing and cross-training so critical skills are held by more than one person✓
• c.Document as little as possible so that your key experts remain indispensable and unlikely to leave
• d.Prohibit members from working outside their assigned specialty to keep everyone focused and efficient

Reducing key-person risk and strengthening the team comes from cross-training and shared knowledge so expertise is distributed. Concentrating skills, enforcing rigid specialization, or withholding documentation increases fragility and single points of failure.

A team member's performance has recently declined, though they were previously reliable. What should the project manager do first?

• a.Quietly reassign their most critical tasks to other members without discussing the change with them
• b.Meet privately to understand what changed and identify what support they may need✓
• c.Formally document the underperformance and issue a warning about the consequences of not improving
• d.Raise the performance decline in a team meeting in the hope that the visibility prompts improvement

A sudden performance drop in a previously strong member usually has an underlying cause; a private, supportive conversation surfaces it and identifies needed help. Jumping to warnings, silently reassigning work, or public callouts damage trust and skip understanding the root cause.

To develop future leaders on your team, which approach is most effective?

• a.Delegate meaningful responsibilities with support and coaching, and give increasing autonomy as members grow✓
• b.Assign leadership duties only to the single most senior member regardless of their actual aptitude for it
• c.Keep all of the leadership tasks to yourself until team members are formally promoted into leader roles
• d.Rotate leadership titles among members frequently without actually changing their real responsibilities

Leaders develop by taking on real responsibility with coaching and growing autonomy, which builds capability through experience. Hoarding leadership work, defaulting to seniority, or granting titles without substance fails to develop genuine leadership skills.

Two team members are in a heated conflict over a design choice, and both have valid technical points that could improve the product. Which Thomas-Kilmann mode should the project manager encourage?

• a.Accommodating, so that one party simply yields to the other in order to keep the peace on the team
• b.Collaborating, to work through both perspectives toward a solution that integrates the best of each✓
• c.Avoiding, in the hope that the disagreement quietly resolves itself over time without intervention
• d.Competing, so that the more forceful personality prevails quickly and the team can move on

When both parties have important, valid input and time allows, collaborating (win-win) integrates their ideas into a superior solution. Avoiding leaves value unrealized, competing forces a lose outcome, and accommodating discards one party's legitimate contribution.

A minor disagreement erupts over the wording of a status report just before a critical deadline, threatening to consume time the team cannot spare. Which conflict-handling mode is most appropriate here?

• a.Accommodating or smoothing on this low-stakes issue so the team can focus on the deadline✓
• b.Collaborating through a lengthy facilitated workshop in order to reach a full consensus on the wording
• c.Escalating the wording dispute up to the project sponsor to make the final call on the language
• d.Competing to impose your own preferred wording on the report immediately regardless of objections

For a trivial issue under time pressure, accommodating (smoothing) preserves the relationship and lets the team focus on what matters. A full collaborate workshop is disproportionate, competing damages relationships over a minor point, and escalation wastes leadership attention on something inconsequential.

A conflict has arisen where you must enforce a mandatory safety regulation that a team member disputes. Which conflict mode fits best?

• a.Compromising by partially relaxing the safety requirement so the member feels their view was honored
• b.Accommodating the member's preference in order to preserve harmony and goodwill on the team
• c.Forcing (competing), because non-negotiable safety and compliance requirements must be upheld✓
• d.Avoiding the issue for now to keep the member satisfied and revisit the safety point another time

When the matter is non-negotiable, such as a legal or safety requirement, forcing is appropriate because there is no room to yield. Compromising or accommodating on mandatory safety is unacceptable, and avoiding leaves a critical requirement unmet.

Two teams disagree over shared resource allocation, both have partially valid needs, and a fully integrated solution is not feasible in the available time. Which approach is most practical?

• a.Forcing your own preferred allocation onto both teams so the matter is settled without further debate
• b.Compromising so each team gives up something and gains something to reach a workable middle ground✓
• c.Avoiding the allocation decision until the resource conflict escalates into a more serious problem
• d.Accommodating whichever team complains the loudest so that the most vocal group stops pushing back

Compromising (give-and-take) is a pragmatic mode when a full collaborative solution is not feasible and a reasonable middle ground satisfies both parties enough. Avoiding delays a needed decision, forcing breeds resentment, and rewarding the loudest team is arbitrary and unfair.

When conflict surfaces in your team, what is generally the healthiest way for a project manager to view it?

• a.As a natural part of teamwork that, managed constructively, can lead to better solutions✓
• b.As a clear sign of a dysfunctional team that must be prevented from occurring at all costs
• c.As a matter best left entirely to HR that the project manager should deliberately stay out of
• d.As evidence that the wrong people were assigned to the team and some of them should be replaced

Constructively managed conflict can surface diverse viewpoints and produce better outcomes, so it is a normal and potentially healthy part of teamwork. Treating all conflict as dysfunction, an HR-only matter, or a staffing error discourages the healthy debate teams need.

Two team members had a disagreement that you helped them resolve last week, but tension between them lingers. What should you do next?

• a.Separate the two members permanently onto different workstreams to prevent any further friction
• b.Ask the rest of the team to weigh in and take sides in order to settle the lingering tension
• c.Consider the matter fully closed since a resolution was already reached during last week's discussion
• d.Follow up with both to confirm the resolution is holding and address any residual issues✓

Conflict resolution is not complete until it holds; following up confirms the agreement is working and catches lingering tension early. Assuming closure ignores the residual friction, permanent separation is an overreaction, and involving the team in sides makes it worse.

You realize that a recurring conflict between two members stems from unclear ownership of overlapping responsibilities. What is the best long-term fix?

• a.Ask the two members to simply try harder to get along with each other despite the overlap
• b.Clarify roles and responsibilities so ownership boundaries are explicit and agreed✓
• c.Let the members renegotiate ownership from scratch before the start of every new task
• d.Rotate the overlapping responsibilities randomly between them each week to keep things fair

When conflict is rooted in ambiguous responsibilities, clarifying roles (for example via a responsibility assignment matrix) removes the structural cause. Telling them to get along ignores the real issue, random rotation adds instability, and renegotiating each task perpetuates the ambiguity.

During a conflict, one party is becoming increasingly emotional and raising their voice. What should the project manager do first?

• a.End the working relationship between the parties by reassigning one of them to a different team
• b.Demand that the person immediately control themselves so that the discussion can continue right away
• c.Match their rising intensity to show that you are taking the issue every bit as seriously as they are
• d.De-escalate by acknowledging emotions and, if needed, pausing the discussion until people can engage calmly✓

High emotion blocks problem-solving, so acknowledging feelings and pausing restores the calm needed for productive dialogue. Demanding composure, escalating your own intensity, or reassigning someone skips the emotional de-escalation that must come first.

Team members constantly ask you to approve routine technical decisions they are fully capable of making, creating a bottleneck. What should you do?

• a.Tell the team to stop asking and just figure the decisions out with no boundaries or guidance at all
• b.Add a formal approval request form in order to slow down the flood of approval requests coming to you
• c.Empower the team to make those decisions within clear boundaries and support their choices✓
• d.Continue approving each routine decision yourself in order to maintain consistency across the work

Empowerment means pushing decision authority to the people doing the work within agreed boundaries, which removes bottlenecks and builds ownership. Approving everything sustains the bottleneck, abruptly refusing without guidance leaves them unsupported, and adding forms increases bureaucracy.

You want to empower your team to own its outcomes. Which action most genuinely increases empowerment?

• a.Announce ambitious goals to the team and then assign them the detailed methods for achieving each one
• b.Involve the team in setting its goals and give it authority over how the work is done✓
• c.Let the team choose only trivial matters for itself while you retain control over all substantive ones
• d.Ask the team for its input regularly but then consistently override it with your own final decision

Real empowerment gives the team a voice in goals and authority over the means, aligning ownership with accountability. Dictating both goals and methods, limiting choice to trivialities, or soliciting input only to override it are empowerment in name only.

A decision affects the whole team, and you want strong buy-in and commitment to the outcome. Which decision approach is best?

• a.Poll the team anonymously and go with a bare majority without any group discussion of the trade-offs
• b.Delay the decision indefinitely until every single member independently arrives at the same conclusion
• c.Make the decision entirely on your own and then announce it to the team as the final word
• d.Facilitate a participatory decision so the team helps shape and commit to the outcome✓

Participatory decision-making builds commitment because people support what they help create, which is valuable when buy-in matters. A unilateral announcement, a discussion-free vote, or waiting for spontaneous unanimity all sacrifice the engagement that participation generates.

Your empowered team makes a decision that turns out poorly, though their reasoning was sound given what they knew. How should you respond?

• a.Publicly identify exactly who made the call so that accountability for the poor outcome is clear
• b.Quietly take over all future decisions of that type yourself to avoid a repeat of the bad result
• c.Revoke the team's decision-making authority going forward in order to prevent any similar mistakes
• d.Support the team, treat it as a learning opportunity, and reinforce that reasonable decisions are backed✓

Sustaining empowerment means backing sound decisions even when outcomes disappoint and extracting the learning, which preserves the team's willingness to decide. Revoking authority, singling people out, or reclaiming decisions punishes good process and destroys the trust empowerment requires.

You need to make an important decision quickly, but you lack specific expertise that several team members have. What is the best approach?

• a.Wait to make the decision until you have personally become an expert on the topic yourself
• b.Delegate the entire decision to whichever team member happens to be available first at the moment
• c.Gather the experts' input rapidly, then decide with their knowledge informing the choice✓
• d.Decide immediately on your own authority to avoid any delay, since speed is the priority right now

Good decision-making draws on those with relevant expertise; consulting them quickly improves the decision without sacrificing needed speed. Deciding alone ignores available knowledge, delegating to whoever is free ignores expertise, and waiting to self-educate is impractical under time pressure.

To help your team make better decisions independently, what should you provide?

• a.Only the final answers you have already reached, without sharing any of the reasoning behind them
• b.Frequent reminders that mistakes will not be tolerated so that people are careful in their choices
• c.A firm rule that all decisions of any significance must be escalated up to you before action is taken
• d.Clear decision-making criteria and the context behind goals so the team can weigh trade-offs itself✓

Teams decide well independently when they understand the criteria and context needed to weigh trade-offs, enabling aligned autonomous choices. Mandating escalation, hiding the reasoning, or instilling fear of mistakes all suppress the independent judgment you want to build.

Some team members are eager to take on more decision authority while others are not yet ready. How should you empower them?

• a.Delegate decision authority progressively, matched to each member's demonstrated readiness✓
• b.Give authority only to the members who ask for it, without regard to their actual capability
• c.Grant every member identical decision authority immediately regardless of their current readiness
• d.Withhold decision authority from everyone until even the least ready member is fully prepared for it

Empowerment is most effective when calibrated to readiness, extending authority as members demonstrate capability. Granting uniform authority ignores differences, holding everyone back to the slowest stalls growth, and going purely by who asks ignores actual capability.

A globally distributed team struggles because members rarely interact outside of formal meetings and feel like strangers. What should the project manager do?

• a.Create intentional opportunities for informal connection and relationship-building across the team✓
• b.Accept that geographically distributed teams cannot realistically build genuine relationships anyway
• c.Require everyone to keep cameras off in calls in order to reduce the fatigue of frequent meetings
• d.Increase the number of formal status meetings so that members are simply in contact more often

Distributed teams need deliberate space for the informal interaction that co-located teams get naturally, which builds the trust behind collaboration. Adding formal meetings, giving up on connection, or removing the visual cues that aid rapport all fail to address the relationship gap.

A virtual team spanning many time zones finds that one region always has to join meetings in the middle of the night. How should you address this fairness issue?

• a.Cancel synchronous meetings entirely and rely only on asynchronous chat for all coordination
• b.Ask the affected region to permanently adjust their personal schedules to fit the meeting time
• c.Keep the current meeting time because changing it would inconvenience the larger group of members
• d.Rotate meeting times so the inconvenience is shared, and record sessions for those who cannot attend live✓

Fair virtual collaboration rotates meeting burdens and provides recordings so no single group bears the cost, sustaining engagement and equity. Freezing an unfair time, eliminating all real-time contact, or forcing one region to sacrifice repeatedly breeds resentment and disengagement.