Adopting Code Reviews for Agile Software

Development

2010 Agile ConferenceMario Bernhart, Andreas Mauczka, Thomas

GrechenigPresenter : 簡淯鈞

Outline

Introduction

Code Review & Agile Software Development

Code Review Process

Code Review Tools

Discussion & Future Work

Introduction

Code ReviewBenefits!

Defects?

When Do We review?At the End of a Sprite…

Which is High Priority?

We need Review Method

Code Review

Benefits & Defects

In Addition…Social Effect on the Team

Collaboration

How We do itpair programming

Differential-Reviewing

Automatic Scheduling

Etc.

Agile Software Development

Controversial?Pair Programming V.S. Peer-Review

Pair Programming V.S. Code Inspection Methods

Four ways to a Practical Code Review(http://www.methodsandtools.com/archive/archive.php?id=66)

Mix Together!But…

Heavyweight in Agile Processes

What We Want?Lightweight and Tool-Supported

Code Review Process

Once a Week!?Not at All

After Commit…Scheduled Automatically

<author, reviewer, filter>

Code Review Process

Following the Workflow…The Developer Commits to the SCM

Matches the Author and the Changed Items, the Review is Automatically Created

The Review is Executed and the Results areDocumented

The Review Result is Consumed by the Author

Create a Corrective Task for the Author

Code Review Process

Process CoherenceThe Time Between the Error Injection and Error Identification

Agile : Based on Feedbacks

Information CoherenceTraditional Review Methods : Modules or Components

The Proposed Review Method : Changes

Code Review Tools

Code Review ToolsReviewcCipse (RC)

Review ConfigurationScheduled Automatically

<author, reviewer, filter>

Code Review Tools

Review Scheduling and ExecutionCompare Editor

Rating : Passed, Warning, Failed

Integration With IssuetrackerAny Review Result May Create a Task…

Discussion & Future Work

Shows Some Early ResultsNeeds Proper Evaluation

How about Performance?Strongly Depends on the Review Scenario

Post-Commit? Pre-Commit?

Knowledge SharingMany Benefits!

Thanks