What problems are likely to arise if formalized program inspections are introduced in a company where some software is developed using agile methods.

What will be an ideal response?

Formalized program inspections are time consuming as code has to be distributed
for review, studied by reviewers and then discussed in a review meeting. Because
of other commitments, this may take days or even a small number of weeks to
complete.
In a plan-based process, the time taken for inspections and reviews can be
taken into account when planning the project schedule and the activities in the
process should be organized so that the inspection does not delay progress on the
software as a whole.
However, in iterative, agile development, the code is being continually
changed so it makes no sense to stop development so that a review meeting can be
set up. It is important to maintain continuous development so that the planned
software increment includes the functionality that has been planned.
A further problem is that developers in an agile team may see the whole
process of inspections to be unnecessary bureaucracy and so may not wish to be
involved in the process.