Top 5 Requirements Review Techniques for Business Analysts

Requirements review techniques communicate, verify and validate requirements. Reviews can be conducted formally or informally. Typical review objectives are:

  • Remove defects
  • Check conformity to specifications or standards
  • Check completeness
  • Quality measurement
  • Reach a consensus on an approach or solution
  • Issue resolution
  • Alternative exploration
  • Education of reviewers

It is highly beneficial to communicate review objectives in advance to participants. 

Requirements Review Technique # 1 Inspection

Inspection is a formal technique that includes an overview of the requirements, individual review, logging of the defects, team consolidation of defects, and follow-up to ensure changes were made. The focus is to remove most of the defects and create a high-quality requirement. While usually performed by peers, it can also be used for stakeholder reviews by a business analyst. The inspection technique is the most formal technique and requires maximum effort.

Requirements Review Technique # 2 Formal Walkthrough

Formal Walkthrough (also known as Team Review) review technique is a formal technique that uses the individual review and team consolidation activities often seen in the inspection. Walkthroughs are used for peer reviews and for stakeholder reviews.

Requirements Review Technique # 3 Single Issue Review

Single Issue Review (also known as Technical Review) review technique is a formal review technique.  Single Issue Review is focused on either one issue or a standard in which reviewers perform a careful examination of the requirements. The focus of the review can be one specific aspect, such as the User Interface review.

Requirements Review Technique # 4 Informal Walkthrough

The informal Walkthrough review technique is an informal technique in which the business analyst runs through the requirements in its draft state and solicits feedback. Reviewers may do minimal preparation before the joint review session. The review comments are incorporated by the business analyst, and the requirements may be submitted for a formal review.

Requirements Review Technique # 5 Ad-hoc Review

The ad-hoc review technique is an informal technique in which a reviewer who has not been involved in the creation of the requirements provides verbal or written feedback. The ad-hoc technique is the most informal technique and requires the least effort.

The usefulness of Requirements Review Techniques

  • Promotes stakeholder discussions and involvement for quality output.
  • Identifies defects early.
  • Desk checks and pass-around reviews are convenient.

Limitations of Requirements Review Techniques

  • Rigorous team reviews can be time-consuming. 
  • Informal reviews are more practical but may not ensure the removal of significant defects.
  • Difficult to validate whether prior independent reviews in desk check and pass-around reviews.
  • This can lead to repeated revisions if changes are not carefully managed.
  • Sharing and discussing review comments over e-mail can elongate the approval process.

This blog written by Adaptive US. It is the World’s Go to Provider of IIBA Certifications Training and Study Aids. Get 100% Success or 100% Refund guarantee for all IIBA certifications Training.. We provide CBAP, CCBA, ECBA, AAC, CBDA, CCA, CPOA online, virtual and on-premise training, question banks, study guides, simulators, flashcards, audio-books, digital learning packs across the globe. For more Information, kindly visit our website:

Leave a Reply

Your email address will not be published. Required fields are marked *