Archive:Inconsistent metrics are meaningless - Revision history

wikademia>Wikademia: moved Inconsistent metrics are meaningless to Archive:Inconsistent metrics are meaningless

2009-04-26T22:38:42Z

moved Inconsistent metrics are meaningless to Archive:Inconsistent metrics are meaningless

← Older revision	Revision as of 22:38, 26 April 2009
(No difference)

wikademia>Wikademia: 3 revisions

2009-04-11T05:54:29Z

3 revisions

← Older revision	Revision as of 05:54, 11 April 2009
(No difference)

wikademia>Chungw: added category

2009-04-10T21:55:15Z

added category

← Older revision		Revision as of 21:55, 10 April 2009
Line 12:		Line 12:
	\| [[Charter for alignment\|Charter for Alignment]]		\| [[Charter for alignment\|Charter for Alignment]]
	\|}		\|}


			[[Category:(Anti-)Behaviors of business process management program governance]]

wikademia>Chungw: added navigation to parent charter

2009-04-10T19:04:24Z

added navigation to parent charter

← Older revision		Revision as of 19:04, 10 April 2009
Line 5:		Line 5:

	Before choosing metrics that determine what decisions and changes should be made, ensure that consistency is enforced. Software tooling is one way to enforce this if everyone uses the same tools, but tooling is only one part of the puzzle.		Before choosing metrics that determine what decisions and changes should be made, ensure that consistency is enforced. Software tooling is one way to enforce this if everyone uses the same tools, but tooling is only one part of the puzzle.


			== Applies to ==
			{\|
			\| [[Image:Alignment.gif\|left\|link=Charter for alignment]]
			\| [[Charter for alignment\|Charter for Alignment]]
			\|}

wikademia>Chungw: Initial behavior page

2009-04-10T16:08:49Z

Initial behavior page

New page

== Summary ==
The problem with inconsistent metrics is that it leads to comparisons that are useless. Teams cannot be compared with one another, and changes cannot be selected for implementation because the impact of those changes will be unknown.

One organization would compare product teams with what seemed like a single, common metric. Upon closer examination, it was determined that teams were measuring differently. The metric became meaningless for cross-team comparisons. Worse, the goal of trying to establish best practices from the better performing teams became impossible because it was unclear which teams were actually performing better.

Before choosing metrics that determine what decisions and changes should be made, ensure that consistency is enforced. Software tooling is one way to enforce this if everyone uses the same tools, but tooling is only one part of the puzzle.