During backlog refinement for a utility billing portal, the epic labeled ‘payments’ is still too large for one iteration. What should the team do?
Select an answer to reveal the explanation.
Short Explanation
An epic named ‘payments’ is like a grocery list that just says ‘food’—you can’t shop it in one trip. Refinement chops it into baggable stories: card pay, ACH, receipt email, and so on.
Full Explanation
Backlog refinement commonly decomposes large epics into smaller stories that fit planning horizons. Those smaller items can be ordered and delivered independently for incremental value. Hiding the epic, parking it only as risk, or freezing it as an undecomposed milestone undermines adaptive backlog management. Clear decomposition keeps payments work visible and plannable for the utility portal.