Your agile team is developing a mobile healthcare application in a regulated environment. During sprint planning for sprint 8, the product owner presents user stories for a new patient data-sharing feature. The team identifies that implementing this feature requires integrating with a legacy hospital system that has unreliable APIs and poor documentation. Past experience shows that such integrations typically reveal unknown dependencies mid-sprint. The product owner insists this feature is critical for a partnership announcement in four sprints and must begin now. The team is concerned about committing to a sprint goal they may not achieve. What approach best balances the business urgency with empirical process control?

Question

Accepted Answer

The correct answer is B. Breaking uncertain work into smaller stories with learning milestones maintains momentum toward the business goal while enabling adaptation based on emerging information (ECO Process Task 3.10: Build shared understanding). This approach honors the empirical principle of transparency and adaptation without delaying value delivery. Option A delays all value delivery by a full sprint when the partnership timeline is tight, and spikes should be time-boxed within sprints, not consume entire sprints. Option C undermines the sprint goal concept and doesn't address how to handle emerging uncertainties. Option D creates a parallel track that fragments team focus and violates the principle of sustainable pace and flow.

More Process Questions