CAPM Practice: Explain the components of an adaptive plan

A release plan takes a longer view, identifying which backlog items will be delivered in which release across several iterations. An iteration plan is more granular, committing to specific items for one iteration.

**Why not B:** Neither release plans nor iteration plans are categorically mandatory or optional in the abstract — their use depends on team practice and organizational context. Scrum requires sprint planning but does not mandate a formal multi-sprint release plan in every engagement; calling one mandatory and the other optional misrepresents both.

**Why not C:** In agile practice both plans are created collaboratively. Release planning typically involves the product owner, team, and key stakeholders working together; iteration planning is conducted by the whole team including developers. Assigning each plan to a different organizational stratum contradicts the cross-functional, self-organizing nature of agile teams.

**Why not D:** The distinction between release and iteration plans is about time horizon and granularity, not about budget versus scope. Both levels of planning address scope — which features and stories will be delivered; budget is managed at the portfolio or program level and is not the differentiating factor between these two plan types.