Functional refinement The goal of the user story is clear The value for the end user is clear The user story has acceptance criteria, it is clear when it is done It is clear how the user story will be tested and verified during the development Dependencies with other work items, teams and/or external parties […]
Preparation The product backlog is sufficiently refined and up to date so that the work can be selected for the next sprint The entire team is invited for the meeting The agenda is determined up front and available for all attendees Stakeholders and/or domain experts are invited if needed The Product Owner has a desired
The retrospective contains setting the stage The retrospective contains gathering data The retrospective contains generating insights The team knows the difference between actions and intentions The retrospective results in one or two action items Action items are SMART The retrospective contains a closure The action items of the previous retrospective are updated The focus is
The team gives a recap of the sprint goal to set the context for the review meeting Completed work items are shown to the Product Owner (and stakeholders). New insights are discussed Optional: work in progress is shown to get early feedback The team evaluates if the sprint goal was achieved. Important observations are discussed
Every team member shares what he did yesterday that brought us closer to achieving the sprint goal Every team member shares what he will be working on today to bring us closer to achieving the sprint goal Every team member shares what is blocking, impeding, or taking him longer possibly preventing us to reach the
