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 consensus on 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 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 requirements. While usually performed by peers, it can also be used for stakeholder reviews. Inspection technique is most formal technique and requires maximum effort. check more information about business analyst and Business analyst Interview Questions.

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 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 review can be one specific aspect such as User Interface review.

Requirements Review Technique # 4 Informal Walkthrough

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

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. Ad-hoc technique is most informal technique and requires least effort.

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 removal of significant defects.
• Difficult to validate whether prior independent review in desk check and pass around reviews.
• Can lead to repeated revisions if changes are not carefully managed.
• Sharing and discussing review comments over e-mail can elongate approval process.

About Adaptive US

Adaptive US is world’s Go to Provider of IIBA Certifications Training (CBAP, CCBA, ECBA, CBDA, AAC, CPOA, and CCA) and Study Aids. Get 100% Success or 100% Refund guarantee for all IIBA certifications Training. Adaptive US provided business analyst training, templates, tools for it’s clients throughout the world.