An organization is transitioning to agile and a project has been chosen as a pilot. The assigned project manager only has experience using predictive approaches, but the project manager is now required to use agile approaches with the help of an agile coach. During the retrospective of the fifth sprint, the project team complains that many obstacles exist with the organization that are creating project delays and rework. What should the project manager do in this situation?

While dedicating a sprint to address obstacles may seem like a focused approach, it could disrupt the regular flow of ongoing work and may not be feasible within the iterative nature of agile. This choice also risks isolating the issue rather than integrating it into the team's daily processes, which could lead to further delays.

Performing a root cause analysis is a valuable technique, but doing it during standup meetings may not be practical. Standups are designed for quick updates and immediate concerns rather than in-depth analysis. This option could lead to time-wasting discussions, detracting from the agile principle of focusing on delivering value quickly.

While discussing impediments during daily standups is important, simply including them does not promote the collaborative effort needed to resolve them effectively. This approach may lead to recognition of the issues but not actively engage the team in working together to eliminate them, which is crucial for fostering a proactive problem-solving culture.