Exam PMP topic 1 question 30 discussion

Option C is the most suitable choice in this scenario as it emphasizes value delivery through iterative development and stakeholder involvement. Creating an MVP helps the team stay focused on the most important aspects of the product, reduces the risk of building unnecessary features, and ensures that the initial version aligns with stakeholders' expectations.

I don't think an MVP can be determined until there is a Product Roadmap. PMI says: "Evolve vision. Product managers will work closely with stakeholders, and in the case of new products/solutions potential stakeholders, to understand their needs. The goal is to develop roadmaps for individual products, product lines, and for the business itself. These roadmaps describe the current vision for the near term, intermediate term (3-12 months), and long term (one year or more) with less detail the further out in time the roadmap goes. These roadmaps help the product managers to guide their prioritization decisions and provides input into the planning activities of other efforts (such as the Enterprise Architecture and Portfolio Management activities)." https://www.pmi.org/disciplined-agile/process/product-management/product-management-practices Thoughts?

MVP is Gold in PMP.

MVP provides tangible thing for decision.

MVP provides tangible thing for decision.

Le PMI recommande : « Faire évoluer la vision. Les chefs de produit travailleront en étroite collaboration avec les parties prenantes et, dans le cas de nouveaux produits/solutions, avec les parties prenantes potentielles, afin de comprendre leurs besoins.

MVP is the best way

In my opinion I think the best way for the stakeholders to better understand the overall value of the new digital product will be to Work with the team on the definition of a minimum viable product (MVP) and present it to the stakeholders

Since the vision for the digital version of the product is unclear, the best way to increase value delivery is to: Define a Minimum Viable Product (MVP) that focuses on delivering the core value of the digital product. Present the MVP to align stakeholders on a shared vision. Ensure early feedback, allowing iterative improvements. Defining an MVP helps focus on delivering essential features first, reducing uncertainty and improving alignment.

A. Gather the team to create a comprehensive product roadmap but only commit to requirements for the next quarter. (So this is saying the team works on the product roadmap now and then commit next quarter, and if the team is working on this for 3 months, nothing else gets done? The roadmap is suppose to be high level overview, does not make sense to me, C is my answer.

C: the vision is not clear, so working on a MVP can flush out value, requirements, test out assumptions etc. MVP can me many things clear that are not clear, so after they can test out and build and iterate in increments, then things will be clear, and a road make. Working with the team and stakeholders and getting everyone on board with the definition of value, can be accomplished with a MVP

C. Work with the team on the definition of a minimum viable product (MVP) and present it to the stakeholders

I voted C, creating MVP so the stakeholders can understand more the value of the product using MVP.

Option C is correct and not B, B is inline to Kanban , here they are talking about product and not the requirement Planning

I think the question is invalid. There is no answer relates to vision communication! Is it waste of time (or risky) to define an MVP with team while the stakeholder is still unclear about the vision? I think team's responsible is to implement MVP and stakeholders/clients should prioritize features and define MVP. What if the stakeholders don't agree with MVP suggested by team? If i have to choose, I'll chose B. Even B doesn't directly mention about vision communication, it's better than C. At least, the PM tried to visualize to support communication to help stakeholders in prioritizing features. Anyway, the question is how to ensure value delivery then it has to be done with prioritization.

La réponse est C &B

Reason - 1. Stakeholder is not aligned with vision for new product. There is no way stakeholders can undstand the value which product can deliver. So only best option is project manager as he already undstand about product and vision , it’s best for him to discuss with team and release MVP