Project Management Professional (PMP) — All Questions

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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