1. Informal Reviews
1.1. Conducted by author and selected set of reviewers
1.2. Participants go through the doc and suggest improvements
1.3. Author make notes and responsible for making the changes
1.4. Pros and Cons
1.4.1. Most commonly used & Fast & Effective
1.4.2. Metricts gathered rarely and contribution to process improvement is small
2. Walkthroughs
2.1. Author is leading the discussion
2.2. Author make notes and responsible for making the changes
2.3. Metrics are usually not tracked
3. Technical Reviews
3.1. Conducted by technically oriented reviewers
3.2. May include a moderator
4. Inspections
4.1. Most formal type of INTERNAL reviews
4.2. Reviewers must be prepared before
4.3. A moderator is running the review and present the work item
4.4. A scribe records the notes
4.5. A reader is involved sometimes
4.6. Reviewers may be assigned to a type of defect(e.g. security, performance) to look for
4.7. Metrics are mandatory
4.7.1. Number of defects found
4.7.2. Types of defects
4.7.3. Issues to be considered for process improvement
5. Management Reviews
5.1. Used to ...
5.1.1. Review the project or it's parts to assess the progress
5.1.2. Get the status
5.1.3. Verify deviations from plans
5.1.4. Review project risks and mitigation plans
5.2. Conducted ...
5.2.1. By or for managers that directly responsible for the project
5.2.2. In some cases, stakeholders or upper management
5.3. Produces a list of action items
6. Audits
6.1. The most formal of the review types
6.2. The least effective at finding defects
6.3. Conducted by independent group(external engagement) with lead auditor
6.4. Auditing team...
6.4.1. determines compliance with specified expectations
6.4.2. perform interviews, observation, exam available documents
6.5. result in...
6.5.1. recommendations for change
6.5.2. list of corrective actions
6.5.3. pass/fail assessment
7. Contractual Reviews
7.1. are associated with a particular contract milestone and conducted to verify adherence to the contract criteria
7.2. Include a management review
7.3. Involve managers, customers, and technical staff working on the project
7.4. Frequently used on large systems or safety-critical systems
8. Requirements Reviews
8.1. Provide one of the highest ROI
8.2. Maybe an informal walkthrough, a technical review, or a formal inspection
8.3. Participants should include all project stakeholders
9. Design Reviews (DR)
9.1. DR are usually technical reviews or formal inspections between peers
9.2. Customers and users may be included
9.3. Reviewers must have technical knowledge
10. Acceptance/Qualification Reviews
10.1. Used to obtain management approval for the system that has been or is still being developed
10.2. Conducted as management reviews or audit
11. Operational Readiness Review
11.1. Done prior to deployment
11.2. includes the review of operational procedures such as backups and other capabilities of the product
12. 6 Phases for Formal Review
12.1. 1. Planning
12.1.1. Training the reviewers
12.1.2. Getting management support
12.2. 2. Kick-off
12.2.1. Having the initial meeting
12.3. 3. Individual Preparation
12.3.1. Read the work product and prepare comments
12.4. 4. Review Meeting
12.4.1. Conducting actual meeting
12.5. 5. Rework
12.5.1. Changes should be made by author
12.6. 6. Follow-up
12.6.1. Re-review if required
12.6.2. Gathering suggestions for improvement