Loading ...
Sorry, an error occurred while loading the content.

Re: [CMMi Process Improvement] Review efficiency as a metric

Expand Messages
  • EDWARD F WELLER III
    Sunny Review effectiveness is a much better indication of the success of reviews - % of defects found - which means you have to colect all post inspection
    Message 1 of 4 , Jul 16, 2013
    • 0 Attachment
      Sunny
      Review effectiveness is a much better indication of the success of reviews - % of defects found - which means you have to colect all post inspection defect discoveries
       
      When you worry too much about efficiency (cost per defect found) in inspections) you are creating a "go faster" environment, which has been proven over 40 years to result in higher overall life cycle costs
       
      For definitions, etc, suggest you get Ron Radices book on inspections - it will also in detail explain the false value of efficiency compared to effectiveness
       
      Ed
       
      ----- Original Message -----
      Sent: Tuesday, July 16, 2013 4:01 AM
      Subject: [CMMi Process Improvement] Review efficiency as a metric

       

      Hi All,
       
      Could you please ellaborate on Review efficiency as a metric? How can we use in the organization? What is the formula for that? Can review efficiency use for Code review or document review?
       
      Please suggest.
       
      Thanks & Regards
      Sunny

    • yogesh verma
      Hi Sunny, Review effectiveness = No. of Pre-delivery defects detected (in a phase) / Total no. of pre-delivery defects for the project (across all phases) The
      Message 2 of 4 , Jul 22, 2013
      • 0 Attachment
        Hi Sunny,

        Review effectiveness = No. of Pre-delivery defects detected (in a phase) / Total no. of pre-delivery defects for the project (across all phases)

        The review effectiveness will tell you the effectiveness of review in the system e.g. in design phase if reviewer could detect 10 defects through review and in the later phases if you discover 10 more defects which are because design problems then the review effectiveness will be 50%.

        The higher the value of review effectiveness the better it is as it tell me that reviews are effective and discovering the defects at the right time. You can review effectiveness with your business goal by doing regression analysis.

        Thanks & Regards,
        Yogesh Verma
        (m) 9373251107


        From: EDWARD F WELLER III <edwardfwelleriii@...>
        To: cmmi_process_improvement@yahoogroups.com
        Sent: Wednesday, 17 July 2013 4:26 AM
        Subject: Re: [CMMi Process Improvement] Review efficiency as a metric

         
        Sunny
        Review effectiveness is a much better indication of the success of reviews - % of defects found - which means you have to colect all post inspection defect discoveries
         
        When you worry too much about efficiency (cost per defect found) in inspections) you are creating a "go faster" environment, which has been proven over 40 years to result in higher overall life cycle costs
         
        For definitions, etc, suggest you get Ron Radices book on inspections - it will also in detail explain the false value of efficiency compared to effectiveness
         
        Ed
         
        ----- Original Message -----
        Sent: Tuesday, July 16, 2013 4:01 AM
        Subject: [CMMi Process Improvement] Review efficiency as a metric

         
        Hi All,
         
        Could you please ellaborate on Review efficiency as a metric? How can we use in the organization? What is the formula for that? Can review efficiency use for Code review or document review?
         
        Please suggest.
         
        Thanks & Regards
        Sunny


      • Ebert, Christof
        Hi Sunny, Efficiency of a process, activity, or task is the ratio of resources actually consumed to resources expected or desired to be consumed in
        Message 3 of 4 , Jul 31, 2013
        • 0 Attachment

          Hi Sunny,

           

          Efficiency of a process, activity, or task is the ratio of resources actually consumed to resources expected or desired to be consumed in accomplishing this process, activity or task. As such efficiency means “doing things right.” An efficient behavior, like an effective behavior, delivers results—but keeps the necessary effort to a minimum.

          Effectiveness is about having impact. It is the relationship between achieved objectives to defined objectives. Effectiveness means “doing the right things.” Effectiveness looks only at whether defined objectives are reached—not at how they are reached.

           

          Review efficiency therefore relates the actual effort to detect defects in a review with the expected effort to detect these defects.

          The actual effort is all effort from preparing, conducting and finalizing the review, e.g. reading a document, using a checklist, recording defects, having a review meeting. It does not include effort from making corrections or project overheads. The expected effort is the planning baseline for doing these activities, based on a realistic baseline, from benchmarks or previous reviews. As an order of magnitude depending on code or document readability, one should find 0,3-1 critical defects per hour.

          Review effectiveness relates the amount of defects found to the totality of defects to be found, again both of comparable type and severity.

           

          A measurement baseline implies to comparing apples and apples. Often we see reviews that would report all type of “defects”, independent of severity and type. This is pointless for any forecasting and quality measurement. If you expect based on code size or document size a certain amount of prio 1 defects in a document, then you need to budget resources for detecting them, and you need to have the right processes to detect them. If the review later finds none of those, you need to question its effectiveness first. Often a code review can be substituted or at least made easier by using automatic approaches, such as static code analysis tools. Many companies today build a suite of such tools in front of the otherwise costly reviews. Note though that even tools have manual effort, such as analyzing the reports, and filtering the results.

           

          Concrete examples for such review efficiency both code and documents with lots of industry benchmarks are summarized in the book:

          Software Measurement. Springer, ISBN 9783540716488, Heidelberg, New York, 2007,

          http://www.amazon.com/gp/product/3540716483

           

          best regards

          -Christof Ebert

          http://www.vector.com/consulting

           

           

          From: cmmi_process_improvement@yahoogroups.com [mailto:cmmi_process_improvement@yahoogroups.com] On Behalf Of Sunny Mehta
          Sent: Tuesday, July 16, 2013 1:02 PM
          To: CMMI Group
          Subject: [CMMi Process Improvement] Review efficiency as a metric

           

           

          Hi All,

           

          Could you please ellaborate on Review efficiency as a metric? How can we use in the organization? What is the formula for that? Can review efficiency use for Code review or document review?

           

          Please suggest.

           

          Thanks & Regards

          Sunny

        Your message has been successfully submitted and would be delivered to recipients shortly.