Adopting Code Reviews for Agile Software Development

14
Adopting Code Reviews for Agile Software Development 2010 Agile Conference Mario Bernhart, Andreas Mauczka, Thomas Grechenig Presenter : 簡簡簡

description

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. - PowerPoint PPT Presentation

Transcript of Adopting Code Reviews for Agile Software Development

Adopting Code Reviews for Agile SoftwareDevelopment

Adopting Code Reviews for Agile Software Development2010 Agile ConferenceMario Bernhart, Andreas Mauczka, Thomas GrechenigPresenter : OutlineIntroductionCode Review & Agile Software DevelopmentCode Review ProcessCode Review ToolsDiscussion & Future WorkIntroductionCode ReviewBenefits!Defects?When Do We review?At the End of a SpriteWhich is High Priority?We need Review Method

find bugs early in the development phase and to enforce coding standards, Performancetime-consuming and expensive, lack of time and resources, agile do not perform formal code reviews as a regular taskEspecially at the end of one sprint completing a development task is usually of higher priority than reviewing.a continuous inspection method and tool for agile software developmentreduce the review overhead and improve the developer acceptance of code inspections

3Code Review Benefits & DefectsIn AdditionSocial Effect on the TeamCollaborationHow We do itpair programmingDifferential-ReviewingAutomatic SchedulingEtc.

4Agile Software DevelopmentControversial?Pair Programming V.S. Peer-ReviewPair Programming V.S. Code Inspection MethodsFour ways to a Practical Code Review(http://www.methodsandtools.com/archive/archive.php?id=66)Mix Together!ButHeavyweight in Agile ProcessesWhat We Want?Lightweight and Tool-Supported

5

Code Review ProcessOnce a Week!?Not at AllAfter CommitScheduled Automatically

Code Review ProcessFollowing the WorkflowThe Developer Commits to the SCMMatches the Author and the Changed Items, the Review is Automatically CreatedThe Review is Executed and the Results areDocumentedThe Review Result is Consumed by the AuthorCreate a Corrective Task for the Author

Code Review ProcessProcess CoherenceThe Time Between the Error Injection and Error IdentificationAgile : Based on FeedbacksInformation CoherenceTraditional Review Methods : Modules or ComponentsThe Proposed Review Method : ChangesCode Review ToolsCode Review ToolsReviewcCipse (RC)

Review ConfigurationScheduled Automatically

Code Review ToolsReview Scheduling and ExecutionCompare EditorRating : Passed, Warning, Failed

Integration With IssuetrackerAny Review Result May Create a Task

Discussion & Future WorkShows Some Early ResultsNeeds Proper EvaluationHow about Performance?Strongly Depends on the Review ScenarioPost-Commit? Pre-Commit?Knowledge SharingMany Benefits!Thanks