A flood-alert SMS service was planned with a phase-based WBS (requirements, build, test, launch). The team now wants adaptive delivery. What is an appropriate next step?
Select an answer to reveal the explanation.
Short Explanation
Phases stacked end-to-end are a waterfall cake; MVP slices let people taste frosting sooner. Pull usable alert value forward instead of waiting for the whole launch phase. That is WBS thinking remixed for adaptive delivery.
Full Explanation
Converting a phase-based WBS to adaptive work means slicing vertical, value-bearing increments—often framed as an MVP—rather than completing entire sequential phases before any release. Citizens get early usable capability and the team learns faster. Phases are not Scrum roles, and forbidding all increments until final launch undoes the adaptive shift.