A "rebuild online permitting" epic is so large that neither Developers nor stakeholders can forecast the next valuable release. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
A boulder does not go through the door. You cut it into stones that still do something useful—submit one permit type, show one status—then you can actually forecast. Giant rebuild-everything epics just sit there looking important.
Full Explanation
Large items block forecasting and delay feedback. The Product Owner slices work into thinner items that still represent value, enabling inspection of outcomes rather than architectural layers. Horizontal layer splits often produce unreleasable inventory. A single go-live Gantt hides uncertainty instead of reducing it through increments.