Inspection and Adaptation within the Sprint

It’s the Sprint Goal which occurs at least every calendar month. Inspection and adaptation towards the goal occurs at least daily.

Try reading it as:

”Sprints enable predictability by ensuring inspection and adaptation of progress toward (a Sprint Goal at least every calendar month).”

Thanks, Ian. That's exactly how I thought it would be stated. I almost feel like the wording should be changed to prevent confusion. 

But anyway, thank you!

That's exactly how I thought it would be stated. I almost feel like the wording should be changed to prevent confusion. 

All due respect to you and Ian, phrasing of this sentence is not the problem; you're missing the context surrounding the sentence in question. Read this section again and pay attention to the context; pay close attention to the first 2 sentences. Per the Scrum Guide:

Sprints are limited to one calendar month. When a Sprint’s horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase. Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month. Sprints also limit risk to one calendar month of cost.

This section is reminding the reader that a sprint is no longer than 1 month so the sentence in question is simply stating that because of the max allowed time, inspection and adaption is sure to happen, at the very least, once a month. This is in contrast to other development methodologies that only inspect and adapt when it is warranted, which may be 4 or 5 months or longer.

Sure inspection and adaptation occurs in the Daily Scrum but depending on the team and the product, an in depth inspection and adaptation may not be necessary or beneficial. For those teams and/or products, the in depth inspection and adaptation happens in the Review and Retro.

It seems like the daily scrum would be an opportunity to inspect progress toward the sprint goal and adapt the upcoming work accordingly

Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something. - Scrum Guide

And the statement you had question about is referring to the Sprint Review meeting which should happen at least once a month as a Sprint cannot be longer than a month, therefore being an opportunity to inspect progress toward the sprint goal and adapt the upcoming work accordingly 

+ 1 Curtis !

That is exactly what the intended meaning of that statement is. Basically telling the advantage of timeboxing work into sprint goals of no more than month. That you are bound to inspect (and therefore adjust and adapt to do better) what has been developed for not more than a month before you move forward.

When you say at least doesn't it mean the minimum?



Shouldn't it have been at most every calendar month?

At least once per month, because you can have multiple Sprints in a month.



If your Sprint length is 1 week, you have 4 Sprint Goals per month.

In the current Scrum guide it states:

Sprints enable predictability by ensuring inspection and adaptation of progress toward a Product Goal at least every calendar month.

And not:

"Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month." 

The progress towards the Product goal is inspected at least every month(max sprint length)

The progress towards the sprint goals is inspected at least every day at the daily scrum