Project Management Professional (PMP) — All Questions

You want feedback within the team to flow in all directions, not just from you downward. What should you encourage?

• a.A culture of regular, constructive peer feedback alongside your own, with norms that keep it respectful and useful✓
• b.Feedback that flows only from the project manager downward in order to maintain clear control
• c.Anonymous complaints submitted in private as the team's main channel for raising any concerns
• d.Feedback exchanged only during the formal annual review cycle rather than throughout the year

Multidirectional, constructive peer feedback with healthy norms accelerates team learning and cohesion beyond top-down input alone. Restricting feedback to the PM, relying on anonymous complaints, or limiting it to annual reviews all choke the continuous feedback a strong team needs.

A capable team is being slowed by an external dependency outside their control that keeps changing. What is the project manager's best role?

• a.Actively manage the external dependency and shield the team from its disruption so they can stay productive✓
• b.Tell the team to simply absorb the disruption from the external dependency as best as they can
• c.Publicly blame the external party for the delays and otherwise take no concrete action yourself
• d.Wait for the external party to stabilize its work on its own before taking any action at all

The PM adds value by managing volatile external dependencies and buffering the team so they can keep delivering. Telling the team to just cope offloads a problem they cannot control, passively waiting cedes influence, and public blame accomplishes nothing constructive.

You want to make sure quieter team members' concerns about the plan are heard before you finalize it. What is the best approach?

• a.Consider input only from the members who happen to speak up on their own without prompting
• b.Actively solicit input through multiple channels and give space for concerns before finalizing the decision✓
• c.Assume that the absence of objections simply means the plan is fully supported by everyone
• d.Finalize the plan first and then let anyone who has an objection raise it afterward if they wish

Proactively soliciting input across channels ensures quieter voices and their concerns shape the plan before it is locked in. Finalizing first, treating silence as support, or only hearing the vocal few systematically overlooks valuable perspectives and weakens buy-in.

A team member repeatedly commits to deadlines and misses them without communicating. What should the project manager do first?

• a.Assume the member is fundamentally unreliable and quietly plan the project around them instead
• b.Have a direct, supportive conversation to understand the cause and agree on realistic commitments and communication✓
• c.Publicly track the member's missed deadlines in front of the team to motivate them to improve
• d.Simply stop assigning the member any time-sensitive work so that missed deadlines cannot happen

A direct, supportive conversation uncovers whether the cause is overcommitment, blockers, or estimation, and rebuilds reliable commitment and communication. Removing time-sensitive work sidelines them, public tracking shames them, and silently planning around them never addresses the root issue.

You are coaching your team toward self-organization, but they still expect you to assign every task. What should you do?

• a.Assign the tasks yourself but ask the team to pretend afterward that they had chosen them
• b.Keep assigning the tasks yourself as before since the team clearly prefers to work that way
• c.Stop assigning any tasks abruptly and simply leave the team to cope however they manage to
• d.Gradually shift task selection to the team, coaching them to pull work and coordinate among themselves✓

Self-organization is built by gradually transferring task selection to the team with coaching so they learn to pull and coordinate work. Continuing to assign entrenches dependence, an abrupt stop leaves them overwhelmed, and a pretense of self-organization builds nothing real.

The team is unsure how to handle disagreements respectfully, and past conflicts turned personal. What proactive step helps most?

• a.Let each member handle conflict however they personally see fit without any shared guidance
• b.Ban disagreements among the members outright in order to keep all team interactions civil
• c.Wait until the next serious conflict actually erupts and only then address how to handle it
• d.Establish ground rules for how the team will handle disagreement and conflict constructively✓

Agreeing ground rules for constructive disagreement in advance gives the team a shared, respectful way to handle conflict before it turns personal. Banning disagreement suppresses needed debate, waiting for the next blowup is reactive, and leaving it to individual styles reproduces the past problems.

A member with deep expertise is reluctant to share knowledge, creating a bottleneck and single point of failure. How should you address this?

• a.Order the expert to document everything they know immediately or else face formal consequences
• b.Accept the bottleneck as it is since the expert is still highly productive on their own work
• c.Understand their reasons and create incentives and a culture that value knowledge sharing and mentoring others✓
• d.Route all of the related work exclusively through the expert since they know the most about it

Reluctance to share often has underlying reasons; understanding them and cultivating a culture that rewards knowledge sharing and mentoring reduces the single point of failure sustainably. Issuing threats breeds resentment, accepting the bottleneck ignores the risk, and concentrating work worsens it.

You want the team to feel collective ownership of the project's success rather than just their individual tasks. What most fosters this?

• a.Connect individual work to shared team goals and outcomes, and celebrate successes as a team✓
• b.Emphasize to each member that they are responsible only for their own individual part of the work
• c.Reward high-performing individuals privately so that the rest of the team does not find out
• d.Set individual targets for each member that end up competing against the team's own goals

Collective ownership grows when people see how their work connects to shared goals and successes are celebrated together. Competing individual targets, a strictly siloed view of responsibility, and hidden individual rewards all reinforce individualism over shared ownership.

During a negotiation over a deadline, the other party becomes positional and stops listening. What technique can help move the conversation forward?

• a.Walk away from the negotiation immediately at the very first sign of positional behavior
• b.Threaten to escalate the matter to higher authority if they do not agree to your terms soon
• c.Actively listen and acknowledge their position, then refocus on shared interests and objective criteria✓
• d.Restate your own demand even more forcefully than before until the other party finally yields

Active listening and acknowledgment lower defensiveness, and returning to shared interests and objective criteria reopens productive negotiation. Forcefully repeating demands entrenches positions, threats damage the relationship, and walking away at the first difficulty forfeits a workable deal.

A team member is technically excellent but frequently dismissive of others' ideas, hurting collaboration. What is the best approach?

• a.Publicly reprimand the member for the behavior so that the rest of the team feels validated
• b.Overlook the dismissive behavior entirely because the member's technical work is genuinely strong
• c.Give specific feedback on the impact of the behavior and coach them toward more collaborative interactions✓
• d.Remove the member from all collaborative work so their behavior can no longer affect others

Specific feedback on the collaboration impact plus coaching helps a strong contributor improve their interpersonal behavior while retaining their skills. Overlooking it lets the harm continue, public reprimand humiliates and escalates, and isolating them from collaboration wastes their expertise and dodges the issue.

You want to ensure the team's daily coordination is effective without wasting time. What practice best achieves this for the team?

• a.A short, focused daily sync where the team coordinates work, surfaces blockers, and aligns for the day✓
• b.A daily status meeting in which each member reports individually to the project manager alone
• c.A long daily meeting that carefully reviews the status of every single task in full detail
• d.No regular sync at all, relying instead on people to reach out to each other only when needed

A short, focused daily sync lets the team coordinate, raise blockers, and align efficiently, serving the team rather than a status ritual. A long detailed meeting wastes time, no sync leaves coordination to chance, and a PM-directed status report misses the peer coordination purpose.

A stakeholder challenges the team's estimates as too conservative and pressures them to commit to a shorter timeline. How should the project manager respond?

• a.Refuse to discuss the team's estimates any further with the stakeholder once they are questioned
• b.Accept the shorter timeline that the stakeholder is pushing for in order to keep them satisfied
• c.Explain the basis for the estimates, involve the team, and negotiate a realistic commitment grounded in evidence✓
• d.Let the team quietly pad its future estimates to protect itself against this kind of pressure

Defending estimates with their rationale, involving the team, and negotiating an evidence-based commitment protects both delivery and the relationship. Caving to pressure sets the team up to fail, refusing to engage damages the relationship, and secret padding erodes trust and transparency.

You realize a decision you made was wrong after new information emerged. What is the best leadership action with the team?

• a.Stick with your original decision anyway in order to appear consistent and decisive to the team
• b.Blame the new information for the earlier decision being wrong rather than owning the change
• c.Change course quietly on your own without explaining to the team why the decision has changed
• d.Acknowledge the change openly, explain the new information, and adjust the decision transparently✓

Openly acknowledging new information and adjusting transparently models good judgment and builds trust; changing your mind with reason is a strength. Clinging to a wrong decision for appearances harms the project, changing quietly breeds confusion, and blaming circumstances dodges accountability.

Your team includes both agile-experienced members and newcomers unfamiliar with agile ways of working. How should you help the team gel?

• a.Provide coaching and knowledge sharing so experienced members help newcomers learn the practices and mindset✓
• b.Separate the experienced members and the inexperienced newcomers into two entirely different teams
• c.Assume the newcomers will absorb agile practices over time without any deliberate support at all
• d.Slow the entire team down to the working pace of its single least experienced newcomer

Coaching and peer knowledge sharing help newcomers learn agile practices and mindset, blending the team into a cohesive unit. Splitting the team fragments it, assuming osmosis leaves newcomers lost, and dragging everyone to the slowest pace frustrates the experienced members.

A team member raises a concern that turns out to be a false alarm. How should you respond to keep people raising concerns?

• a.Ask the member to fully verify any concern themselves before ever raising it with you again
• b.Point out to the member that they ended up wasting the team's time on a complete non-issue
• c.Thank them for raising it, reinforcing that speaking up is valued regardless of the outcome✓
• d.Quietly note the false alarm on the member's record to discourage similar reports in future

Thanking someone for a false-alarm concern keeps the channel open so real issues continue to surface early. Criticizing the false alarm, requiring full verification before raising anything, or penalizing them teaches people to stay silent, which is far more dangerous.

You want to help your team maintain focus and protect their productive time from constant interruptions. What should you do?

• a.Pass every incoming request straight through to the team exactly as it arrives to keep it moving
• b.Shield the team from unnecessary interruptions and help establish focus time and clear intake for requests✓
• c.Schedule frequent check-in meetings that end up interrupting the team's work on a regular basis
• d.Tell the team members to simply ignore the interruptions on their own as best as they are able

Protecting the team by filtering interruptions and establishing focus time and a clear intake process preserves productivity. Forwarding every request, telling the team to fend off interruptions alone, or adding frequent check-ins all increase the disruption you should be reducing.

A team member's cultural norm is to avoid openly disagreeing with authority, so they rarely voice concerns to you directly. How can you get their input?

• a.Adapt your approach with alternative, culturally comfortable channels for feedback and show that input is genuinely welcomed✓
• b.Only seek input from the members who are already comfortable challenging you to your face
• c.Conclude that the member simply has no concerns to raise since they consistently stay silent
• d.Insist that the member disagree with you openly and directly just like everyone else on the team

Adapting to culturally comfortable feedback channels and demonstrating that input is welcomed surfaces perspectives you would otherwise miss. Insisting on a style that conflicts with their norms, assuming silence means agreement, or valuing only direct challengers all lose valuable input.

The team is excited but overcommitting, planning more than it can sustainably deliver. As their coach, what should you do?

• a.Help the team plan realistically based on capacity and evidence, protecting a sustainable pace✓
• b.Let the team overcommit as it wishes and allow it to learn from the inevitable failure to deliver
• c.Encourage the team's ambition further and add even more work on top of the plan they already have
• d.Cut down the team's plan yourself without involving the members in the decision to reduce it

Coaching the team to plan within capacity and sustain pace prevents burnout and missed commitments while keeping ownership with the team. Letting them fail wastes morale, unilaterally cutting the plan removes ownership, and encouraging further overcommitment compounds the problem.

You want to know whether your leadership is actually helping the team or getting in their way. What is the best way to find out?

• a.Assume that your leadership must be effective simply because the project is making progress
• b.Avoid asking the team for feedback at all so that you do not end up inviting any criticism
• c.Ask the team for honest feedback on your leadership and act on it, modeling openness to improvement✓
• d.Rely only on your own manager's assessment of your leadership rather than the team's view

Seeking and acting on the team's honest feedback about your leadership provides the most relevant signal and models the openness you want in the team. Assuming effectiveness from progress, relying solely on your manager, or avoiding feedback all leave you blind to your real impact on the team.

A member of your team is going through a personal hardship that is affecting their work. What is the most appropriate leadership response?

• a.Show empathy, offer reasonable support and flexibility, and adjust workload temporarily as needed✓
• b.Hold the member to exactly the same output as before and ignore the personal situation entirely
• c.Discuss the member's personal situation with the rest of the team so they can offer support
• d.Immediately reduce the member's role on the project on a permanent basis to protect delivery

Empathetic leadership offers reasonable support and temporary flexibility to a member facing hardship, sustaining trust and eventual performance. Ignoring the situation is callous, a permanent role reduction overreacts, and sharing their private matter with the team violates confidentiality.

You want the team to continuously improve rather than settling into fixed routines. What practice most supports this?

• a.Regular retrospectives where the team reflects and commits to specific improvements each cycle✓
• b.Improving the way the team works only when a serious problem eventually forces a change
• c.Keeping the team's process fixed once it is working adequately so nothing risks being disrupted
• d.Having the project manager dictate all improvements without any reflection from the team

Regular retrospectives that produce owned improvement actions drive continuous improvement as a team habit. A frozen process stagnates, waiting for serious problems is reactive, and PM-dictated changes without team reflection lack the ownership continuous improvement depends on.

A stakeholder consistently communicates only through one team member, bypassing agreed channels and overloading that member. What should you do?

• a.Cut the stakeholder off from communicating with the team entirely to relieve the pressure
• b.Let the current arrangement simply continue since project information is still flowing through it
• c.Tell the overloaded team member that they should just handle the extra communication themselves
• d.Clarify the agreed communication channels with the stakeholder and redistribute the load appropriately✓

Reaffirming agreed communication channels and redistributing the load protects the overloaded member and keeps information flowing appropriately. Allowing the pattern overloads one person and creates a single point of failure, telling them to cope ignores the strain, and cutting the stakeholder off damages the relationship.

Halfway through a sprint, the project manager realizes team members hold different assumptions about what "done" means for a user story, causing rework. What is the best way to build shared understanding?

• a.Let each developer apply their own quality bar to move faster
• b.Facilitate the team in agreeing on an explicit definition of done and post it where everyone can see it✓
• c.Ask the product owner to write more detailed acceptance criteria alone
• d.Have the project manager personally inspect every finished story against their own private checklist and be the sole person permitted to mark it accepted for the team

A shared definition of done creates a common, transparent standard the whole team owns, preventing divergent assumptions and rework. Individual quality bars fragment understanding, PM inspection creates a bottleneck, and having the product owner work alone misses the team's collective agreement that makes the definition binding.

A team agreed on a ground rule that everyone keeps cameras on during remote standups, but two members repeatedly join with cameras off. What should the project manager do?

• a.Revisit the ground rule with the team, understand the reasons, and reaffirm or adjust the agreement together✓
• b.Quietly drop the ground rule since it is not being followed
• c.Immediately report both members to their functional managers and request that the camera-off behavior be formally documented in their performance records
• d.Turn off their own camera too so no one feels singled out

Ground rules are owned by the team, so enforcement means bringing the issue back to the group to understand root causes and re-commit or revise. Reporting members escalates prematurely, silently dropping the rule undermines all agreements, and mirroring the behavior abandons the norm the team set.

During a sprint, the team is blocked because a required test environment is unavailable and only the IT department can provision it. What is the servant-leader project manager's primary responsibility?

• a.Engage IT directly to remove the impediment so the team can resume work✓
• b.Ask the team to build their own workaround environment
• c.Tell the team to work on lower-priority tasks and wait for IT
• d.Log the blocker in the risk register and address it next sprint

Removing impediments that are beyond the team's control is a core servant-leader duty, so the PM works with IT to clear the blocker quickly. Merely reassigning work leaves the impediment in place, deferring to next sprint delays value, and pushing the team to improvise adds risk they should not have to absorb.

A project manager leads a team where members come from cultures with very different attitudes toward directness and hierarchy. Some stay silent in group settings. How should the PM foster participation?

• a.Insist that every team member adopt the same direct, low-context communication style so meetings become faster and no one has to interpret indirect signals
• b.Adapt facilitation to offer multiple channels for input, such as written feedback and small groups, respecting cultural differences✓
• c.Assume the quiet members have nothing to add and proceed
• d.Require everyone to speak in turn so no one can stay quiet

Cross-cultural leadership means adapting communication approaches so everyone can contribute in a way that fits their comfort, such as anonymous or written channels and smaller groups. Forcing a single style or public turn-taking ignores cultural context, and assuming silence means no input wastes team knowledge.

A developer solved a critical production issue over the weekend, saving a major client relationship. How should the project manager best recognize this contribution?

• a.Give everyone on the team an identical reward to keep things equal
• b.Give a private thank-you and consider it handled
• c.Wait until the formal annual performance review to mention the achievement so it can be weighed objectively alongside all of the person's other yearly contributions
• d.Acknowledge the achievement genuinely in a way meaningful to the individual and visible to peers, tied to the impact✓

Effective recognition is timely, sincere, tied to specific impact, and delivered in a form the individual values, which reinforces motivation and desired behaviors. Delaying to the annual review loses immediacy, identical blanket rewards dilute the meaning, and a purely private note may under-recognize a team-visible contribution.

A high-performing, experienced team consistently delivers and needs little day-to-day direction. Which leadership style is most appropriate for the project manager to adopt?

• a.Directive, assigning detailed tasks and closely supervising execution
• b.Coaching, focusing heavily on skill-building fundamentals
• c.Delegating, empowering the team to self-organize while the PM removes obstacles✓
• d.Autocratic, making all decisions to maintain control

Situational leadership matches style to team maturity; a capable, motivated team performs best with a delegating style that grants autonomy while the leader clears obstacles. Directive or autocratic styles demotivate mature teams, and heavy coaching on fundamentals is better suited to less experienced members.

Two senior stakeholders disagree sharply over a requirement, and the dispute is stalling the team. The project manager wants a durable outcome both can support. Which conflict-resolution approach is best?

• a.Collaborate to find a solution that integrates both parties' underlying interests✓
• b.Withdraw and let the stakeholders resolve it themselves later
• c.Force a decision by siding with the more senior stakeholder
• d.Smooth over the disagreement by emphasizing points of agreement only

Collaborating (problem-solving) seeks a win-win by addressing the underlying interests of both parties, producing the most durable commitment. Forcing creates a loser, smoothing only masks the issue temporarily, and withdrawing leaves the conflict unresolved and the team blocked.

During negotiation with a vendor over a schedule slip, the project manager wants to preserve a long-term partnership while still protecting the project. What negotiation posture is most effective?

• a.Take a hard positional stance and demand full penalties
• b.Avoid the conversation and absorb the delay silently
• c.Focus on interests behind each position and seek options for mutual gain✓
• d.Concede whatever the vendor asks to keep them happy

Interest-based (principled) negotiation focuses on the parties' underlying needs and generates options for mutual gain, protecting both the project and the relationship. Hard positional demands damage the partnership, unconditional concession sacrifices the project, and avoidance forfeits any chance to recover.

A team member frequently interrupts others and dismisses ideas in meetings, and colleagues have started to disengage. What should the project manager do first?

• a.Speak with the member privately, share the observed impact, and agree on more constructive behaviors✓
• b.Publicly correct the behavior in the next meeting to set an example
• c.Reassign the disruptive member to a different project right away so the current team can recover its psychological safety without any further confrontation
• d.Ignore it because the member is technically strong

Emotionally intelligent leadership addresses behavior privately, focusing on observed impact and agreeing on change, which preserves the member's dignity and the team's safety. Public correction humiliates, reassignment is premature, and ignoring the behavior lets it continue eroding psychological safety.

A stakeholder with high power and high interest has become skeptical after an early setback and is now withholding support. How should the project manager re-engage them?

• a.Reduce communication until results improve on their own
• b.Provide the stakeholder only with carefully curated positive updates and omit the setbacks so that their confidence in the project is gradually rebuilt over time
• c.Route all interactions through the sponsor to avoid the stakeholder
• d.Meet to understand their concerns, share transparent progress, and involve them in shaping the path forward✓

A high-power, high-interest stakeholder must be managed closely; re-engaging means understanding concerns, being transparent, and involving them in solutions to rebuild trust. Reducing contact, filtering out bad news, or avoiding them entirely all deepen disengagement and risk losing critical support.

A new team is forming and members are polite but hesitant, unsure of roles and how decisions will be made. According to team development stages, what does the team most need now?

• a.Clear direction on goals, roles, and working agreements to move through forming✓
• b.Intense conflict facilitation to accelerate bonding
• c.Formal performance rankings to spur competition
• d.Minimal involvement so they can figure things out independently

In the forming stage, teams need orientation and clarity about goals, roles, and working agreements to establish a foundation. Withholding involvement leaves them adrift, forcing conflict is misaligned with this stage, and performance rankings undermine the trust that is still being built.

The project manager notices team members completing tasks but rarely helping one another or sharing information. How can the PM best build genuine collaboration?

• a.Assign larger individual workloads to keep everyone busy
• b.Create shared goals, encourage pairing and knowledge sharing, and celebrate collective outcomes✓
• c.Discourage cross-talk so members focus solely on their own work
• d.Measure and reward only individual task completion so each member has a clear personal incentive to finish their own assigned work as quickly as possible

Collaboration grows when success is defined collectively; shared goals, pairing, and recognition of team outcomes incentivize members to help one another. Rewarding only individual output or discouraging interaction reinforces silos, and simply adding workload does nothing to connect the team.

A team member raises a serious safety concern about a deliverable but seems worried about being blamed. What is the most important thing the project manager should reinforce?

• a.That raising concerns is acceptable only when there is a proven solution
• b.That concerns should be raised only through formal written channels
• c.That the team is psychologically safe to speak up, and thank the member for surfacing the concern✓
• d.That the member should first confirm the issue is real before speaking up

Psychological safety is the belief that one can raise concerns or mistakes without fear of blame, and leaders reinforce it by welcoming and thanking those who speak up. Requiring proof, solutions, or formal-only channels before voicing concerns raises the barrier to reporting and can suppress critical safety information.

A junior team member is eager but makes frequent mistakes because they lack experience with the tools. Which leadership approach best fits their development level?

• a.A hands-off style that waits for them to learn by trial and error
• b.A coaching style that provides guidance, feedback, and skill-building support✓
• c.An autocratic style that removes their decision-making entirely
• d.A delegating style that leaves them to work independently

Situational leadership pairs an enthusiastic but low-competence member with a coaching style that builds skills through guidance and feedback. Delegating or hands-off approaches overwhelm someone still learning, and an autocratic style stifles the growth the member is ready to pursue.

An impediment reported in the daily standup is outside the team's authority to resolve and requires a decision from a director in another department. What should the project manager do?

• a.Escalate the impediment promptly to the director with the needed context and a clear ask✓
• b.Tell the team to engineer a temporary workaround on their own, regardless of the impact on quality, so that the sprint goal is not put at any risk
• c.Close the impediment as unresolvable and move on
• d.Wait for the director to notice the issue on their own

When an impediment exceeds the team's authority, the servant-leader escalates it quickly to the right decision-maker with enough context to act. Waiting passively delays resolution, forcing a workaround risks quality, and closing it as unresolvable abandons the team's need.

Two teams that must integrate their work disagree over interface ownership, and each blames the other for delays. How should the project manager help them resolve it?

• a.Separate the teams entirely so they never have to coordinate
• b.Let the delay continue until one team concedes
• c.Decide the interface ownership unilaterally as the project manager and impose that decision on both teams so the delay ends without a lengthy negotiation
• d.Bring both teams together to clarify interfaces, agree on responsibilities, and define how they will collaborate✓

Cross-team conflict over shared work is best resolved by facilitating a joint conversation that clarifies interfaces and establishes shared responsibilities and collaboration norms. Imposing a decision breeds resentment, waiting prolongs the delay, and separating interdependent teams makes integration impossible.

A globally distributed team struggles because members interpret written messages differently, leading to misunderstandings. What is the best way to strengthen shared understanding?

• a.Rely on longer written documents to remove any ambiguity
• b.Use richer communication such as video calls for complex topics and confirm understanding through active listening✓
• c.Require all members to gradually become fluent in one another's native languages so that written messages can never again be misinterpreted across the team
• d.Limit communication to reduce the chance of misinterpretation

Complex or ambiguous topics benefit from richer communication channels like video, paired with active listening and confirmation to verify shared meaning across cultures. Demanding language fluency is unrealistic, longer documents add ambiguity, and limiting communication reduces the very interaction needed for alignment.

During a retrospective, the team identifies that unclear priorities are their biggest impediment, but resolving it depends on the product owner. What should the project manager do?

• a.Note the impediment and revisit it only if it appears again
• b.Tell the team that priority-setting is not their concern
• c.Facilitate a conversation with the product owner to clarify and stabilize priorities, and track the action to closure✓
• d.Ask the team to guess at the most likely priorities using their own judgment so that work can continue without waiting on the product owner's input

Impediment removal includes connecting the team with the person who can resolve the blocker and following the action through to closure. Deferring, having the team guess, or dismissing their concern all leave the root impediment in place and undermine the value of the retrospective.

A team consistently meets commitments and members openly challenge one another's ideas while remaining respectful and focused on shared goals. Which team development stage is this?

• a.Storming, because members are challenging each other
• b.Forming, because roles are still being defined
• c.Performing, because the team is productive and self-managing with healthy debate✓
• d.Adjourning, because the work is nearly complete

In the performing stage, a team is cohesive, self-managing, and delivers reliably, with disagreement channeled constructively toward shared goals. Forming lacks this maturity, storming involves unresolved friction rather than respectful challenge, and adjourning refers to disbanding at project close.

A team member who has been the sole expert on a critical component is planning to leave the organization in two months. What should the project manager prioritize?

• a.Ask the member to document everything on their last day
• b.Delay the departure by denying the resignation request
• c.Arrange knowledge transfer and pairing now so expertise is shared before the member departs✓
• d.Assume another team can reverse-engineer the component later

Reducing key-person risk requires proactive knowledge transfer, such as pairing and documentation while the expert is still available. Waiting until the last day compresses transfer too much, assuming reverse-engineering adds risk and cost, and blocking a resignation is neither feasible nor respectful.

During a conflict between two team members, the project manager finds the disagreement is minor and the team is under intense deadline pressure. Which conflict-handling approach may be most practical in this moment?

• a.Force a resolution immediately regardless of the deadline
• b.Ignore the conflict permanently and hope it disappears
• c.Temporarily smooth or accommodate to keep delivery moving, then address the issue fully after the deadline✓
• d.Escalate the minor interpersonal issue to senior management so a neutral higher authority can impose a binding resolution before the deadline arrives

Conflict style should fit the situation; for a minor issue under acute time pressure, smoothing or accommodating can maintain progress, provided the PM returns to resolve the root cause afterward. Forcing wastes goodwill on a minor matter, escalation is disproportionate, and permanent avoidance lets issues fester.

A project manager wants the team to feel collective ownership of their working agreements rather than following rules imposed from above. How should the ground rules be created?

• a.Have the sponsor dictate the rules for consistency
• b.Facilitate the team to co-create the ground rules together and agree to uphold them✓
• c.Skip formal ground rules and rely on common sense
• d.Write the ground rules based on the last project and hand them out

Team-created ground rules generate ownership and accountability because members are more likely to honor agreements they shaped. Imported or sponsor-dictated rules feel imposed, and skipping ground rules entirely leaves behavior expectations ambiguous and inconsistently applied.

A remote team member has been noticeably withdrawn and their output has dropped. The project manager suspects a personal or motivational issue. What is the best first step?

• a.Raise the performance dip publicly to encourage accountability
• b.Reach out privately with empathy to check in and understand what is going on✓
• c.Issue a formal performance warning to prompt improvement
• d.Reassign the member's tasks without discussion

Emotionally intelligent leadership begins with a private, empathetic check-in to understand the situation before drawing conclusions or acting. A formal warning, silent reassignment, or public callout all skip understanding the cause and can worsen disengagement.

The project manager wants to ensure the whole team truly shares the same understanding of the project vision and how their work connects to it. Which practice best achieves this?

• a.Email the vision statement once at kickoff
• b.Assume understanding because no one asked questions
• c.Keep the detailed vision at the leadership level to avoid overwhelming the team, sharing only the specific tasks each member needs to complete their work
• d.Co-create and regularly reinforce the vision, inviting the team to connect their work to it and asking clarifying questions✓

Shared understanding of vision is built through co-creation and ongoing reinforcement, with dialogue that lets members link their work to the goal. A one-time email, silence mistaken for comprehension, or withholding the vision from the team all leave alignment to chance.

A team member proposes an idea that the project manager believes is flawed, but the member is enthusiastic and other members are watching. How should the servant-leader respond?

• a.Acknowledge the thinking, ask questions to explore it, and let the team evaluate it collaboratively✓
• b.Change the subject to spare the member embarrassment
• c.Immediately and directly point out to the enthusiastic member all of the reasons the idea will not work so the team does not waste any time exploring it
• d.Approve the idea to avoid discouraging the member

Servant-leaders encourage contribution and shared decision-making by acknowledging input, asking exploratory questions, and letting the team assess ideas on their merits. Dismissing the idea discourages participation, rubber-stamping it ignores real concerns, and deflecting avoids the productive discussion.

A team's ground rules include a rule to keep discussions respectful, but during a heated debate one member makes a personal remark about another. What should the project manager do in the moment?

• a.Let the debate continue so the tension resolves itself
• b.Make a personal remark back to demonstrate consequences
• c.End the meeting abruptly without addressing the remark
• d.Calmly intervene, remind the group of the agreed respect norm, and refocus on the issue✓

Enforcing ground rules in real time means calmly restating the agreed norm and redirecting the group to the issue, protecting a respectful environment. Allowing the remark to stand normalizes it, ending the meeting avoids the problem, and retaliating violates the very norm being upheld.

The project manager wants to recognize the team's effort after a demanding release, but the members value different things: some want public praise, others prefer time off or learning opportunities. What is the best approach?

• a.Give every team member the same identical public award for the sake of simplicity and fairness, regardless of what each individual personally values as recognition
• b.Provide no recognition to avoid appearing to play favorites
• c.Recognize only the top contributor to set a benchmark
• d.Tailor recognition to what each member values while affirming the team's collective achievement✓

Effective recognition accounts for individual preferences, since a meaningful reward for one person may not motivate another, while still honoring the team's shared success. Uniform awards ignore differences, withholding recognition demotivates, and singling out one person can undermine team cohesion.

A newly assigned team includes members from partner organizations who are used to different processes and terminology. How can the project manager accelerate a shared way of working?

• a.Let each partner keep their own separate process indefinitely
• b.Avoid the topic and let processes align naturally over time
• c.Impose the project manager's own home-organization process and terminology on everyone immediately so there is a single consistent standard from the first day
• d.Facilitate creating a common working agreement and glossary that blends practices the team commits to✓

A shared working agreement and common glossary, co-created across partners, quickly establish a unified way of working and shared vocabulary. Imposing one side's process breeds resistance, keeping separate processes causes friction, and hoping for natural alignment prolongs confusion.