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.
Reference:
Agile Practice Guide, Chapter 5: "Agile Product Development"
PMBOK Guide - Seventh Edition, Value Delivery System and Stakeholder Engagement
-

When a key executive expresses concerns about project success, especially regarding costs, the project manager must seek to understand the concern directly. A one-on-one meeting with the CFO enables the project manager to gather details, clarify any misunderstandings, and explore potential solutions or adjustments.
The PMBOK Guide - Seventh Edition highlights stakeholder engagement and communication as critical success factors. Engaging stakeholders individually promotes trust and effective issue resolution.
Option B is premature without understanding the specifics of the CFO's concern.
Option C is useful but may not address the CFO's immediate concerns.
Option D could come across as dismissive if concerns are not first acknowledged.
Reference:
PMBOK Guide - Seventh Edition, Stakeholder Performance Domain
PMI's Principles of Effective Stakeholder Communication
-

Probabilistic analysis is a technique that involves considering various possible scenarios and their associated probabilities to develop a budget that accounts for future uncertainties. This method is a common practice in project management to address the inherent risks and uncertainties in project budgets. It allows for a more comprehensive and realistic approach to budgeting, particularly in the face of uncertainties1.
Reference:
PMI's "A Guide to the Project Management Body of Knowledge (PMBOK Guide)"1

The project manager must take immediate action to address both behavioral and performance issues. Providing direct, constructive feedback to the underperforming senior technical member will help address their critical behavior and performance lapses. According to the PMBOK Guide - Seventh Edition, project managers are responsible for managing interpersonal conflicts and promoting team collaboration.
By addressing the disruptive behavior and lack of task performance, the project manager fosters a psychologically safe environment and restores team dynamics.
Option A avoids the issue and reduces collaboration.
Option B escalates prematurely and may cause greater disruption.
Option C is positive, but without addressing the root cause, the issue may persist.
Reference:
PMBOK Guide - Seventh Edition, Team Performance Domain
PMI Talent Triangle - Leadership: Conflict and Feedback Management
-

When a stakeholder raises a concern about quality, the project manager should first validate the claim against objective data, such as metrics or reports defined in the quality management plan. This ensures that decisions are evidence-based and aligned with documented quality criteria.
The PMBOK Guide - Seventh Edition emphasizes that decisions regarding deliverable compliance should be based on quality metrics and standards defined during planning.
Option A bypasses verification and may lead to unnecessary rework.
Option C assumes resolution requires funding without confirming the problem.
Option D relates to risk management and is not the first logical step.
Reference:
PMBOK Guide - Seventh Edition, Quality Performance Domain
PMI Practice Standard for Project Quality Management