PMP · Question #1108
A project sponsor wants to develop software that would have 30 features and would be used in 10 different countries. The team feels overwhelmed with the amount of work to be done. What should the proj
The correct answer is A. Support the team to find and execute the minimum viable product (MVP).. When a project team feels overwhelmed by a large scope, the project manager should support them in identifying and executing a Minimum Viable Product (MVP).
Question
Options
- ASupport the team to find and execute the minimum viable product (MVP).
- BOrganize project execution to satisfy the project sponsor's request.
- CEncourage and motivate the team with project incentives.
- DSubdivide the team to handle different aspects of the project.
How the community answered
(45 responses)- A76% (34)
- B7% (3)
- C4% (2)
- D13% (6)
Why each option
When a project team feels overwhelmed by a large scope, the project manager should support them in identifying and executing a Minimum Viable Product (MVP).
When a project team is overwhelmed by a large scope, focusing on a Minimum Viable Product (MVP) is an effective agile strategy. The MVP approach involves delivering a core set of features that provide sufficient value to early customers, reducing the initial workload, managing team stress, and allowing for iterative development and feedback to inform subsequent feature development.
Simply organizing execution to satisfy the sponsor's large request without addressing the team's feeling of being overwhelmed will likely lead to burnout, missed deadlines, or quality issues.
While incentives can boost morale, they do not address the fundamental issue of an overwhelming scope; they are a temporary fix without solving the root cause of the team's stress.
Subdividing the team might distribute the work but doesn't reduce the overall workload or complexity of 30 features for 10 countries, and can introduce coordination overhead.
Concept tested: Minimum Viable Product (MVP) and scope prioritization
Source: https://www.pmi.org/learning/library/minimum-viable-product-agile-development-6479
Topics
Community Discussion
6A. When the team is overwhelmed and the scope is huge, the PM should help them focus on the MVP to deliver value incrementally. The other options either ignore the problem or just add pressure.
A is right. MVP lets the team focus on core features first, easing the overwhelm.
Agreed on A, but call it out for what it is: MVP is about validating assumptions and delivering incremental value early, not just making the team feel less overwhelmed.
A is the right call here because the team is overwhelmed and an MVP lets them deliver value incrementally instead of boiling the ocean. Has anyone seen an exam question where the sponsor pushes back on the MVP approach and insists on all 30 features up front, and how does that shift the answer?
A is correct per the agile mindset of delivering iteratively. D is the tempting trap here because splitting the team sounds like a quick fix, but subdividing an overwhelmed team just creates coordination overhead without reducing the actual scope.
Confirmed A on exam last week, and it maps directly to Agile Delivery Domain 3. The key here is the team feeling overwhelmed, which signals you need to descope to the MVP so they can deliver value incrementally rather than boiling the ocean. Use my exam trick: when a team feels swamped by a large scope, always look for the option that reduces or prioritizes the work, which is the MVP.