Creativity is definitively not the point of Agile. Agile methods ( like SCRUM originally ) are all about minimising downtime ( i.e. time where the developer is not coding / analysing / doing his primary job ) while maintaining the project progressing toward the goal. If the goal is primarily the production of creative product, Agile does not fit. For example, I have never seen PoC, demo, explorations, ... developed using Agile.
It is weird that you mentioned quality. Although it is correct that Quality is orthogonal to Agile, I have never heard of any Agile implementation that did not focus on quality, generally adding stuff for XTreme programming or a focus on books like Clean Code, ...
OK so measuring quality is a problem on its own. For example TDD seems to be considered the incarnation of all evil nowadays, but it was all the rage back then. I think that would be unfair to retroactively say that the project I worked on did not put emphasis on quality simply because we used TDD and it is not so hot 9 years later.
Also, I'm talking about Agile early-days here, right after stuff like RUP and Prince2. Agile back then was a developer led initiative. So it was all about getting rid of daily annoyance that were keeping developer not coding and going off track (also, getting rid of the lies and BS). Since it was developer led, and developers don't really like to develop shit, most quality metric were self imposed and they used to work. Code Coverage for example is a wonderful tool for developers. It allows to pinpoint the place of the code where there is insufficient testing. Why would you not want that ? Well I guess, if that is used by your PHB, you probably don't want it. But again, saying that using quality metric is gimmick and not a focus on code quality is unfair when developer have chosen to use those metrics.
All of that is history. Nowadays, Agile is all about micro-management. In my company, CRMs and Consultant use Agile - I don't even what that fucking means and see no relationship whatsoever with what we did in development.
You noted that I said "did", because here is the funny thing. Since we were using proper agile, we get rid of everything that does not bring value, including Agile itself. We have had a long period of under-funding, low resource and inability to affect the delivery date, content or estimations. When the developer stop having that kind of control on the project, it ceases to be Agile - keeping the variety of meeting is just charade and a waste of time ( why would we spend time estimating the task if that estimation is not used to affect the delivery dates or expectations). We kept the daily scrum going until the team became too silo-ed and the majority stopped understanding what the other were saying.