The correct answer is B - Chair a weekly team retrospective focusing on identifying areas for continuous improvement.
Retrospectives are a core Agile practice used to inspect and adapt the team's process, foster self- improvement, and enhance performance. If productivity is flat, the best approach is to collaboratively reflect with the team to uncover bottlenecks, identify areas for experimentation, and implement process adjustments.
PMI Agile Practice Guide:
"Retrospectives are a key feedback loop that allow the team to assess their performance and decide how to improve it. The retrospective is a cornerstone for continuous improvement and high-performing teams." (PMI Agile Practice Guide, Section 5.8 - Retrospectives) Mike Griffiths adds:
"Rather than externally imposed metrics, agile teams should drive performance improvements through retrospectives where they inspect their own work and collectively identify opportunities for efficiency." (PMI-ACP Exam Prep, Chapter 7 - Continuous Improvement) Incorrect options:
* A is diagnostic but insufficient for process improvement without team involvement.
* C introduces hierarchy and undermines team empowerment.
* D introduces extrinsic motivation, which may damage team collaboration and intrinsic ownership.

The correct answer is C - Asked to be relieved of project tasks to maintain team velocity.
Agile promotes transparency and accountability within teams. When a team member becomes unavailable due to competing priorities, it is their responsibility to inform the team so that work can be reallocated appropriately. This maintains the integrity of sprint commitments and avoids unplanned impacts on velocity.
From the PMI Agile Practice Guide:
"Team members are expected to proactively communicate capacity issues. Agile teams thrive when individuals are transparent about availability and workload, allowing adjustments to commitments." (PMI Agile Practice Guide, Section 4.1 - Agile Mindset and Team Behavior) Mike Griffiths states:
"If someone's availability changes, they must make that clear to the team. Holding on to tasks without capacity leads to velocity distortion and delivery issues." (Mike Griffiths, PMI-ACP Exam Prep Book, Chapter 4 - Team Performance) Why other options are incorrect:
* A attempts to do both initiatives, which may result in burnout or failed delivery.
* B focuses effort away from the agile team's responsibilities.
* D is unrealistic in cross-functional organizations where members may support multiple initiatives.

When a feature is too large to fit into a sprint, agile recommends decomposing it into smaller user stories or increments. According to the PMI Agile Practice Guide (Section 5.2: User Stories and MVPs) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning), teams should break down epics or large stories into Minimum Viable Product (MVP) segments and deliver value incrementally.
* Option A is correct: this enables the team to deliver value sooner and iteratively build on it.
* Option B delays addressing customer concerns.
* Option C sacrifices overall product balance.
* Option D violates time-boxing principles in Scrum and agile.

When comparing total scope (story points) and velocity, you can calculate the number of sprints each team expects:
* Team A: 420 / 30 = 14 sprints
* Team B: 280 / 20 = 14 sprints
Even though the story points are different, both teams estimate the same number of sprints, which means they estimate similar effort and duration relative to their own internal baselines. This aligns with the concept that story points are relative and not comparable across teams.
PMI Agile Practice Guide (Section 5.4: Velocity and Relative Estimation) and Mike Griffiths' PMI-ACP Exam Prep Book (Chapter 6: Adaptive Planning) explain that velocity is a team-specific measure and cannot be directly compared between teams.
* Option D is correct: both teams have estimated the same project size in their own context.
* Options A and B incorrectly compare velocity between teams.
* Option C is irrelevant; velocity is based on team experience, not technology assumptions.

In agile, the Product Owner is the ultimate decision-maker regarding backlog prioritization and scope changes. According to the PMI Agile Practice Guide (Section 5.1: Backlog Prioritization), any changes that affect value delivery, schedule, or scope should be discussed with the Product Owner, who evaluates the business impact.
Mike Griffiths in the PMI-ACP Exam Prep Book (Chapter 6: Value-Driven Delivery) reinforces that product direction and scope decisions must be handled through collaboration between the team and the Product Owner.
* Option D is correct: seeking Product Owner input ensures value-based decision-making and customer alignment.
* Option A (re-estimating the entire project) is unnecessary and burdensome.
* Option B rejects valuable input and ignores iterative flexibility.
* Option C goes against agile principles of focus and sustainable pace.