Author(s)

J.B. Iniesta

Abstract

A tool and a set of metrics to support technical reviews J.B. Iniesta ABSTRACT What is not measured is not controlled. What is not tracked is not done. If both adage are true, it is obvious that we need to measure and track the process of doing technical reviews of software projects. In this paper I intend to describe how we keep track and measure this process in our Company. We have found that a tool to support these activities is a necessity. INTRODUCTION In late 1.992 our Quality Group was instructed by Management to set up technical reviews in all the projects of our Division. At first 16 projects were planned to be reviewed. Since each project would generate at least 4 to 10 documents, and each document would be reviewed by some 4 to 6 people, it became obvious from the start that we had in our hands a big management problem. THE PROJECT DEVELOPMENT METHODOLOGY (MDP) In October 1.992 our Company adopted officially a methodology for software project development: Me

Keywords