One of the biggest mistakes teams make after a project review is filing the project review document away and never referring to it again. As we discussed, this is a mistake for organizations seeking to improve the efficiency and success for software development.
As each new project is begun, it is effective to review the recommendations from previous projects as a "self-check" for the new project. At various planned times throughout a newer project, it's effective to review the list of recommendations and evaluate as a group how the team is performing in those areas. Accountability makes time and effort of the project review more productive.