Hm. I don't think it does. As it suggests a goal or set of goals--not how to achieve them.

But even if it could be formalised into something approaching a process or best practice, I would still rail against its imposition, despite being the one who suggested it. Especially on existing, productive teams that currently use other methods.

Any methodology is better than no methodology. And, at their best, all methodologies--waterfall, TDD, RAD, Use cases, SSADM et al--all have their merits when applied properly to particular projects. The problems arise when a methodology is seen to be successful for one project and is mandated for all subsequent projects without recourse to logic and common sense on the ground. Once formalised, and without the considered application of human intelligence on a case by case basis, they can become millstones around the necks of the people to whom they are mandated.