Lack of Formal Reviews at work

Everyone feels under time pressure. It is a general misconception that following Agile Methodology in the project life cycle means that there should not be any documentation and they resist doing the same. The truth is that Agile always says that there can be a reasonable amount of documentation and not too many unwanted documents. For that matter, even the traditional models insist that everything towards the process and no document is unnecessary.

If a person creates unnecessary documents then it means that he has not understood processes rightly. If reviews do not happen then there is a risk that errors are hiding within the code or work that has been done. It is a tendency to blame it on time constraint especially when the project has a tough grueling deadline.

Having said that it is better to review the work product in any kind of software development methodology rather than doing rework many times which wastes a lot of time. If the work is not reviewed, the individual may think that he is on the right track. In order to ensure that the review takes place, we can get to the micro level of the past work done or current work being done and bring out the review defects and insist the team that it is important to follow these processes to ensure that we eliminate bugs. So this will help the team to realize the importance of review and the product has added quality.