Effective code review during the development phase helps identify issues earlier and avoids rework and bug fixes during the later phases of the project. It is important for the project team to define the code review process and the guidelines for the project at the beginning of the development phase. The code review should not be limited to checking the naming conventions, indentation, and other best practices errors or warnings, which can be easily caught by best practice tools. The process should primarily be focused on achieving the following quality objectives:

• Solution approach: The code should be implemented in the correct way. If the existing business logic or processes have been modified, they should be modified at the appropriate level. The code should be aligned as per the technical design documents.
• Extensibility: The solution should be extensible and appropriate.
• Easy to read and follow: The code should be easy to read and follow.
• Error handling: The code should be able to handle errors appropriately. It's easier to catch such issues during the code review process compared to the testing phase.
• Education for the team: The code review process helps in educating the development team members with review feedback from more senior resources. It needs to be used as a training exercise. Set up a culture where the code reviews and feedback sharing become a learning experience rather than a blame game.