Focus is one of the scrum values and this choice really embraces that. Whilst the sprint goal is what the team should be aiming for each and every sprint it is not always going to 100% possible. Especially when teams are newly formed it can take a bit of time for them to truly understand capacity and happy path planning can take over. However, the framework is based on inspect and adapt with transparency so focus on what you can deliver and inspect and adapting is a great way to go forward. This approach has been taken in the past by Matt, a Scrum Master in a large finance organisation, and here is what he had to say about it:
The focus in the team is essential to the teams' success and having a shared and understood goal that really shapes that focus is an excellent precursor for success. In saying this, I have experienced teams when they newly form can be quite ambitious with the volume of work that they take in and this learning pattern is quite a good thing for them to experience early on. However, that is only if they learn from it. This was the case with a team I worked with early on in their formation and it really helped them grow. The retrospective really focussed on what they thought was possible along with what tripped them up and how we should allow for that buffer going forward, only every planning to 80% of the understood capacity. I'd love to say that they hit the sprint goal every time but that would not be true but now they knew that planning is great but plans need to be fluid, this helped their ability to be flexible and pivot when needed.
Lets look at some of the other options below
Gain 5 Points