Difference between revisions of "Metrics on and generated by CI"

From CitconWiki
Jump to: navigation, search
Line 11: Line 11:
 
can be useful to present metrics on big visible charts. also useful to aggregate information important to the team (e.g. bus times)
 
can be useful to present metrics on big visible charts. also useful to aggregate information important to the team (e.g. bus times)
 
http://www.panic.com/blog/2010/03/the-panic-status-board/
 
http://www.panic.com/blog/2010/03/the-panic-status-board/
 +
 +
[http://www.panopticode.org/ panopticode] and his [http://java-metrics.com/ blog]

Revision as of 11:58, 17 April 2010

If metrics are used to measure performance - people will perform to the metrics. trends matter much more than the current state.

number of unit tests - discussion when number goes down cyclomatic complexity - people that are very familiar with the code will notice outlayers - "why is that little thing so complicated?" code coverage - worthless. trend could be interesting crap4j - we like

the value of metrics is directly proportionate to how well the reader 'gets' the team and the project.

can be useful to present metrics on big visible charts. also useful to aggregate information important to the team (e.g. bus times) http://www.panic.com/blog/2010/03/the-panic-status-board/

panopticode and his blog