A Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog (cit. Scrum Guide).
Have you clearly defined a Sprint Goal at the end of your Sprint Planning? Is this Sprint Goal understandable and transparent to everyone? Is it defined in a way that provides guidance and flexibility to the Development Team?
The aim of this article is to raise awareness on the importance of having a Sprint Goal defined and to provide some suggestions on how to create one.
A few days ago, I was observing a Sprint Retrospective. The Scrum Team decided to work on the Definition of Done (DoD), identified as the most important topic to adapt for the next Sprint. The discussions were open and animated, when an unexpected discussion emerged during the session.
In 2016 the Scrum Values were added to the Scrum Guide. In this article I share a workshop I run several times, with excellent feedbacks, hoping that you'll see value in reusing it in your working environment.
Over the centuries, humans have managed to adapt to many situations and evolve to become what we are today. History shows that we have an innate ability to adapt and evolve.
This remains valid as part of a change in business, such as the adoption of Scrum.