Sprint Planning initiates a sprint in Scrum. It is all about the 'Why', the 'What' and the 'How' for the sprint - the shared purpose that guides the Scrum teams' efforts.

If you found this episode useful, please don't forget to share it with others, thank you!

Sprints are the heartbeat of Scrum, driving continuous delivery and incremental progress towards a project's goals. They provide a structured framework for collaboration, adaptation, and improvement, empowering teams to deliver value in a timely and efficient manner.  

Sprints are not just about delivering features; they are about fostering a culture of collaboration, transparency, and continuous improvement. By embracing the principles of Scrum, teams can unlock their potential, achieve remarkable results, and deliver value that truly matters.

Sprint retrospectives are a mandatory event in Scrum and marks the end of the Sprint. It is the event for the Scrum team to conduct an internal inspection and adaptation in its quest for continuous improvement. In this episode, we talk about what retros are, how they can be run, common misconceptions and dysfunctions around them as well as some tips and tricks to make your retrospectives better.

Retrospectives can be as simple as a Lean Coffee event or as involved as you want it to be. So where will you take your next retrospective?

Scrum Guide - 2020-Scrum-Guide-US.pdf (scrumguides.org) Here's the link to the Esther Derby and Diane Larsen book - Agile Retrospectives – Making Good Teams Great (Pragmatic Programmers): Amazon.co.uk: Derby, Esther, Larsen, Diana, Schwaber, Ken: 9780977616640: Books