Which of the following statements about Release Planning Session is/are Correct? A) Release Planning Sessions are conducted to develop a plan that…

Statements A and B accurately describe the purpose and outcome of a Release Planning Session within the Scrum framework. The session is designed to create a high-level, strategic plan that outlines the timeline for delivering increments of usable functionality to the customer (Statement A). This process provides the Scrum Team and stakeholders with a clear overview of the intended releases and the overall product delivery schedule, which is crucial for coordination and long-term forecasting (Statement B). These activities are central to aligning the development effort with the product vision and business objectives.

C) Whether the releases will follow a phased deployment pattern or a continuous deployment pattern depends on the stakeholder requirements.

This is an oversimplification. While stakeholder requirements are a primary input, the deployment strategy also depends on technical feasibility, organizational capabilities, and the Product Owner's strategic decisions.

D) Release Planning Sessions should produce a detailed Release Plan for the entire project.

This contradicts agile principles. Scrum emphasizes adaptive planning over predictive, detailed upfront plans. A Release Plan in Scrum is a high-level forecast, not a detailed, fixed schedule.

1. ScrumStudy SBOK® Guide

3rd Edition.

For A & B: Chapter 8

Section 8.2

"Plan and Estimate – Conduct Release Planning

" states that the objective of the Release Planning meeting is "to enable the Scrum Team to have an overview of the releases and delivery schedule for the product they are developing." It also clarifies that the output is a Release Plan which defines when sets of usable functionality will be delivered.

For D: Chapter 2

Section 2.4

"Scrum Principles - Empirical Process Control

" emphasizes that Scrum is an empirical framework that relies on transparency

inspection

and adaptation

which is contrary to creating a detailed upfront plan for an entire project.

2. Paasivaara

M.

& Lassenius

C. (2014). Agile Development and Release Planning. Aalto University

Department of Computer Science and Engineering.

For A & B: In Lecture 5

"Release Planning

" the purpose is defined as creating a high-level plan (or roadmap) that shows which features will be implemented in which release and when releases will be delivered. This supports the idea of providing an overview and a schedule for delivering functionality. (See slides on "Release Planning" and "Agile Release Train").

For D: The same lecture materials emphasize that agile release plans are not "big upfront plans" but are high-level and subject to change based on feedback and evolving priorities

directly refuting the notion of a detailed plan for the entire project.

3. Svahnberg

M.

Aurum

A.

& Wohlin

C. (2008). A systematic review on release planning in software development projects. Information and Software Technology

50(9-10)

947-962. https://doi.org/10.1016/j.infsof.2007.09.003

For C: This review (Section 4.1

"Constraints") identifies multiple constraints on release planning beyond just requirements

including budget

available resources

and technical dependencies. This supports the reasoning that the deployment pattern depends on more than just stakeholder requirements.