Transition plans generally look good on paper :-). But, it is usually very difficult to measure the success of a transition, especially when the program spans across multiple years, geographies and cultures. And, it becomes even more challenging in agile teams where the focus is on working software over comprehensive documentation.
While it’s essential to create a plan and follow it diligently, there are many nuances that makes a huge difference either ways (positive or negative) depends on whether the teams identifies and takes care of them or overlook them. My talk, based on an on-going program transition, would be focussed on many such nuances and how are we handling them.