Scott Downey has a lot of work on metrics and good information on his site. For productivity, the standard measure of velocity is a great one. Scott adds in another of work capacity that is very useful because you can then use the ratio of work capacity to velocity for more comparisons. One important thing to make sure you do here though is to ensure you set a "keystone" card so that your scale is anchored (a two is a two now and will still be a two in a year). If you don't set a keystone card that you always reference your scale can tend to drift.
The other items are much more difficult to measure. If you are calculating any sort of "value" measure on user stories, than tracking the amount of value delivered per sprint similar to velocity would be a good metric to ensure not only are you developing faster but you are developing the correct things.