This is a nice paper that conceptually describes goals with metrics in the Agile software development. A very good starter reading. I like the concepts and the ideology, but what I lack in the paper is the depth of how to measure things.
Some aspects that come to my mind as and old "metric" guy are:
- How to define "change" in the cost of change metric? What is the difference between rework and change?
- How to define scrap and rework? How to measure those concepts in software development? Is the first feature that one develops to show proof-of-concept a waste - or is it a learning activity?
In short - nice article, but requires digging deeper into the context.