Milestone 3
In this milestone, you will be paired with another team. Your assignment is to inspect their code and identify early problems in their product and process. Follow your team's code review process to fill out the External Code Inspection. It is due Friday morning.
The goal of Friday's class is to exchange the results of our External Code Inspection. By the end of class, you will compile a list of problems the other team identified in your code, which you will discuss with your instructor on Friday.
Roles
(Based on: https://www.owasp.org/index.php/Steps_and_Roles)
Reviewees
Each of these roles will rotate as different code is inspected.
- Author: wrote the code being inspected.
- Reader: not the Author, informally walks through the Author's code.
- Scribe: takes notes in a Google Doc shared with his/her own team on problems the Review Team identifies.
Review Team
- Moderator: leads the review, keeping people focused on:
- Staying on task.
- Identifying problems, not solutions.
- Keeps the discussion egoless; rephrases attacks on the Author to focus on the code.
- Reviewer: everyone else on the Review Team. Identifies problems at the end of the Reader's walkthrough.
Agenda
5m: Setup Reviewees create a Google Doc and share it with themselves.
20m: Review For each file under review:
- Moderator announces the file in consideration.
- Reviewees select Reader and Scribe, who are not the Author.
- Reader walks through the code.
- After reading is finished, Reviewers state the problems they found in the code, using their notes on their External Code Inspection as a reference.
- Scribe records identified problems.
25m: Swap Stop the review and switch teams, repeating the Setup and Review steps.
Turn in instructions
Have one person on your team create a shareable link to your Google Doc in the "Everyone With The Link Can Comment" mode. Turn in the link in the box below.