Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| ### Next Steps Bug Code Review |
| Prepare for Bug Code Review ( 3 : VER : 2 : 2.1 ) Developer
Activity: Prepare for Bug Code Review
Developer
|  |  |  | Build |  |  |  | Stabilize |  |
|  | Participating Roles Responsible: Developer Informed: Developer Solution Architect
### Overview Before a code review occurs, preparation work must be performed to ensure the code review involves the correct participants and is completed in a timely manner. The lead developer should organize the code review by identifying the reviewers, scheduling the code review, and sending out the code for review to all of the reviewers. # Entry Criteria Changed source code that is unit tested is ready for review. # Sub-Activities
1 | Identify Reviewers | Determine who will participate in the code review. The lead developer and architect responsible for the code area should participate in the review. All developers on the same team as the developer whose code is being reviewed should participate in the review.
2 | Schedule the Review | Schedule a review meeting with the reviewers. Provide sufficient time for each reviewer to read and understand the code before the meeting occurs. Plan the length of the review meeting to correspond to how much code must be reviewed.
3 | Circulate Code for Review | Send the code to each reviewer on the list so that they have a chance to see the code before participating in the review.
# Exit Criteria
| The list of reviewers is identified.
| The review is scheduled.
| The source code for the review has been delivered to the reviewers.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |