The answer is B because there is no "Release Sprint" --> Release Sprint: Each sprint must result in a potentially releasable increment, regardless of the number of teams and deliverables involved in a release, so batch sizes of undelivered work can be minimized and controlled. A so-called Release Sprint would therefore be a contra-indication to agile practice.

B . There’s no release sprint, hardening sprint or integration sprint in scrum

B . There’s no release sprint, hardening sprint or integration sprint in scrum

B, all sprints have to be treated the same

Answer is B. There is no "release sprint"

A is correct

A properly functioning Scrum Team may not necessarily have a Release Sprint at all. The concept of a Release Sprint is not a core part of the Scrum framework as defined in the Scrum Guide. Scrum focuses on delivering potentially shippable increments at the end of each Sprint, meaning the product should be in a releasable state after every Sprint. The decision to release or not is a business decision rather than a framework requirement. Therefore, while a team may choose to have a Sprint focused on release activities (sometimes referred to as a Release Sprint), it is not a requirement for a Scrum Team to function properly.

B. False Scrum does not prescribe the use of a specific ceremony called a "Release Sprint."

There is no such thing as Release sprint n the 2020 Scrum Guide

B. False A properly functioning Scrum Team does not have Release Sprints. Scrum Teams work in Sprints, which are time-boxed periods during which they create a potentially shippable product Increment. While the product Increment may be released at the end of a Sprint if it meets the Definition of Done and provides value to stakeholders, there is no specific type of Sprint called a "Release Sprint" in the Scrum framework. Sprints are typically focused on producing increments of product functionality rather than releases.

No release sprint in SCRUM.

There is no such sprint as release sprint in Scrum.

B. Faux Dans le cadre de la méthodologie Scrum, il n'y a pas de concept de "Release Sprint". Un Sprint dans Scrum représente une période fixe (généralement de 2 à 4 semaines) au cours de laquelle une équipe Scrum travaille sur un ensemble de fonctionnalités ou d'objectifs spécifiques. À la fin de chaque Sprint, une incrémentation du produit potentiellement livrable est produite.

B. Dans le cadre de la méthodologie Scrum, il n'y a pas de notion de "Release Sprint" en tant que composant spécifique de la méthodologie. Un Sprint dans Scrum est un intervalle de temps fixe (généralement de 2 à 4 semaines) au cours duquel un travail défini est effectué et un incrément potentiellement livrable est produit.

There is not a Release Sprint

There is no "Release Sprint" in Scrum.

No such thing as "Release SPRINT"