Review process is intended to ensure the completeness and correctness of the work products. Merely performing reviews does not meet the full purpose. Reviews must be followed with

Proper correction

The defects need to be fixed and the completion status of reported defects needs to be logged properly. After rework the work product needs to be labelled suitably.

Verification by reviewers after correction

Reviewer needs to ensure the verification of the work product against the reported defects.


Root cause analysis of defects

Major or repetitive defects needs to be further analysed to determine the root causes.


Taking corrective actions on root causes of defects

Further to root cause analysis, action plans to prevent recurrences of the defects needs to be taken

Review Data Analysis

Review parameters like review speed, review effectiveness etc needs to be analysed and compared against the goal set for those parameters. Further actions needs to be deployed based on the analysis. For more information please refer the post on Review Data Analysis

Making Frequently Committed Defect List (FCDL)

FCDL can be made taking review feedback from the reviewer. And FCDL needs to be continuously updated after each round of review. The key is to learn from faults and consciously avoid repeating them.

Conducting Trainings

Trainings can be triggered to avoid repetition of defects or to improve the depth of review

Communicating the status to stakeholders

Finally, it is important to ensure that the status of review, rework, corrective actions etc. is communicated to all stakeholders.


Review is one of the methods for verifying an artefact. (Another method forverification of source code is unit testing). A proper review provides answers to all the ‘wh’ questions.(Refer 15 Points to be taken care during review of a work-product). In fact review itself can be defined using the ‘wh’ questions


Catching defects early reduces cost. Below 15 points explains the things to be taken care during review of a document.

  1. Ensure compliance w.r.t higher level documents. For example, If a design document is reviewed, ensure that all the user needs detailed in requirement document are addressed in the design document too
  2. Ensure spelling and grammar. It has got its own importance especially during translation from one language to another.
  3. Ensure that the document addresses an alternate way of

Reviews have been introduced based on Weinberg’s Concept of Egoless Programming Principle. According to this principle, independent teams are established to detect defects. All work products come under the scope of review. It is the responsibility of project manager to identify the work products for review and allocate sufficient time for review. In case 100% review is not feasible, the work products which need not be reviewed shall be identified in the project.

 Review process may vary based on the type of review as well as procedures /steps involved in the review. It has got 3 critical aspects. And it could be summarised as below