Release planning is the process of determining which features from the product backlog will be delivered in an upcoming release. The product backlog is an ordered, detailed list of all known requirements, features, and fixes for the product. Because it is prioritized and often contains estimated work items (like user stories), it serves as the direct and most "ready" input for selecting a coherent set of functionality to be developed and delivered as a single product increment. The team uses this prioritized list to forecast what can be accomplished within a release timeframe, aligning with the broader strategic goals outlined in the product roadmap.

A. A product idea is a nascent concept, far too high-level and unrefined to be used for detailed release planning.

C. A product roadmap is a strategic document showing major themes over time; it guides release planning but lacks the granular items needed for the plan itself.

D. A product vision is a long-term, aspirational goal that provides direction but is not a tactical tool for planning specific release content.

1. International Institute of Business Analysis (IIBA). (2017). Agile Extension to the BABOK® Guide (Version 2).

Section 6.5, Plan the Release: This section describes release planning as a high-level summary of features to be delivered. Figure 6.5.1, "Release Planning Inputs and Outputs," explicitly lists the "Prioritized Backlog" as a primary input to the "Plan the Release" process.

Section 4.1.2, The Product Backlog: "The product backlog is the master list of all the work that needs to be done to the product... It is the single source of requirements for any changes to be made to the product." This establishes it as the source from which releases are planned.

2. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org.

Product Backlog section (p. 11): "The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team." Release planning is fundamentally about selecting work from this single source for a future increment.

3. Pichler, R. (2010). Agile Product Management with Scrum: Creating Products that Customers Love. Addison-Wesley Professional.

Chapter 3, Working with the Product Backlog: The book explains that the product backlog is the primary artifact for release planning. It states, "The product backlog is the basis for release planning in Scrum... It contains all the features, bug fixes, and other work that needs to be done." (Paraphrased from concepts in the chapter).