How often should progress toward a Sprint Goal be checked?
I found multiple references in the Scrum guide and I am confused.
Scrum Theory - Inspection
Scrum users must frequently inspect Scrum artifacts and PROGRESS TOWARD A SPRINT GOAL to detect undesirable variances. [Frequently]
The Sprint
Sprints enable predictability by ensuring inspection and adaptation of PROGRESS TOWARD A SPRINT GOAL at least every calendar month. [Monthly]
Daily Scrum
The Development Team uses the Daily Scrum to inspect PROGRESS TOWARD THE SPRINT GOAL and to inspect how progress is trending toward completing the work in the Spring Backlog. [Daily]
Therefore first the Scrum guide says progress toward a Spring Goal must be checked frequently and I find logical to maximize the opportunities to inspect and adapt. So in this context, DAILY would make sense. Then what exactly is meant when it says ... PROGRESS TOWARD A SPRINT GOAL at least every calendar month?
Then what exactly is meant when it says ... PROGRESS TOWARD A SPRINT GOAL at least every calendar month?
Sprints enable predictability by ensuring inspection and adaptation of PROGRESS TOWARD A SPRINT GOAL at least every calendar month.
It's a bit of a clumsy sentence, but I think it's not talking about the frequency of inspection and adaptation of the plan to achieve the Sprint Goal, rather, a team should (frequently/daily) inspect and adapt its progress towards a Sprint Goal, which is predicted to be achieved at least once every calendar month.
PROGRESS TOWARD A SPRINT GOAL at least every calendar month?
Remember that the Sprint Guide uses a one month sprint as the example time box. So in reality that is saying "PROGRESS TOWARD A SPRINT GOAL at least every sprint". Key words there are at least implying that is the absolute minimum. "Frequently" is pretty ambiguous so apply that as you will.
My preference is to coach the team to have the Sprint Goal in focus continuously and everything that they do should be in support of it. If at any point in the sprint one of them feels that the Spring Goal is in jeopardy it should trigger an immediate conversation with the rest of the Development Team. Based on the discussion it could result in a conversation with the entire Scrum Team.
As Alex pointed out, that's a tricky choice of words. The current structure of that sentence (Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month) creates confusions for many (myself included).
The takeaway is progress towards the Sprint Goal must be tracked frequently, rather daily than monthly. Thank you all for your feedback.
+ 1 Daniel Wilhite and Andrei Vrabie
add this to your statement Andrei
The takeaway is progress towards the Sprint Goal must be tracked frequently....+
Their inspection should not be so frequent that inspection gets in the way of the work. - Scrum Guide.
So,considering Daily scrum as the most frequent daily inspect and adapt ceremony, it is wise to do it at least once per day and not as frequent as to get in the way of the work.
What must be the frequency of inspection of scrum artifacts and progress towards Sprint Goal?
What must be the frequency of inspection of scrum artifacts and progress towards Sprint Goal?
The Scrum Guide says:
"The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work.
...
The Daily Scrum is not the only time Developers are allowed to adjust their plan. They often meet throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s work."
Bear in mind that the best way to inspect and adapt, in lean and agile practice, is as closely as possible to the time and place of work being carried out.