A project manager is building a bridge. High-level project elements are managed predictively, while the software that retracts the bridge is developed using agile methods. During development, the workflow is frequently disrupted by delays and impediments caused by missing information. How should the project manager address this?

Making work visible with Kanban boards directly addresses the problem of disruptions and missing information. Kanban boards highlight bottlenecks and impediments in the workflow, allowing the project manager and team to identify where information is lacking or processes are stalled. This transparency enables proactive problem-solving and improved flow. Increasing retrospectives might help identify issues but doesn't inherently solve the visibility problem causing the delays. Breaking work into smaller batches is a good agile practice but doesn't directly address the cause of the disruptions (missing information). Applying lean manufacturing techniques to limit WIP is valuable for flow, but without visibility into why work is getting stuck, it won't resolve the core issue of missing information causing disruptions.