Sprint Planning Schedule

The formal Sprint Planning happens within the Sprint as the first event. If the planning starts before the Sprint Review it might miss out the opportunity to utilize some essential latest insights.

Because towards the end of previous Sprint, the participants of the Sprint Review come up with valuable input to subsequent Sprint Planning, by adapting the Product Backlog. A revised Product Backlog defines the probable Product Backlog items for the next Sprint.

However the scope of next Sprint is finalized only in the next Sprint Planning

So, Sprint Planning starts in current Sprint so the decisions can be deferred until they are needed and latest insights can be used to plan the next steps

Thanks Ali,

It seems clear now.

The next event after retrospective meeting of previous sprint and first event in a sprint is planning meeting. You can do the backlog refinement meetings in earlier sprints but planning for a sprint happens within the sprint.

Scrum Guide says "assess what it can accomplish over the *upcoming* (not current) Sprint." There is nothing in Guide which says Planning starts in current Sprint.

Although it borders on semantics, I think Greg is right...

The sequence of events is clear: planning after retro. Aslo, next sprint starts immediately after sprint ends.

But that does not define where sprint planning goes (first of new sprint, or final of previous sprint).

In my opinion, it also depends on how the events are organized agenda-wise. So if you end day X with retro, it could be logical to start day X+1 with planning is first event of the new sprint (or at least call it this way).

Also, at the very very first sprint, the first thing to do is plan. Ergo, the first event ever taken on by the team is planning, as start of the first sprint. Thus one can say that in essence every team starts with planning as first event of first sprint.

But, does it really matter? Because regardless of your very first sprint, over time, it makes no difference.