Opinions by someone who sees something for the first time are extremely helpful in creating "deliverables that are understood by anyone." If the review meetings are efficiently facilitated, this can bring the team's level up.
This workflow definition (process model) is simple, with no send-backs or loops. But it wasn't designed on the assumption that all created program codes will be reviewed. Rather, it assumes partial program codes that will be announced at the weekly team meeting. During the meetings, members can write into the "4. Meeting Comments" as a record of proceedings. Yes, chats can be effective whether online or offline.
One more thing... How about sending notification emails for prepared processes, so that people can write in comments before the meetings.
