Is Agile Code Review an Oxymoron?

Guest Host and Moderator

Esther SchindlerEsther Schindler is the editorial director of Software Quality Connection. She has been writing about technology subjects since 1992, and has focused on software development topics for the last several years. You've read plenty of her articles, as her byline has appeared in CIO.com, ITWorld.com, Software Test & Performance, SD Times, Informit.com, ComputerWorld and DevSource.com. She is also a well-known chocoholic.

http://twitter.com/estherschindler

Guest Expert Speaker

Jack GanssleA popular speaker, Jack is the Technical Editor of Embedded Systems Programming magazine as well as author of the magazine's monthly column "Breakpoints". He has published over 600 articles on different aspects of embedded development, as well as six books on the subject. On-line, he writes the weekly Embedded Pulse column on embedded.com and is editor of The Embedded Muse, a free bi-weekly email newsletter.

www.ganssle.com

Jack’s Perspective on Agile and Code Review

Code reviews are essential for producing quality, maintainable, software. Some of the agile methods embrace reviews; others seem to discount them. As a passionate advocate of reviews, I feel any method- agile or otherwise - that doesn't demand reviews should be abandoned or modified.

Guest Expert SpeakerJared RichardsonJared Richardson has authored and coauthored a number of books, including the best selling Ship It! A Practical Guide to Successful Software Projects and Career 2.0: Take Control of Your Life. He’s a regular at software conferences and a thought leader in the Agile space. Jared works full-time as an internal coach at defense contractor Logos Technologies. He’s made a career out of helping teams find, and fix, their process blind spots. He lives in Morrisville, North Carolina with his wife and children where he recently, quite by accident, became a backyard chicken farmer.

Find Jared on the web at AgileArtisans.com

Jared’s Perspective on Agile and Code Review

Pair programming was a staple of XP, but it never worked that well for me. I also saw little value in large groups reviewing a single developers code. I settled on the peer code review as the best solution. When a developer finishes a feature (or fixing a bug), and before checking in their code, they would go find a co-worker who wasn't "deep" in another issue, and review the work. 

Guest Expert Speaker

Dave RooneyA veteran Agile Coach in Ottawa, ON, Canada with over 20 years industry experience, Dave is a Co-founder/Consultant with Westboro Systems. He’s been involved with Agile Software Development since 2000, helping private and public sector organizations from pre-funding startups to the Fortune 15 improve their software delivery process. He is an active writer, speaker and advocate of agile methods in Canada.

http://twitter.com/in/daverooneyca

Dave’s Perspective on Agile and Code Review

"I come to Agile from the Extreme Programming world, so my perspective is quite simple: at least two pairs of eyes must see every line of production code before it's committed to source control.  There are, however, a multitude of ways to accomplish that goal!"

What’s Different?

What’s different about code reviews when you’re doing agile?

Inspection Strategies

Do different types of software require different inspection strategies?

Agile Approaches

Agile approaches:  TDD vs. XP vs. FDD vs. SCRUM  (and is TDD a stand-alone practice or part of XP)?

What’s the worst example of code review that you’ve seen or heard about?

Things I learned the hard way. 

Questions?

http://smartbear.com/products