PMP · Question #970
A project manager is leading a project in which the product requirements have not been fully met due to several uncertainties about customer acceptance. What should the project manager do?
The correct answer is B. Gather enough requirements to produce a minimum viable product (MVP) with which to evaluate. When product requirements are uncertain due to customer acceptance, the project manager should aim to gather enough requirements to build a Minimum Viable Product (MVP) to evaluate with customers and reduce uncertainty.
Question
A project manager is leading a project in which the product requirements have not been fully met due to several uncertainties about customer acceptance. What should the project manager do?
Options
- AGather a reduced number of approved requirements and add some extra features to fulfill the
- BGather enough requirements to produce a minimum viable product (MVP) with which to evaluate
- CStop all project activities until all requirements are set up front by the project sponsor and the key
- DAsk team members to research and collect data about the best features offered by similar
How the community answered
(23 responses)- A4% (1)
- B74% (17)
- C13% (3)
- D9% (2)
Why each option
When product requirements are uncertain due to customer acceptance, the project manager should aim to gather enough requirements to build a Minimum Viable Product (MVP) to evaluate with customers and reduce uncertainty.
Adding "extra features" when requirements are uncertain is counterproductive and increases risk; the focus should be on validating core functionality, not expanding scope.
Building a Minimum Viable Product (MVP) is an agile strategy specifically designed to address requirement uncertainties and customer acceptance issues by delivering core functionality quickly for early feedback and validation.
Stopping all project activities until all requirements are fully defined is a waterfall approach that is unsuitable for situations with high uncertainty about customer acceptance and can lead to significant delays.
While market research can be helpful, it doesn't directly address the *project's* specific customer acceptance uncertainties for *its* product; direct customer feedback on a tangible product (MVP) is more effective.
Concept tested: Agile product development, minimum viable product (MVP)
Source: https://learn.microsoft.com/en-us/azure/devops/boards/get-started/what-is-an-epic-feature-story?view=azure-devops#mvp-minimal-viable-product
Topics
Community Discussion
5
Yuki V.Feb 5, 2026Confirmed B on my exam last month. When customer acceptance is uncertain, the MVP approach lets you put something tangible in front of them and gather real feedback instead of guessing at requirements upfront.
Mateus R.Feb 4, 2026I first leaned toward D, thinking research might resolve the uncertainty, but that just delays decisions without validating anything with the customer. The key phrase is "uncertainties about customer acceptance," which points straight to building a minimum viable product so you can get real feedback early. Think of it like a chef letting someone taste a small sample before cooking the whole meal, rather than guessing what they want and hoping for the best. B is the agile-aligned answer because it embraces uncertainty through iteration rather than trying to eliminate it upfront.
Ola B.Feb 17, 2026B is the right call here because when customer acceptance is uncertain you build an MVP and let real feedback settle it. I always tell folks to spin up a quick sandbox and ship a barebones version so you can see how stakeholders react, that is the fastest way to cut through requirement ambiguity. One thing I am still curious about though, how does this MVP approach square with strict predictive contracts where the customer expects every requirement delivered up front?
Bao N.Feb 22, 2026D. Researching competitors de-risks acceptance before you commit to requirements.
Mateus R.Feb 24, 2026B is the right call here. Think of it like shopping for a used car: you kick the tires and take it for a spin before you hand over the cash, which is exactly what a feasibility study does for a project, evaluating technical and economic viability before you commit. D sounds appealing but researching competitors is market analysis, not the same as proving your own proposed solution can actually fly.