A multi-team project switched from a predictive approach to agile per the product owner's request. Midway, a team discovered the necessary technical capability to meet a business requirement was missing, requiring rework that must be communicated to stakeholders. What should the agile project lead have done to prevent this?

The correct answer is assessing technical and organizational readiness and identifying risks at the start of the first iteration. In an agile environment, especially when transitioning from a predictive approach, it's crucial to proactively evaluate the team's capabilities and potential roadblocks. This includes technical readiness to ensure the team possesses the necessary skills and resources, and organizational readiness to confirm support and understanding of agile principles. Identifying risks early allows for mitigation strategies to be developed, preventing issues like the discovery of missing technical capabilities midway through a sprint, which leads to rework and stakeholder communication challenges. Asking the product owner to approve an external expert for acceptance criteria is not a preventative measure for technical capability gaps. Defining clear acceptance criteria during initiation is good practice but doesn't guarantee the team can meet them if the technical capability is absent. Increasing communication between a single team member and the product owner, while generally beneficial, wouldn't address a systemic lack of technical capability across the team.