On a treasury refunds roadmap, automated refunds depend on a working payments component. What release-planning action respects that dependency?
Select an answer to reveal the explanation.
Short Explanation
You can’t auto-refund money through a pipe that isn’t connected yet. Payments first, then automated refunds—same as laying plumbing before installing the faucet.
Full Explanation
Release and roadmap sequencing should honor technical and business dependencies. Automated refunds need a working payments foundation before they can succeed. Scheduling the dependent feature first, deleting the foundation, or delivering refunds alone invites failure. Payments before automated refunds is the sound order on the treasury roadmap.