Methodologies: Engineering, Product Design, Project Management

Formal Technical Reviews

Continuous Improvement, Design Review, Error Prevention, Process Improvement, Quality Assurance, Quality Control, Quality Management, Quality Management System (QMS), Software Testing

Formal Technical Reviews

Continuous Improvement, Design Review, Error Prevention, Process Improvement, Quality Assurance, Quality Control, Quality Management, Quality Management System (QMS), Software Testing

Objective:

A formal process for finding defects in software and documents.

How it’s used:

A structured peer review process with defined roles and procedures for finding defects in software artifacts like code, designs, and requirements. It aims to improve quality and find errors early in the development lifecycle.

Pros

Effective at finding defects early; Improves the quality of software products.

Cons

Can be time-consuming and require significant preparation; Requires trained participants.

Categories:

Engineering, Quality

Best for:

Reviewing critical software components or documents to ensure their quality and correctness.

Formal Technical Reviews find applications across various industries such as automotive, aerospace, software development, and healthcare, where the reliability and safety of systems are paramount. This methodology is particularly effective during the requirements analysis and design phases of software projects, serving as a disciplined approach for evaluating software artifacts. Teams typically consist of a moderator, authors of the artifacts under review, reviewers who are subject matter experts, and stakeholders who provide insights on requirements and expectations. Initiators of the review may include project managers or quality assurance leads who recognize the necessity of maintaining high-quality standards. The review process can be implemented iteratively throughout the development cycle, allowing for early detection of defects before the product moves into later stages, significantly reducing the cost and effort required to rectify issues later. Regularly scheduled reviews can also facilitate knowledge sharing among team members, helping to align the understanding of requirements and design across the group, thereby promoting consistency and coherence in the development effort. The discipline of Formal Technical Reviews can also support compliance with industry regulations and standards, making it a preferred strategy in sectors such as pharmaceuticals and defense, where documentation of quality processes is often mandated.

Key steps of this methodology

Conduct a pre-review meeting to outline objectives and roles.
Review the software artifacts individually to identify potential defects.
Group discussion of findings, focusing on defects discovered during the review.
Document defects and areas for improvement identified during the discussion.
Establish action items and assign responsibilities for addressing defects.
Ensure that all participants understand their roles in the follow-up process.

Pro Tips

Establish clear criteria for success to guide the review process, ensuring all participants understand the priorities and expectations.
Encourage diverse roles during reviews, such as technical leaders and non-technical stakeholders, to leverage varying perspectives for deeper analysis.
Integrate review outcomes into a continuous feedback loop, ensuring lessons learned are documented and inform subsequent development phases.

To read and compare several methodologies, we recommend the

> Extensive Methodologies Repository <
together with the 400+ other methodologies.

Your comments on this methodology or additional info are welcome on the comment section below ↓ , so as any engineering-related ideas or links.