An organization transitioning to agile assembled a new team. The project is struggling: team velocity varies widely and every sprint delivers less than committed. A new project lead with strong technical skills has been assigned. What should the project lead do?

The project is struggling with inconsistent velocity and under-delivery, indicating an issue with estimation accuracy. Recommending a different estimation technique during the retrospective is the most appropriate action. The retrospective is the ideal forum for the team to collaboratively identify process improvements, including how they estimate. A new technique, such as Planning Poker or Affinity Estimation, could lead to more accurate and consistent forecasts. Requiring estimates only from senior developers bypasses team collaboration and may not improve accuracy if the underlying estimation process is flawed. Allocating more time for estimation during sprint planning doesn't guarantee better estimates; the problem might be the technique itself, not the time spent. Reviewing and updating estimates in the daily standup is too late; the daily standup is for progress updates and impediment removal, not for re-estimating sprint work.