PMP · Question #549
A company is launching a new product that has to be ready before the summer season begins. After the discovery process, the team realizes that the requirements are very uncertain. What should the proj
The correct answer is C. Assist the team in proposing a minimum viable product (MVP).. When faced with a new product launch having uncertain requirements and a fixed deadline, the project manager should assist the team in proposing a Minimum Viable Product (MVP).
Question
Options
- AAsk to include some business subject matter experts (SMEs) in the team.
- BRegister a risk and define a contingency plan to finish the project on time.
- CAssist the team in proposing a minimum viable product (MVP).
- DInvite stakeholders to discuss project requirements prioritization.
How the community answered
(44 responses)- A2% (1)
- B5% (2)
- C82% (36)
- D11% (5)
Why each option
When faced with a new product launch having uncertain requirements and a fixed deadline, the project manager should assist the team in proposing a Minimum Viable Product (MVP).
While business SMEs can help clarify requirements, proposing an MVP is a strategic approach to navigate inherent uncertainty and deliver value efficiently within time constraints, beyond just clarifying details.
Registering a risk and defining a contingency plan is a reactive risk management technique; an MVP is a proactive strategy to address and mitigate the impact of requirements uncertainty.
An MVP approach is ideal for uncertain requirements and fixed deadlines because it focuses on delivering core functionality that provides maximum value early. This allows the team to gather validated learning, adapt to feedback, and iterate quickly, enabling faster market entry and managing uncertainty effectively.
Inviting stakeholders to discuss prioritization is part of backlog management, but it doesn't provide a strategic solution for building a product with highly uncertain requirements within a tight timeframe as effectively as an MVP does.
Concept tested: Agile product strategy (MVP)
Source: https://www.scaledagileframework.com/minimum-viable-product/
Topics
Community Discussion
8C is correct here. With uncertain requirements and a hard deadline before summer season, an MVP lets the team deliver something usable on time while continuing to refine, which is exactly how we handle product launches when the scope keeps shifting.
Yeah C is the right call, MVP fits the uncertain requirements angle perfectly, just make sure you connect it to the hard deadline in the stem too because that is the other half of why C beats the other options.
Leaned toward D first. Uncertain requirements plus a hard deadline equals MVP, pick C.
C is right. My senior always says uncertain requirements plus a hard deadline means MVP.
C is the exam answer but they also test MVP for validating assumptions with real users, not just hitting deadlines.
C. Saw this on exam last month, MVP handles uncertain requirements, not contingency.
D is the move here. When requirements are super uncertain but you have a hard deadline like summer season, you gotta get stakeholders in a room and prioritize so the team knows exactly what matters most before time runs out.
C is correct because the qualifier "uncertain" plus a fixed deadline points to iterative delivery, not a big upfront prioritization session where you commit to a frozen scope. D traps people because prioritizing sounds responsible, but it assumes you can nail down what matters most before you start, which contradicts the uncertainty in the stem.