A project manager is responsible for building a bridge. The high-level elements of the project are handled using a predictive approach. The software responsible for retracting the bridge has been developed based on agile principles. During software development, the workflow is often interrupted by various delays or impediments due to lack of information.How should the project manager handle this situation?

While lean manufacturing focuses on eliminating waste and improving efficiency, it may not directly address the visibility of work and obstacles faced by the team. The project manager needs to prioritize creating transparency rather than solely limiting work, which could potentially lead to confusion about ongoing tasks and their statuses.

Increasing the frequency of retrospectives may help in reflecting on past performances and improving future processes, but it does not necessarily provide immediate solutions to the delays caused by lack of information. Retrospectives are more focused on learning and adjustment rather than addressing real-time workflow issues that need urgent attention.

Incorporating small batches of work can enhance agility and adaptability; however, it does not inherently improve the visibility of the workflow or the specific impediments being encountered. Without a clear view of the current status and challenges, simply breaking work into smaller pieces may not resolve the ongoing delays effectively.