Agile Austin - Peer Code Review An Agile Process

Peer Code Review: An Agile Process

Gregg Sporar Senior Product Manager [email_address] http://blog.smartbear.com http://twitter.com/smartbears

Code Collaborator codecollaborator.com

But is code review really Agile?

Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan The Manifesto

Working software is the primary measure of progress. Manifesto Principles - I

Getting to Working Software

Behaviors
Requirements
Design
Architecture

Behaviors
Coding

Professional Writers Have Editors

Spell Czech: Good, butt knot enough

ROI: The Experiment

Rule of Bug: Earlier == Cheaper What if we had Peer Review? ? ? ?

$152k, down from $368k 32, down from 194

Move the Feedback

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Manifesto Principles - II

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely . Manifesto Principles - II

Bus Number >= 2

Collective Code Ownership

Continuous attention to technical excellence and good design enhances agility. Manifesto Principles - III

The Ego Effect

Continuous Learning

Are the meetings necessary?

Can We Avoid:

Formal Inspections Michael Fagan, IBM, 1976

Fagan Phases = Meeting

Code review without meetings?

Adapt and Adjust

Over-the-Shoulder

Over-the-Shoulder Easy / Free Interruption No info Recorded Walk-through

Email Easy / Free No Interruption / Remote Conversation Tracking Info. Hard to Retrieve No End?

Pair Programming

Pair Programming No Tools or Workflow Deep Thought Big Time Commitment No Info. Recorded Too Close

Tool-Assisted Review

Reviewers Identify Changes Package/Deliver Organize Communication Track Defects Audit Trail Reports Automatic Metrics Hapless Developer Version Control

Tool-Assisted Review Collection Communication Chronicling Install and Maintain Time or Money

Tools Code Collaborator Commercial Crucible Commercial Review Board Open-Source Rietveld/Gerrit Open-Source

What’s the most efficient use of time?

Cisco® MeetingPlace® Case Study 3,200,000 lines of code 2,500 reviews 50 developers 10 months San Diego, Bangalore, Budapest s

CodeReviewBook.com

60-90 minutes max Time (minutes) Defects Found

Go slowly: 200-500 LOC/hour

Not too much: 200-400 LOC

http://blog.smartbear.com	477
http://www.slideshare.net	16
http://www.hanrss.com	1
https://securegateway.slb.com	1

Agile Austin - Peer Code Review An Agile Process

by gsporar on Jan 11, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

4 Embeds 495

Statistics

Agile Austin - Peer Code Review An Agile Process — Presentation Transcript