In agile teams using Scrum, when do they generally develop high-level estimates required in Estimating practice 1.1?

High-level estimates in agile teams utilizing Scrum are typically developed during the backlog grooming and sprint planning steps. This phase is crucial as it allows the team to assess the work required for upcoming tasks and user stories. During backlog grooming, the team refines the backlog items to ensure that all requirements are clear, and potential complexities are considered. This process often involves discussions about scope and effort, leading to the establishment of high-level estimates.

During sprint planning, the team evaluates these estimates more closely with the aim of determining how much work can be realistically completed in the upcoming sprint. This collaboration ensures that everyone is aligned on expectations and the feasibility of completing the defined tasks within the sprint timeline. By engaging in this estimation process iteratively, Scrum teams can adapt their plans dynamically based on what they learn in earlier sprints, which is a fundamental principle of agility.

The other scenarios presented do not align with the typical processes in Scrum; high-level estimates are not developed during final reviews or daily stand-ups, as those are focused on assessing completed work and daily progress, respectively. Additionally, estimating at the end of a project would contradict the agile principle of iterative planning and frequent reassessment, hindering the team's ability to react to changes effectively throughout the development process.