Topic:

What information should be measured and tracked for agile software development projects?  Which stakeholders are interested in which sorts of information?  Which metrics are useful and which are just useless busywork?  How are different kinds of metrics used, and how can they be mis-used?  What happens when we measure the wrong things?

The use of several common agile metrics is covered, including story cycle time, velocity, running tested features, earned business value, cyclomatic complexity, various approaches to tracking defects, and fallacious or misleading metrics focusing on estimated and actual time.

About the Speaker:

An IT professional since 1977, Dave discovered Agile in 2002 and found it solved or alleviated many of the problems inherent in traditional IT.  Since then, he has been a dedicated practitioner and ardent proponent of change toward Agile and Lean thinking and practics.