Scribd
Upload
46 views2 pages

Project Name Code Review Record: Schedule

This document is a code review record template for a company project. It includes sections for the review title, schedule, review team members and their roles/time spent, files and versions to be reviewed, and a table to document any issues found along with their proposed resolutions. The template will be used to facilitate code reviews and ensure all findings and their resolutions are properly tracked.

Uploaded by

anarki85
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
46 views2 pages

Project Name Code Review Record: Schedule

This document is a code review record template for a company project. It includes sections for the review title, schedule, review team members and their roles/time spent, files and versions to be reviewed, and a table to document any issues found along with their proposed resolutions. The template will be used to facilitate code reviews and ensure all findings and their resolutions are properly tracked.

Uploaded by

anarki85
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

COmpany

Project Name Code Review Record

Title
(add here a title for the review describing the feature to be reviewed)

Schedule
Event Date (dd-mmm-yyyy) Instructions

Review Author sends the review request to reviewers by email.


requested on:

Deadline for the Reviewers complete inspection logs and sends them to the
review author by email.
comments:

Consolidated Author consolidates individual logs into a single log and


log available: sends it to the participants by email.

Review team
Name Reviewer Role Scope Time Spent

Review scope
File(s) and version(s) to be reviewed

401130663.doc
Company Logo

Project Code Review Record

Item Reviewer Filename Line # Issue Resolution


1.
2.
3.
4.
5.
6.
7.
8.
9.
10.

Resolution codes: F – fixed, per resolution description; NC – no change; Dup – duplicate issue, the item number should be put to resolution
column; Bug – the finding will be resolved through the bug/defect process. The number of the Bug/Defect and database name should be put in
the resolution column.

You might also like