Top Down Infrastructure Reorganization

Existing large-scale CMS implementation provided obstacles in terms of cost for new deployments, usability, openness, scalability, and overall value. T-Mobile decided that they needed a more appropriate match for their environment and chose SR2. The first goal was to leverage their preferred common architecture and to remove the in-place CMS product which set the terms for its control over T-Mobile's architecture. Secondly, T-Mobile needed to separate their content lifecycle deployment from their code lifecycle deployment. As T-Mobile explored their options, they quickly realized that SR2 provided the best architectural paradigm for their success.