Skip to main content

Roles and Responsibilities in a Review

In Review process there are different type of Role and Responsibilities in the process. Now we are describing following participants in the review process.

1. The Moderator : Moderator is the leader of the review process. Moderator also known as the Review Leader. The Moderator determine the review type, Review approach and the Review Team. The Moderator also scheduling the Review meeting, transfer the document to everyone within the review team before meeting, provide possible training for the other team members and lead the review meeting and collected the data that meeting get in the review meeting.

2. The Author : The Author is the writer of Document under review. His main work is to understand as much as possible the document and work to improve the quality of the document. Every part of teh document should be understandable for the document and Author understand sthe defect found in the document.

3. The Scribe : The Scribe also called recorder. As per his/her name his/her work to record every defects found during the review meeting and he/she also records any suggestion or feedback to improve the quality of the document.

4. The Reviewer : Reviewer also called the inspectors. His/her main work is to check the defects, suggestion and feedback that record by the recorder and check them to improve the quality as per the business perspective, Standards of the organization and the domain knowledge.

5. The Manager : He is the top level of management . His/her role is to execute the review, allocate time for the product and decide whether review process objective has been met or not.

Comments

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Ad-Hoc Testing

Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.