A financial technology startup is using Kanban to manage development of their investment portfolio management application. The company's venture capital investors have indicated they expect to see significant user growth metrics within the next quarter to justify the next funding round. The product manager proposes prioritizing several features aimed at user acquisition and viral growth, even though current users have been requesting enhanced portfolio analytics and reporting capabilities. The development team notes that the growth features are technically simpler to implement than the analytics features. How should the team prioritize their work?

Question

Accepted Answer

The correct answer is C. Option C is correct because it addresses the business environment consideration of balancing multiple stakeholder needs while focusing on sustainable business outcomes (ECO Business Environment Task 1.5). Effective prioritization in agile requires understanding that investor metrics, user satisfaction, and product quality are interconnected—optimizing for one at the expense of others can create business risks. A balanced approach that considers the full business context leads to better long-term value. Option A is a common distractor because while investor requirements seem urgent and tied to company survival, prioritizing growth features for users who may not stay due to product deficiencies represents short-term thinking that can backfire—high acquisition with low retention creates poor unit economics and may actually concern investors who analyze cohort data. Business environment awareness includes understanding that sustainable growth requires both acquisition and retention, and that informed stakeholders value product-market fit over vanity metrics.

PMP Practice Question: Business Environment — Agile, Medium

More Business Environment Questions