Pete, I hear you, I really do. I know exactly what you are talking about. It is very hard to explain to mgrs how they would benefit from process integration, given they have never seen it at work. They would nod in agreement, but at the end of the day, I am afraid they do not comprehend what this is about.
Re. RTC. The reason I said RTC is a new paradigm, is that it's not just like any other higher end tool, say compare ClearCase (base + triggers) or UCM with PVCS Dimensions, SpectrumSCM, etc, as in you have integration between source and change. That is small stuff. RTC takes this at the higher level and provides full end-to-end integration starting with the project, going into releases, iterations, work items, team members and time allocated/spent on work items, integrated collaboration, source code control, build engine/builds and work items included, it's pretty much traceability throughout the project lifecycle. To add to that, you can also plugin in the Req & QA/Test Execution/Exit components into the mix as well. Installation of the hole thing is very lightweight, one script type deal, and all configuration and work-flow changes are done via supported interfaces in the RTC IDE. Currently it has 4 templates (scrum being one) which can also be extended/modified or you can build your own.
That was kind of long ;-((
-c
