PMP Exam Dumps : Project Management Professional (PMBOK 7th Version)

A sprint retrospective is a scrum event in which the team reflects on the past sprint and identifies areas for improvement and action items for the next sprint. A sprint retrospective helps the team to continuously improve, inspect and adapt, and grow as a team and as individuals. A sprint retrospective also provides a safe space for the team to communicate openly and honestly about the issues and conflicts they faced during the sprint, and to find ways to resolve them and prevent them from happening again. A sprint retrospective is not a performance evaluation or a blame game, but a constructive and collaborative way to increase the team’s motivation and engagement with the project. References:

What is a Sprint Retrospective? | Scrum.org

The Sprint Retrospective - What It Is & Tips for Making the Most of Your Meeting

In government-funded projects during political transitions, proactive stakeholder engagement is essential to maintain continuity. The project sponsor has the political influence and position to communicate with the incoming administration to highlight the project's progress, strategic value, and alignment with national/international goals.

According to the PMBOK® Guide – Seventh Edition, managing stakeholder relationships and ensuring continuous support is critical in such scenarios.

Option A delays progress unnecessarily.

Option C supports documentation but not continuity.

Option D is passive and ignores risk mitigation.

When expert estimates vary widely, the most effective technique is to facilitate structured consensus-building using a method like Planning Poker or a Delphi-style approach. Having SMEs reveal estimates simultaneously (A), discuss the assumptions behind the highest and lowest values, and then re-estimate reduces anchoring bias and surfaces hidden constraints or missing scope. This improves estimate quality by aligning understanding of work complexity, risks, and dependencies. Using historical information (C) is helpful, but it may not resolve differences if the current work is novel or if SMEs interpret the task differently; historical data should complement—not replace—assumption alignment. Recommending an iterative approach (B) is too vague and does not directly address divergence. Escalating to the sponsor (D) is inappropriate because estimate differences are a normal planning issue best resolved by facilitation and expert discussion, not escalation. Structured group estimation produces more reliable durations, supports buy-in from those doing the work, and strengthens the schedule baseline by making assumptions explicit and agreed.

==========