Key Software Metrics Identified by Accenture

Introduction

This page categorizes, lists, and defines the software metrics that Accenture has identified as being the most useful for monitoring and controlling projects.

Note: This page has been populated with a few candidate categories and metrics to illustrate the formatting. Delete this sentence when you have added your actual content.

Size Metrics

Size metrics measure the magnitude of the product being developed in the project.

KLOC

A KLOC is one thousand lines of source code, excluding blank lines and comment-only lines. Maybe IEEE defines this?

Function Point

A Function Point is a measure of business functionality delivered to a user by an information system. It is defined by IFPUG, the International Function Point Users Group, and several ISO standards.

Story Point

A Story Point is a measure of the effort required to implement a user story in Scrum Agile projects. Story points are measured in units defined by the development team as a reflection of their own capability, or team velocity, and therefore should not be directly compared across teams. However, if an Agile team has a constant team velocity, the story points can be related to person-hours of effort

Schedule Metrics

Schedule metrics measure the duration of the project. Schedules are not unique to software projects, so definitions from [[http://pmi.org][PMI], the Project Management Institute, could be used.

Effort Metrics

Effort metrics measure the amount of labour expended in the project. Effort is not unique to software projects, so definitions from [[http://pmi.org][PMI], the Project Management Institute, could be used.

Quality Metrics

Quality metrics measure the characteristics of the defect injection and removal processes used in the project, the latent defects in the product being developed and its subsequent reliability.

Comments

Enter your comments here: