# **Peer Review (PR)** _(Approval of this Peer Review Procedure Document indicates a clear understanding of the purpose, scope, and content described herein. By signing this document, each stakeholder agrees to adhere to the defined peer review process, roles and responsibilities, review criteria, and documentation standards. Approval also confirms commitment to allocate necessary resources, conduct peer reviews as planned, and ensure compliance with organizational quality standards and project requirements.)_ **Document Revision History** | Version | Date | Change Information | Author | Approver | | ------- | ---- | ------------------ | ------ | -------- | | V1.0 | Feb 24, 2026 | Initial Draft | Melisha Dsouza | Pooja Thorat | ### **1. Introduction** The purpose of Peer Reviews is to detect and remove defects early in software work products, thereby improving quality and reducing rework costs. Peer Reviews also help team members develop a shared understanding of the work products and promote defect prevention practices. ### **2. Purpose, Goals, and Objective** Peer Reviews involve a methodical examination of software work products by peers to identify defects and areas where changes are needed. The specific products that will undergo a peer review are identified in the project's defined software process or project charter and scheduled as part of the software project planning activities. ### **3. Policies** The Peer Reviews schedule has to be shared with the stakeholders and everyone working on those work products. There is a privilege of performing a surprise Peer Review on the declared work product in the project charter, but that has to be initiated 2 hours before the scheduled time. ### **4. Work Product** The work product of the Enovate for Peer Reviews is, - **Review Schedule**: A schedule shall be prepared for reviews of all work products listed in the plan for Peer Reviews and should be shared with the stakeholders. - **Review Report**: The Review sheet shall have the work products mentioned and the information about the Peer Review performed, with action items and conclusions. Review report shall have the following reviews by default for all projects- * Requirement Review * Tesstcase Review * Code review * Milestone Review - **Checklist for Review:** A small checklist needs to be checked every time a peer review is performed to not miss anything. ### **5. References** | Process Elements | File Name or Reference | | ---------------- | ----------------------------------------------- | | Plan | Project Plan with the schedule of review | | Plan | Review Schedule | | Documents | Work products stated in the plan for Peer review | | Checklist | Review Checklist | ### **6. Roles and Responsibilities** | Roles | Responsibilities | | ------------------------------ | ---------------- | | Project Owner | • Should be clear with the work products to be reviewed, and also help in monitoring the reviews | | Business Analyst / Project Coordinator | • Communicates and resolves any communication gaps between the team for the reviews.<br>• Record MOM in Jira | | Team Leader | • To help the developer with critical technical issues and findings in review<br>• Ensure that the things required for the Peer review are in place as per the plan.<br>• Keep the PM informed of any changes required in the plan and any issues encountered by the team members. | | Project Manager | • Prepare review plan (Comes under detailed project plan)<br>• Performs the review assigned to him.<br>• Prepare mom and share with other stakeholders. | ### **7. Records of Peer Review** | Record | Where to get? | | -------------------------------- | -------------------------------------------------------------- | | Procedure Document | PR Process area in GitLab of the respective project | | Review Report | PR Process area in GitLab of the respective project | | Review Schedule | Process area in GitLab of the respective project | | Project plan with review plan | Plan the Process area in Gitlab of the respective project | | Review Findings | Jira in the respective project | | Review Checklist | PR Process area in Gitlab of the respective project | ### **8. Skills Required** Skills for Peer Review are much project-dependent for **DEVELOPER/TEAM LEAD/PROJECT MANAGER.** For the remaining roles, skills are listed below. | Roles | Skills | | ----------------------------------- | ------ | | Project Owner | • CMMI knowledge up to level 3<br>• Decision making capabilities<br>• Analytical skills | | Business Analyst / Project Coordinator | • CMMI knowledge up to level 3<br>• Excelled in creating reports based on findings<br>• Analytical skills<br>• Jira tool | ### **9. Verification and Validation** - Periodic reviews of the Peer reviews and work will be done by the BA and the Manager. - All managerial tasks and required information will be maintained in Jira. - This provides awareness of and insight into review activities at an appropriate level of abstraction and promptly. The time between the reviews should meet the needs of the organization. ### **10. Entry and Exit Criteria** | Category | Details | | --------------- | ------- | | Entry Criteria | Assigned Stakeholders<br>Review Plan<br>Work Products to be reviewed | | Exit Criteria | Review Schedule<br>Review sheet<br>Review Checklist | ### **11. Acronyms and Abbreviations** | Acronym/Term | Description/ Definition | | ------------ | ----------------------- | | PM | Project Manager | | PC | Project Coordinator | | BA | Business analyst | ### **15. Procedure Tailor According to the Project** Click the link → Copy the document → Move it to your project folder → Update as needed. Do not edit the original file. 🔗 [Document Link](https://docs.google.com/document/d/1E5VtWokNN8VcNkMkTaIuiCclJnNMzP5o/edit?usp=sharing&ouid=116180547719541291059&rtpof=true&sd=true)