Thanks!
Marta

The quantification which you mention here is something totally different from what I was refering to - what you are talking about is the post-controlling phase of a project, i.e., the project is released and now we need to measure its value.
I agree with you, post-controlling is difficult, and I don’t have a definite answer for that one - because it depends on the project itself (i.e. boxed software vs online service, commercial vs defence software, etc.). Most probably would be senior management (or the product owner of the project in question) that needs to tell what are the parameters against which the success of the project should be measured. I am sorry for not being able to help you more with this one, and thanks for commenting :).

Arrived to your blog from Nathan’s one. Good entry.
Recently I was reading in another Agile Blog about velocity / productivity. In that blog somebody mentioned a sentence by Paul Hodgetts, Agile Coach and Certified Scrum Master:

“Velocity is more of a quantity of work completed metric. Useful and important, but not the sole measure of success. I think you would want a set of metrics that together help us understand our current capabilities to deliver as well as if those capabilities are changing from one point in time to another. I don’t believe there is one magic “agility number” to measure [productivity].”

You seem to take it one step further. More than productivity, it is important to concentrate on ROI or value. Agreed. You say that it is important not to focus on an abstract number, but measuring the value after releasing is sometimes even more difficult to quantify.
How do you suggest we can tackle this? at the end of the day, we need to “quantify” in one way or another, the results of the project. Even if it is to show senior management.

Thanks!
Marta