One thing I wish to add to the accepted answer, is that you shouldn't take the meaning of the word "Sprint" literally. You see from Thomas Owens' answer that it was a name attached to the way they structured they're work.
In a sprint in a sporting event, participants prepare for the sprint (e.g. warm-up), start the sprint when the signal is given, cover a ...
Jeff Sutherland, one of the creators of Scrum, provides an answer in his book Scrum: The Art of Doing Twice the Work in Half the Time:
And so my team embarked on what we called "Sprints". We called them that because the name evoked a quality of intensity. We were going to work all out for a short period of time and then stop to see where we were.
The sprint goal is typically a short missive you can communicate in business terms. For instance,
We want to deliver the customer profile page
If that takes 1 day or 2 weeks, mission accomplished. In fact, as a business, you would rather have it in one day than two weeks, wouldn't you?
The artifact of people must appear busy comes from an idea that ...
I think of the options you have listed you should choose #2
Change the Goal to be more encompassing
...even if that means the goal is more vague.
Let's face it: the sprint goal is always going to be some variation on "build value for the organization" anyways.
It sounds like the goal is getting in your way and I am going to guess that is hindering the ...
It is worth reminding yourself that the sprint goal is a solution to a problem.
Some teams may drift a little during a sprint if they do not have a clear focus and an understanding of the value the sprint delivers. The sprint goal helps teams to avoid this.
The question to ask yourself then is:
Given we do not have enough work to do for the Sprint Goal ...
The Sprint Goal is a focusing tool for the Development Team. It is not necessary for all work selected for a Sprint to be aligned with the Sprint Goal. In fact, I usually recommend that the Sprint Goal should be something that can be met through the completion of at most about 60-70% of the Product Backlog Items selected for the Sprint. If the Development ...
First, I think it should be stated that wierd stuff happens sometimes.if this was an odd circumstance that happened in one sprint, I'd shrug and move on. However, it sounds from your question that this is a frequent problem.
There are three likely causes (or a combination of them).
1) your view of the product is too short-sighted. Scrum is meant to be ...
Sprint Planning is the meeting in which the team plans the work to be performed in the sprint. For example, from the Scrum Guide:
Sprint Planning answers the following:
What can be delivered in the Increment resulting from the upcoming Sprint?
How will the work needed to deliver the Increment be achieved?
Just have a discussion around these ...