F.1 Scope. This appendix identifies a set of management indicators that might be used on a software development project. This appendix is not a mandatory part of this standard. The information provided is intended for guidance only.
F.2 Applicable documents. This section is not applicable to this appendix.
F.3 Candidate indicators. Given below is a set of candidate management indicators that might be used on a software development project. There is no intent to impose these indicators or to preclude others.
a. Requirements volatility: total number of requirements and requirement changes over time.
b. Software size: planned and actual number of units, lines of code, or other size measurement over time.
c. Software staffing: planned and actual staffing levels over time.
d. Software complexity: complexity of each software unit.
e. Software progress: planned and actual number of software units designed, implemented, unit tested, and integrated over time.
f. Problem/change report status: total number, number closed, number opened in the current reporting period, age, priority.
g. Build release content: planned and actual number of software units released in each build.
h. Computer hardware resource utilization: planned and actual use of computer hardware resources (such as processor capacity, memory capacity, input/output device capacity, auxiliary storage device capacity, and communications/network equipment capacity) over time.
I. Milestone performance: planned and actual dates of key project milestones.
j. Scrap/rework: amount of resources expended to replace or revise software products after they are placed under project-level or higher configuration control.
k. Effect of reuse: a breakout of each of the indicators above for reused versus new software products.