The modern equivalent would be resume-driven development. I've always found it somewhat ironic that CADT was originally used to describe the GNOME 1.x to 2.x s

The modern equivalent would be resume-driven development. I've always found it somewhat ironic that CADT was originally used to describe the GNOME 1.x to 2.x switch, when GNOME 2.x was for a long time quite stable (and which was stable over the KDE 3 -> 4 changeover period), and newer versions of GNOME have tended to have less backwards compatibility and more churn.