Agile Artifact Review Process Description1. OverviewIn a peer review, co-workers of a person who created an artifact examine that product to identify defects and correct shortcomings. A review: verifies whether the work product correctly satisfies the specifications found in any predecessor work product, such as requirements or design documents identifies any deviation from standards suggests improvement opportunities to the author promotes the exchange of techniques and education of the participants.All interim and final development work products are candidates for review, including: requirements specifications user interface specifications and designs architecture, high-level design, and detailed designs and models source code test plans, designs, cases, and procedures software development plans, including project management plan, configuration management plan, and quality assurance plan 2. Agile Artifact Review ProceduresAgile Artifact Review is a lightweight review technique, in which artifacts are reviewed in detail by the reviewer. This technique is designed for a single reviewer, independent from author.ObjectiveTo identify defects as closely as possible to the point of occurrence in order to facilitate corrective action.Participants The author (or team leader) Reviewer (IV&Ver)Review Forms AgileArtifactReview_Form.xls: Concern Log and Problem List AgileArtifactReview_Form-FieldDesc.xlsEntry Criteria The author has stated his or her objectives for the review. The document has been spell-checked.Tasks Responsible1. Either distribute a physical or electronic copy of the work product to a reviewer, or simply notify a reviewer that work product is available. Author informs a reviewer that the artifact is ready to be reviewed. Author2. Either distributes a physical or electronic copy of the review form to a reviewer. (Only for first review) Team Leader/QM3. If necessary, author/team leader explains on document background, purpose, design rationale, etc. (i.e. a fast walkthrough) Author and Team Leader4. Obtains work product to be reviewed including review forms. Reviewer5. Examine the work product, to understand it, remain focused on finding defects and evaluate the work product. Either hand-write comments in Areas of Concern Log, or enter comments into the file. Deliver the Areas of Concern Log with comments to the author after completing the review. Reviewer6. Perform any necessary rework of the work product (including any other project artifacts affected by defects identified).Mark Area of Concern Log to indicate action taken.Record defects and resolve issues raised on Problem List. Author7. After finish rework, check in work product. AuthorDeliverables ? Modified work product? Filled Agile Artifact Review FormsVerification No verification of rework is required. The author is responsible for making appropriate decisions on issues and for correctly performing any rework.Exit Criteria ? The author has addressed all review issues raised.? The author has made any appropriate changes in the work product.