What is Review Efficiency

What is Review Efficiency?

How do we measure the performance of a Business Analyst? I am going to explain one of such metrics in this post. What is review efficiency?

Business Analysts conduct reviews on documents containing business analysis information like requirements. BABOK Version 3 discussed Reviews as a Technique.

What are Reviews?

Reviews are used to evaluate the content of a work product. The work product may be a package of several deliverables, a single deliverable, a portion of a deliverable, or work in process. Reviews can be formal or informal ,depending on the project and available time.

What is review efficiency?

Measuring the success of reviews is an important metric for a team. How do we measure the efficiency of reviews? Reviews are conducted throughout the lifecycle of the project.

Project teams conduct reviews on documents as well as code. By measuring and tracking this metric, the team can reduce the cost as well as effort in re-work.

The efficiency of reviews is measured relative to the number of defects found in the project. Efficient reviews reduce the number of defects in the project (which needs re-work).

Review efficiency for Requirements Specification document

It can be calculated by the following formula:

Requirements Review Efficiency (RRE) = Total number of review defects in requirements document / (Total number of review defects in requirements document + Total number of testing defects having source as requirements phase) x 100

Let’s take an example. A business analyst finds ten review defects while reviewing the requirements document. During unit/integration/system testing, the team found 200 defects.

Thirty of these defects were identified as being created during the requirements elicitation phase. So in this case,

RRE = (10/(10+30) * 100 = 25%

This means that 25% of the defects were reduced and no re-work was required to fix them.

The formula for calculating review efficiency for the entire project is:

Review Efficiency (RE) = Total number of review defects / (Total number of review defects + Total number of testing defects) x 100

RRE is one of the quantitative performance measures for Business Analysts. I will be discussing more business analysis topics in the coming posts.

Read Also: How do I differentiate myself from other Business Analysts?

About Techcanvass

Techcanvass offers IT certification courses for professionals. We are an IIBA endorsed education provider (EEP), iSQI ATP (for Certified Agile Business Analyst Training) as well as Agile Testing alliance partner for CP-SAT certification training in Selenium.

Techcanvass offers CBAP Course, CCBA Course, ECBA Course and Agile Analysis Certification (AAC) Course.

Abhishek Srivastava is a seasoned IT professional with diverse experience in Banking, Insurance, Utility and Education domains. Managing large accounts, Program management & Developing business solutions has been his forte.An NIT / IIM Kozhikode graduate, He founded Techcanvass (https://techcanvass.com) in 2013. With Techcanvass, He is pursuing his dream of creating an organization imparting quality education to IT professionals. He believes that learning is a lifelong journey and one must never stop learning.He also loves writing and sharing his knowledge. Some of his notable books are ERP to E2RP, UML Modelling for Business Analysts, Business Analysts Practitioners Guide, Software Testing: A practical Approach. All these books are available on Amazon.

2 comments

  1. I believe this is actually a measure of review effectiveness, not efficiency. Review *effectiveness* measures what fraction of the extant defects are detected by the review. Review *efficiency* measures the number of defects detected per hour of review effort, which then translates into the average cost of detecting a defect.

    Also, the denominator is incorrect for calculating total effectiveness because it doesn’t include the number of defects found by users (that is, how many defects leaked through the development process and into the released product).

    This is not a good metric for measuring BA performance: it’s a good metric for measuring how well your reviews work. You could have a high review effectiveness even if a BA created many defects, provided they were found during reviews. Metrics like this should *never* be used to evaluate the performance of individuals.

    Please see my book “Peer Reviews in Software” for more information.

    1. Hi Karl,
      Thanks for your inputs. Appreciate it. Semantically, what you say about effectiveness makes more sense. So review effectiveness may be more appropriate.

      However, as far as denominator is concerned, it is appropriate. In case of “Requirements Review Efficiency (RRE)”, the denominator is “(Total number of review defects in requirements document + Total number of testing defects having source as requirements phase)”. So the second part does not only take development team testing defects but any such exercise, including users. So the defect leakage, which you are mentioning is covered.

      I would definitely like to read your book some day, I really admire your writing and insights into many BA and testing related topics. I have also written a book on software testing – a practical approach, which is available on Amazon and by Prentice hall of India.

Leave a Reply

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