nerdexam
PMI

PMP · Question #773

A project manager is assigned to a new project that will launch the digital version of a current product. Even though the product is well known, the vision for its digital version is not clear to…

The correct answer is C. Work with the team on the definition of a minimum viable product (MVP) and present it to the. To clarify an unclear product vision and effectively increase value delivery, the project manager should collaborate with the team to define and present a Minimum Viable Product (MVP).

Submitted by haruto_sh· Apr 18, 2026Process

Question

A project manager is assigned to a new project that will launch the digital version of a current product. Even though the product is well known, the vision for its digital version is not clear to the stakeholders. What should the project manager do to increase value delivery?

Options

  • AGather the team to create a comprehensive product roadmap but only commit to requirements for
  • BCreate a visual task board with all of the relevant stakeholders to support backlog prioritization
  • CWork with the team on the definition of a minimum viable product (MVP) and present it to the
  • DUse spikes to dig deeper into the technical challenges of the new product, thus reducing the

How the community answered

(36 responses)
  • A
    11% (4)
  • B
    6% (2)
  • C
    81% (29)
  • D
    3% (1)

Why each option

To clarify an unclear product vision and effectively increase value delivery, the project manager should collaborate with the team to define and present a Minimum Viable Product (MVP).

AGather the team to create a comprehensive product roadmap but only commit to requirements for

Creating a comprehensive product roadmap without a clear product vision risks building the wrong features; the immediate need is to clarify the vision, not just plan out uncertain requirements.

BCreate a visual task board with all of the relevant stakeholders to support backlog prioritization

While a visual task board helps with backlog prioritization and transparency, it is a tool for managing work that has already been defined, not for clarifying an unclear product vision or defining the product itself.

CWork with the team on the definition of a minimum viable product (MVP) and present it to theCorrect

When the product vision is unclear, defining a Minimum Viable Product (MVP) allows the team to deliver the most essential value quickly, gather early feedback from stakeholders, and iteratively refine the product vision based on real-world usage and learning. This approach directly addresses the unclear vision by building something tangible and valuable.

DUse spikes to dig deeper into the technical challenges of the new product, thus reducing the

Using spikes focuses on resolving technical challenges, which is important for execution, but it does not directly address or clarify an an unclear product vision for stakeholders, which is a higher-level product definition issue.

Concept tested: Product vision and MVP definition

Source: https://www.pmi.org/pmbok-guide-standards/agile/agile-practice-guide

Topics

#Minimum Viable Product (MVP)#Value Delivery#Stakeholder Engagement#Agile Principles

Community Discussion

5
Yuki V.Yuki V.Apr 1, 2026

Confirmed C on exam last week. The key phrase here is the vision is not clear, which is exactly the scenario where defining a minimum viable product shines. An MVP gives stakeholders something tangible to react to, which aligns everyone on what actually delivers value without overcommitting to a full roadmap upfront. A is wrong because committing to a comprehensive roadmap when the vision is fuzzy is putting the cart before the horse, and D focuses on technical spikes when the real problem is stakeholder alignment, not technical uncertainty. My memory hook for this one was simple: unclear vision equals MVP, because you need a concrete

17
Anjali D.Anjali D.Mar 11, 2026

I first leaned toward B since a visual task board with stakeholders sounds collaborative, but the real issue here is an unclear vision, not task tracking. Switched to C because defining an MVP with the team and presenting it to stakeholders is exactly how you bring focus to a fuzzy vision and start delivering value fast.

5
Hiroshi T.Hiroshi T.Mar 19, 2026

Picked D first too. Re-read the stem: the problem is unclear vision, not technical uncertainty, so spikes solve the wrong problem. Option C is the agile answer for validating a fuzzy product vision with stakeholders, per the PMBOK Guide seventh edition section on delivering value iteratively. An MVP forces the conversation about what minimum scope actually delivers value, which is exactly what these stakeholders need to see. The other options either overcommit too early or skip the vision alignment step entirely.

5
Carlos M.Carlos M.Apr 15, 2026

Leaned toward A but the unclear vision screams MVP, pick C.

2
Yuki V.Yuki V.Apr 17, 2026

C is right but I would frame it as the unclear vision means you build small to learn fast, not just to deliver something, and that distinction showed up on my exam.

0
Full PMP Practice