Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint.
The timebox for this event is 3 hours for a 30 day Sprint. The timebox is shorter if the Sprint is shorter, e.g. 90 minutes hours for a 2-week Sprint.
The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done. Inspected elements often vary with the domain of work. Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved.
The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint.
The Sprint Retrospective concludes the Sprint.
Sprint Planning occurs immediately after the Retrospective.
How to use metrics to make improvements objective
Improve your team connectedness with this Retrospective pattern.
Help the team reflect on how to improve agile events, incl. the Daily Scrum
Stop Doing/Start Doing gets old quickly. Here are better patterns to use.
Define the rules of the team and its identity
1. Sutherland, J. and Schwaber, K. (2020). The Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game.