1 / 14

Adopting Code Reviews for Agile Software Development

Adopting Code Reviews for Agile Software Development. 2010 Agile Conference Mario Bernhart, Andreas Mauczka, Thomas Grechenig Presenter : 簡淯鈞. Outline. Introduction Code Review & Agile Software Development Code Review Process Code Review Tools Discussion & Future Work. Introduction.

zeal
Télécharger la présentation

Adopting Code Reviews for Agile Software Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Adopting Code Reviews for Agile Software Development 2010 Agile Conference Mario Bernhart, Andreas Mauczka, Thomas Grechenig Presenter : 簡淯鈞

  2. Outline • Introduction • Code Review & Agile Software Development • Code Review Process • Code Review Tools • Discussion & Future Work

  3. Introduction • Code Review • Benefits! • Defects? • When Do We review? • At the End of a Sprite… • Which is High Priority? • We need Review Method

  4. Code Review • Benefits & Defects • In Addition… • Social Effect on the Team • Collaboration • How We do it • pair programming • Differential-Reviewing • Automatic Scheduling • Etc.

  5. 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

  6. Code Review Process • Once a Week!? • Not at All • After Commit… • Scheduled Automatically • <author, reviewer, filter>

  7. 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

  8. Code Review Process • Process Coherence • The Time Between the Error Injection and Error Identification • Agile : Based on Feedbacks • Information Coherence • Traditional Review Methods : Modules or Components • The Proposed Review Method : Changes

  9. Code Review Tools • Code Review Tools • ReviewcCipse (RC) • Review Configuration • Scheduled Automatically • <author, reviewer, filter>

  10. Code Review Tools • Review Scheduling and Execution • Compare Editor • Rating : Passed, Warning, Failed • Integration With Issuetracker • Any Review Result May Create a Task…

  11. Discussion & Future Work • Shows Some Early Results • Needs Proper Evaluation • How about Performance? • Strongly Depends on the Review Scenario • Post-Commit? Pre-Commit? • Knowledge Sharing • Many Benefits!

  12. Thanks

More Related