According to the PMBOK Guide, the communications management plan is a component of the project management plan that describes how project communications will be planned, structured, implemented, and monitored for effectiveness. It includes information such as the communication requirements, methods, formats, frequency, roles, and responsibilities of the project stakeholders. When a company's new communication system introduces online dashboard reporting, this is a change that affects the communication methods and formats of the project. Therefore, the project manager should update the communications management plan to reflect this change and ensure that the project communications are aligned with the new system and the stakeholder expectations. Updating the communications management plan will also help the project manager to identify and address any potential risks, issues, or challenges that may arise from the change, such as compatibility, security, or training needs. References: PMBOK Guide, Tools for managing projects : digital dashboards to report performance

The first step in managing stakeholder disagreement, especially regarding the use of new tools, is to investigate the reasons behind the disagreement. This involves understanding the perspectives and concerns of the stakeholders, which can reveal the underlying issues that need to be addressed. Seeking to understand before being understood is a principle that aligns with the PMBOK Guide's emphasis on stakeholder engagement as a key aspect of project management. By identifying the gaps and concerns, the project manager can work towards building consensus and finding a solution that aligns with the project's objectives and the stakeholders' needs. References: Overcoming Stakeholder Resistance Through Dialogue1, PMBOK Guide - Sixth Edition.

To define the MVP in an agile project, it's essential to identify the highest-value features and gather input from stakeholders. MVP refers to the smallest functional product that delivers value to users.
Option D (Conducting an information-gathering session) aligns with MVP development since the value delivered is the priority in Agile.
Option E (Referring to the stakeholder register) ensures that the right stakeholders are consulted to define what "minimum" means from their perspective.
Option A (Creating a WBS) is traditional/predictive and not suitable for MVP-focused, value-driven development.
Option B (RACI) is useful for role clarity but not directly relevant to defining an MVP.
Option C (Developing a PM Plan) is broader and not MVP-specific.
References:
Agile Practice Guide, Chapter 5: "Agile Product Development"
PMBOK Guide - Seventh Edition, Value Delivery System and Stakeholder Engagement
-

When a director demands the ability to make the final go/no-go decision about whether the systems go live, the project manager should schedule a meeting with the project sponsor to determine if it is appropriate to accept the director's request. The project sponsor is typically a senior executive in a corporation (often at or just below board level) who is responsible to the business for the success of the project. This meeting would help clarify roles and responsibilities, and ensure that the decision-making process aligns with the project's governance structure. References:
https://www.coursera.org/articles/project-management-lifecycle
https://www.projectmanager.com/blog/project-director-role

In project management, performing tasks in parallel, also known as fast-tracking, is a schedule compression technique used to shorten the project schedule without changing the project scope. It involves performing more activities concurrently or overlapping activities that were originally planned to be done in sequence.
This approach can help meet time-to-market needs by accelerating the project schedule. However, it may increase project risk and requires careful management.
: PMBOK Guide - Sixth Edition, Section 6.6.2, "Schedule Compression"