In Agile frameworks such as Scrum, the Product Owner is responsible for maintaining and prioritizing the product backlog. If the team is unclear or in disagreement, the Project Manager (or Scrum Master) should facilitate a conversation between the team and the Product Owner to clarify the order based on business value and dependencies.
Per the Agile Practice Guide, backlog prioritization is a key responsibility of the Product Owner. This ensures the team is always working on the most valuable stories aligned with the project's strategic goals.
Option A forces a choice without validating the business priority.
Option C risks prioritizing ease over value.
Option D may help with team conflict but does not address prioritization directly.
References:
Agile Practice Guide, Section 3.1 - Product Owner Role
PMBOK Guide - Seventh Edition, Value Delivery System
-

When a risk such as country-wide power cuts materializes and impacts the project timeline, the project manager should first analyze the impact of the issue on the project's objectives, including scope, time, cost, and quality. After assessing the impact, a change request should be submitted to update the project schedule, reflecting the new timeline and any adjustments to the project plan. Additionally, the project manager should extend the project deadline accordingly and ensure that the project schedule is updated to reflect this delay.
This ensures that all stakeholders are aware of the changes and that the project plan remains accurate and up- to-date. It is also essential to log the risk in the risk register and collaborate with the risk owner to implement the planned mitigation actions, preventing further impact on the project123456789101112131415161718.
References:
PMP Risk Management Process - A Guide for 20241
PMI Global Megatrends 20222
Practice Standard for Project Risk Management3
Risk Response Plan in Project Management: Key Strategies & Tips4
Risk Management for Business Analysts (PMI-RMP/IIBA-ECBA)5
Plan Risk Responses | Project Management Professional (PMP)7
PMP Exam Strategies for Risk Response: Mitigate Risk, Avoid, or Transfer8 Risk Management Process for PMP9 Using a Project Schedule in Project Management10

The project manager should identify adequate change management tools to conduct the project, as this will help them to manage the changes to the product baseline in a flexible and efficient way. Change management tools are methods, techniques, or software that help to plan, execute, monitor, and control changes in a project. Some examples of change management tools are change request forms, change logs, configuration management systems, traceability matrices, and change impact analysis. By using these tools, the project manager can ensure that the changes are properly documented, evaluated, approved, implemented, and communicated. This will also help to minimize the risks and costs associated with the changes, and to maintain the quality and scope of the product. References:
* Change Request Form: Definition, Types, Process & Tools
* Change Log Template - Project Management Docs
* Configuration Management: What is it and why is it important?
* Traceability Matrix in Software Testing with Example Template
* Change Impact Analysis - an overview | ScienceDirect Topics

According to the PMBOK Guide, 6th edition, one of the key processes of the Project Stakeholder Management knowledge area is Identify Stakeholders, which involves identifying the people, groups, or organizations that could impact or be impacted by the project, and analyzing their expectations, interests, and influence. One of the outputs of this process is the stakeholder register, which contains information such as the identification, assessment, and classification of the project stakeholders. By reviewing the stakeholder register, the project manager can gain insight into the expectations of the specific client team member who is requesting trivial information, and understand the possible reasons behind their behavior, such as lack of trust, low engagement, or hidden agenda. This will help the project manager to plan and implement appropriate strategies to manage the stakeholder's expectations and requests, and avoid unnecessary conflicts or delays in the project. References: PMBOK Guide, 6th edition, pages 509-510, 515.