Goodship Aces

Metric Tracking and Reporting

Metric	Usage
Estimated vs. Actual effort	Will help us refine our estimation precision. Can be used either at the project level or at greater levels of granularity (individual features)
Effort by Activity	Shows us where we're putting effort - analysis, design, documentation, testing, etc. - and how that changes over time. Helps us track our methodology.
Effort by feature/requirement	Assists us in planning increments, especially in the implementation plan. Gives us an idea of our team's productivity and how many features of the application we can promise to complete.
Effort by page of documentation	Useful when scheduling project artifacts and due dates. Easy to collect.
# of changed baseline requirements / # of baseline requirements	"Requirements churn"; a measure of how reliable our requirements are, and where to allow for change in our design.
Reported Defects / Time	Helps us measure product quality and how long the testing phase will last.
Fixed Defects / Time	Helps us measure product quality and how long the testing phase will last.

Measurement	Collection	Impact
Effort	Hours worked on spreadsheet	Required. Low; requires 5 minutes per day or so.
Effort by activity	Activity noted on spreadsheet as well	Low; spreadsheet will be open anyway.
Number of requirements	Count in SRS	None; information readily available.
Number of changed requirements	Date and number of changed requirements updated after each change	Low; requires discipline in tracking changes to requirements.
Use cases completed	Definition of explicit functional requirements in SRS	Medium; methodology may not necessarily support counting requirements or "features"
Number of defects	Defect status ("Open", "Closed", etc), date of status change.	Medium; requires use of defect tracking tool and discipline in reporting all defects through the tool.