A city finance WBS includes a work package labeled "Payment gateway." The adaptive team breaks it into stories such as tokenize card, send receipt email, and support a refund path across upcoming iterations. What practice does that illustrate?
Select an answer to reveal the explanation.
Short Explanation
A WBS chunk is like a whole pizza; stories are the slices you can serve one at a time. Tokenize, receipt, refund—each can land in an iteration without waiting for the entire gateway. That is how plan-based decomposition feeds adaptive delivery.
Full Explanation
Teams often start from traditional decomposition such as a WBS and then slice work packages into backlog stories sized for iterative delivery. The payment-gateway example shows incremental value paths rather than one monolithic release. CAPM expects recognition of that WBS-to-adaptive translation, not discarding all decomposition or freezing every story as an immovable baseline milestone.