PMI-ACP Practice Questions #102
You are a Product Owner for a new carpooling app, and you are working with stakeholders to prioritize features for the Minimum Viable Product (MVP). The stakeholders are evaluating three key features, each with its own balance of risk and value:
- Automated Ride Matching – This feature has high value as it allows users to find and book carpools based on their location and preferences. However, it also carries high technical risk due to the complexity of algorithms and API integrations.
- User Ratings & Reviews – This feature provides moderate value by improving trust between drivers and passengers. It carries low risk since it follows common rating mechanisms used in other applications.
- Payment Integration – This feature offers high value by enabling seamless in-app payments, reducing friction for users. However, it has moderate risk due to regulatory compliance, security concerns, and integration with payment gateways.
Which sequence should you prioritize these features in?
A. First implement User Ratings & Reviews, then Payment Integration, and finally Automated Ride Matching.
B. First implement Payment Integration, then User Ratings & Reviews, and finally Automated Ride Matching.
C. First implement Automated Ride Matching, then Payment Integration, and finally User Ratings & Reviews.
D. First implement Automated Ride Matching, then User Ratings & Reviews, and finally Payment Integration.
Analysis
The question requires prioritizing three features for a Minimum Viable Product (MVP) while balancing risk and value. The key principle in Agile prioritization is to address high-value, high-risk items first to mitigate uncertainty early, followed by high-value, low-risk items. Low-value items, even if low risk, should generally be deferred. Given this prioritization approach, the optimal sequence should start with the feature that provides the highest value while addressing significant technical risks, followed by a feature with high value but moderate risk, and finally, the feature with moderate value and low risk.
Analysis of Options:
A: First implement User Ratings & Reviews, then Payment Integration, and finally Automated Ride Matching.
This is not the best choice. User Ratings & Reviews, while beneficial, provide only moderate value and have low risk. Implementing this feature first does not align with Agile risk-value prioritization. High-risk, high-value features should be addressed earlier in the development cycle to validate feasibility and mitigate uncertainty. Deferring Automated Ride Matching, which is the most technically complex and valuable feature, increases project risk.
B: First implement Payment Integration, then User Ratings & Reviews, and finally Automated Ride Matching.
This sequence is also not ideal. Payment Integration is high-value but only carries moderate risk, meaning it can be implemented after addressing the highest-risk item. Implementing User Ratings & Reviews second, before tackling the most complex feature (Automated Ride Matching), does not align with Agile principles. Delaying Automated Ride Matching increases project risk and may cause integration challenges later.
C: First implement Automated Ride Matching, then Payment Integration, and finally User Ratings & Reviews.
This is the best option. Automated Ride Matching is both high-value and high-risk, making it the priority for early development. Addressing this feature first allows the team to validate the core functionality and manage technical uncertainties upfront. Once the highest-risk feature is stable, Payment Integration, which has high value but moderate risk, can be implemented next. Lastly, User Ratings & Reviews, which provide moderate value and carry low risk, can be developed towards the end, as it does not significantly impact core functionality.
D: First implement Automated Ride Matching, then User Ratings & Reviews, and finally Payment Integration.
While this option correctly prioritizes Automated Ride Matching first, it places User Ratings & Reviews before Payment Integration. Since Payment Integration provides higher value and has moderate risk, it should be addressed before a lower-value feature like User Ratings & Reviews. This sequencing is suboptimal.
Conclusion
The best answer is Option C, as it follows the risk-value prioritization approach. By tackling Automated Ride Matching first, the team mitigates major technical uncertainties early. Payment Integration follows as the next high-value feature with moderate risk, ensuring a smooth user experience. Finally, User Ratings & Reviews are implemented last, as they offer moderate value and carry minimal risk.
PMI – ACP Exam Content Outline Mapping
| Domain | Task |
| Product | Refine Product Backlog |
| Product | Manage Value Delivery |
Topics Covered:
- Prioritize features based on business value, risk, and feasibility to optimize early learning and value delivery.
- Ensure high-risk, high-value features are developed first to mitigate uncertainties early in the development cycle.
- Balance feature sequencing to maintain technical feasibility and business impact.
- Focus on delivering incremental value by addressing the most critical features first in the MVP.
- Align feature prioritization with customer needs, usability, and business impact while managing development risks.
- Optimize work sequencing to ensure that core functionality is validated early, reducing rework and integration issues.
If you’re preparing for the PMI Agile Certified Practitioner (PMI-ACP)® Exam, we highly recommend enrolling in our PMI-ACP® Exam Prep Program. Designed to provide a comprehensive Agile learning experience, this program not only helps you ace the PMI-ACP® exam but also enhances your Agile mindset, leadership skills, and ability to deliver value-driven projects. Ensure exam success and career growth with our expert-led, structured preparation program tailored for Agile professionals.
