Which of the following is NOT a step in planning a delivery sprint?

Conducting a project retrospective is typically a step that occurs at the end of a sprint, rather than during the planning phase of a delivery sprint. A project retrospective focuses on reflecting on the past sprint—discussing what went well, what didn’t, and how processes can be improved in future sprints. During the planning phase, the focus is on determining the scope of the upcoming sprint, which includes adding new user stories, defining tasks for each story, and validating estimates for those stories.

In contrast, adding new user stories and tasks as needed is an integral part of sprint planning, where the team identifies requirements and organizes work for the upcoming sprint. Defining tasks for each user story ensures that the team has a clear plan of action to accomplish the user stories. Additionally, validating estimates for each user story is crucial in ensuring that the team is aligned on the scope of work and the time required to complete it, facilitating effective sprint execution.