Project Management Professional (PMP) — All Questions

A PM discovers that a critical path activity can be shortened by paying for overtime, adding cost but saving time. Before approving, what should the PM verify?

• a.That scope will be reduced to offset the cost
• b.That the time saved is on the critical path and the added cost is justified and approved✓
• c.That the activity has ample float already
• d.That the change can bypass change control for speed, since crashing only affects cost and not the approved scope

Crashing is worthwhile only when the compressed activity is on the critical path and the added cost is justified and properly approved. Activities with ample float would not shorten the project, scope reduction is a different lever, and no change should bypass change control.

A project manager is engaging a seller under a time-and-materials contract for an urgent, loosely defined task. What control is most important to include?

• a.Full cost reimbursement with no oversight
• b.A not-to-exceed ceiling and clear labor rates to limit open-ended cost✓
• c.Assuming no special controls are needed, since time-and-materials contracts carry inherently low cost risk to the buyer
• d.A fixed deliverable price with no rate schedule

Because T&M is open-ended, a not-to-exceed ceiling and defined labor rates cap the buyer's exposure while retaining flexibility. Assuming no risk, using a fixed price without rates, or reimbursing without oversight would leave cost uncontrolled or contradict the T&M structure.

During execution, stakeholders complain they are overwhelmed by too-frequent, overly detailed reports. What should the PM do?

• a.Revisit the communications plan and tailor frequency and detail to each stakeholder's needs✓
• b.Stop reporting to those stakeholders entirely
• c.Send only verbal updates from now on
• d.Continue reporting exactly as-is, since providing more information more often is always better for stakeholders

Effective communication is tailored, so the PM should revisit the communications plan and match the frequency and level of detail to each stakeholder's needs. Stopping reports, keeping the overload, or switching to verbal-only fails to right-size communication to the audience.

A PM wants to identify risks by leveraging the collective knowledge of the team and experts through structured, anonymous rounds that build consensus. Which technique is this?

• a.Brainstorming
• b.Interviews
• c.SWOT analysis
• d.The Delphi technique✓

The Delphi technique gathers expert input anonymously across multiple rounds to build consensus while reducing bias and dominance effects. SWOT and brainstorming are open group methods, and interviews are one-on-one, none providing the anonymous, iterative consensus of Delphi.

A project manager is quantifying which individual risks have the greatest potential impact on the project's objective by varying one factor at a time. Which diagram displays this?

• a.A control chart
• b.A tornado (sensitivity) diagram✓
• c.A responsibility assignment matrix
• d.A cumulative flow diagram

A tornado diagram from sensitivity analysis ranks risks by their impact on an objective, displaying the most influential factors as the widest bars at the top. Cumulative flow diagrams, control charts, and RAMs address flow, process variation, and roles, not risk sensitivity.

A PM must decide how to handle a low-priority threat that is not worth the cost of a proactive response, choosing instead to set aside contingency and monitor it. Which response is this?

• a.Transfer via insurance
• b.Mitigation through redesign of the affected work to lower the threat's probability before it has any chance to occur
• c.Passive acceptance combined with contingency reserve for a form of active acceptance✓
• d.Active avoidance

Acceptance acknowledges a risk without proactive change; active acceptance establishes a contingency reserve and monitoring while passive acceptance simply documents it. Avoidance, transfer, and mitigation all involve proactive action inappropriate for a low-priority threat not worth that cost.

During a project, the PM realizes that the schedule, cost, and scope baselines are being tracked separately with no integrated view of performance. What should the PM establish?

• a.A rule to update all of the baselines every week regardless of whether any approved changes have actually occurred
• b.Separate dashboards that are never reconciled
• c.A performance measurement baseline integrating scope, schedule, and cost for earned value✓
• d.A focus on schedule only, ignoring cost

The performance measurement baseline integrates scope, schedule, and cost so earned value analysis can measure integrated performance against a single reference. Isolated dashboards, a schedule-only focus, or arbitrary baseline updates prevent a coherent view of project performance.

A team practicing continuous integration wants fast feedback on whether new code breaks the build. Which practice most directly supports this?

• a.Manual testing once per release
• b.A quarterly integration event
• c.Waiting until the end of the sprint to integrate
• d.Automated builds and tests triggered on each code commit✓

Automated builds and tests on each commit give immediate feedback when code breaks, a core continuous integration practice that reduces integration risk. Manual, quarterly, or end-of-sprint integration delays feedback and lets defects accumulate, undermining the fast-feedback goal.

A PM is starting a hybrid initiative and must decide governance. The organization requires phase-gate funding approvals, but delivery teams work in sprints. How can both coexist?

• a.Abandon phase gates entirely
• b.Force sprints to match multi-month gate cycles
• c.Run the sprints with no connection to funding decisions so the delivery teams stay fully independent of the gates
• d.Align sprint increments to phase gates so gate reviews assess demonstrated increments✓

Hybrid governance aligns iterative delivery with phase-gate funding by timing gate reviews to assess demonstrated, working increments. Abandoning gates ignores organizational funding needs, stretching sprints to gate length defeats agility, and disconnecting sprints from funding removes accountability.

A PM notices the project team is unclear which requirements are must-haves versus nice-to-haves, complicating prioritization. Which technique clarifies this?

• a.Critical path method
• b.Monte Carlo simulation run over the requirement priorities to model the uncertainty in their relative importance
• c.MoSCoW prioritization (Must, Should, Could, Won't)✓
• d.Earned value analysis

MoSCoW prioritization classifies requirements as Must, Should, Could, or Won't have, clarifying relative importance for scope and release decisions. Monte Carlo, earned value, and critical path address uncertainty, performance, and schedule, not requirement prioritization.

A project manager wants to estimate relative effort of backlog items quickly using a scale that reflects uncertainty, avoiding false precision. Which agile technique fits?

• a.A definitive engineering estimate
• b.Story points via planning poker✓
• c.Parametric cost modeling
• d.Bottom-up estimating in exact hours

Story points estimated through planning poker capture relative size and uncertainty without implying false precision, and they support velocity-based forecasting. Exact-hour, parametric, or definitive estimates impose precision that is unwarranted for uncertain, evolving backlog items.

During execution of a fixed-price contract, the seller requests additional payment claiming the buyer's changes increased their costs. What is the appropriate mechanism to resolve this?

• a.Immediately pay whatever the seller requests
• b.Address it through the contract's claims administration and change control provisions✓
• c.Refuse to discuss the request and hold the seller strictly to the original fixed price no matter what has changed
• d.Terminate the contract to avoid the dispute

Contested changes and requests for additional payment are handled through the contract's claims administration and change control provisions, seeking negotiated resolution. Paying blindly, refusing to engage, or terminating the contract escalate risk rather than resolving the claim fairly.

A PM wants to ensure that as the team gains information, near-term work is planned in detail while the overall roadmap stays flexible. Which combination supports this in agile?

• a.A high-level product roadmap with detailed, refined items only for upcoming sprints✓
• b.A frozen backlog that cannot change once set
• c.A fully detailed, item-by-item plan produced for the entire backlog at project start so nothing is left uncertain
• d.No roadmap and no detailed planning at all

Agile pairs a flexible high-level roadmap with just-in-time detailed refinement of only the near-term items, mirroring rolling wave planning. Detailing everything up front wastes effort on uncertain work, having no plan gives no direction, and a frozen backlog contradicts adaptability.

A project manager finds that the team lacks a shared understanding of the overall project objectives and how their work connects to value. What should the PM provide?

• a.A clear vision and objectives that connect the team's work to intended value✓
• b.A detailed schedule with task assignments but no explanation of the purpose or the value behind each activity
• c.A detailed cost breakdown by account
• d.A list of individual task deadlines only

Connecting the team's work to a clear vision and objectives builds shared purpose and motivates value-focused delivery. Task deadlines, cost breakdowns, or a purpose-free schedule provide mechanics without the meaning the team is missing.

A PM is monitoring risks and wants to periodically check whether new risks have emerged, existing risks have changed, and responses remain effective. What is this activity called?

• a.Planning risk responses
• b.Monitoring risks (risk reassessment and audits)✓
• c.Risk identification only
• d.Qualitative risk analysis, which prioritizes risks by probability and impact at a single point early in planning

Monitoring risks includes risk reassessment and risk audits to track existing risks, identify new ones, and evaluate response effectiveness throughout the project. Qualitative analysis, identification, and response planning are earlier, distinct steps rather than the ongoing monitoring activity.

A predictive project's sponsor asks why the PM invests effort in a detailed WBS before scheduling. What is the best justification?

• a.It sets the project budget directly without any further estimating, replacing bottom-up cost analysis entirely
• b.It defines the total scope and provides the basis for estimating, scheduling, and control✓
• c.It replaces the need for a schedule entirely
• d.It is required only for agile projects

The WBS decomposes and defines the total scope of work, forming the foundation for estimating, scheduling, resourcing, and control. It does not replace the schedule, is not agile-only, and does not by itself set the budget without subsequent estimating.

During a sprint review, stakeholders realize a previously high-priority feature is no longer needed due to a market change. What should happen to it?

• a.The sprint is canceled to remove the feature
• b.The product owner removes or deprioritizes it in the backlog to focus on current value✓
• c.It is silently deleted with no stakeholder awareness
• d.The team must still build it because it was formally committed earlier, regardless of the recent shift in the market

The product owner continuously manages the backlog for value, so an obsolete feature is removed or deprioritized transparently. Building unneeded work wastes capacity, silent deletion harms transparency, and canceling the sprint is an extreme step reserved for an invalidated sprint goal.

A project has EV = $250,000 and PV = $250,000, but AC = $300,000. How should the PM characterize performance?

• a.On schedule and on budget
• b.Behind schedule and over budget
• c.Ahead of schedule and under budget
• d.On schedule but over budget✓

SPI = EV/PV = 250,000/250,000 = 1.0 (on schedule) while CPI = EV/AC = 250,000/300,000 = 0.83 (over budget). Equal EV and PV mean planned value has been earned on time, but spending exceeds the value earned, indicating a cost overrun.

A PM is closing a phase and wants to formally confirm that all phase deliverables are accepted before proceeding to the next phase. Which practice accomplishes this?

• a.Updating only the risk register
• b.Starting the next phase without review
• c.Conducting a phase-gate review to verify deliverables and authorize continuation✓
• d.Archiving the phase documents and moving on silently to the next phase without any formal verification or review

A phase-gate review formally verifies that phase deliverables are complete and accepted and authorizes moving to the next phase or stopping. Proceeding without review, updating only one register, or archiving silently skips the governance checkpoint that controls phase transitions.

During execution, a PM must decide how to respond to an identified opportunity to finish early if a partner contributes specialized capability the team lacks. Which opportunity strategy fits?

• a.Avoid
• b.Mitigate
• c.Accept the opportunity passively by taking no proactive action and simply noting it in the risk register for awareness
• d.Share the opportunity with the partner best able to capture it✓

Sharing allocates ownership of an opportunity to a third party best able to capture its benefit, such as a partner with specialized capability. Avoidance and mitigation are threat strategies, and passive acceptance takes no action to realize the opportunity.

A project manager wants to reduce the risk of building the wrong product by delivering thin, end-to-end slices of functionality that stakeholders can evaluate. Which agile concept is this?

• a.Completing all backend work before any user-facing feature
• b.Prioritizing the least valuable items first
• c.Delivering vertical slices as small, valuable increments for early feedback✓
• d.Building the entire system before any demo

Delivering thin vertical slices of end-to-end functionality gives stakeholders working results to evaluate early, reducing the risk of building the wrong thing. Doing all backend first, waiting for the whole system, or prioritizing low value delays feedback and value.

At project closeout, the PM confirms deliverables are accepted, contracts are closed, and resources are released, but the sponsor asks what final step ensures benefits are tracked after the project ends. What should the PM address?

• a.Keep the full project team in place indefinitely after closeout so they can monitor benefits realization forever
• b.Transition ownership and the benefits realization plan to operations or the benefits owner✓
• c.Report only the final cost and stop there
• d.Immediately disband and forget the project

Because benefits often accrue after the project ends, closeout includes transitioning the product and benefits realization responsibility to operations or a designated benefits owner. Disbanding without transition, retaining the team indefinitely, or reporting only cost fails to ensure benefits are tracked and realized.

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.