One of the most common processes in any software development lifecycle is reviews, be it document reviews or code reviews. There are a few simple steps which can make meetings more effective as well as green. Here are a few such steps:
- The review object is sent across by author and a review invite is sent across at least 2 days prior to the actual review.
- In case, this is a complex object, the author gives a brief overview of what it is and what is accomplished.
- All reviewers review the object offline and note their comments either in the document itself or in a separate text document.
- For the above step all the reviewers can enter their comments in a single text document or each reviewer can have a separate document.
- On the day of the review, the author books a conference room. The author then shares the document on a laptop. No printouts or copies of the document are required.
- If the number of reviewers is more, the author will project the document on the projector.
- The reviewers would quickly collate the comments and go through the areas that need discussions.
- Finally, the moderator collates all the comments from the reviewers and finalizes the comments to be taken up.
- The author incorporates the review comments and releases the document after appropriate approval.
This way the meetings will not only be green, but also very effective.
- Reductions in paper usage as no printouts are taken.
- As all the reviewers come prepared with the comments, the meeting is very focused and effective.
- Moderator can explain the reasons for acceptance or rejection of comments, making things very clear to the team.