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
-