What are the benefits of "MSF for Agile Software development"?

Question

Now I'm usually skeptical of Visual Studio goodies that come with the 'agile' brand name. So when I saw Agile for MSF in the process draft document I thought I'd take a look (which is coming to grips with the transition to agile. Its amazing... the speed of adoption of anything that comes signed 'Microsoft'. )

From a cursory glance, it looks like a bunch of workflow templates + some terms from UX Design (Personas) + IDE integration + management/'governance' reports. I didn't see much value added in proportion to the process overhead of entering all the workitems and misc information into the data repository..
But I could be wrong. Didn't spend much time doing a 'deep-dive'. So if someone is using this or evaluating this (without a bias), please share your findings..

• MSF for Agile Software Development Process Guidance download page
• MSF for Agile Software Development - Granville Miller

Answer 1

For what it's worth, the "MSF for Agile" doesn't have a very good reputation in the Agile community. See http://groups.yahoo.com/group/scrumdevelopment/message/16978 for example.

Answer 2

I actually know the guys who authored that, and we've talked about it before. The "benefit" if you will is that it comes with the TFS templates by default, and can be a good starting point for organizations who are floundering around. In general, when I worked with teams around TFS, we threw out both MSF for Agile and MSF for CMMI and instead did a map of their workstreams to find where they needed to improve. Then we looked at a variety of agile practices to help them in those areas.