What if the vendor can’t get the bug fix in time? It may not be vital early on, but the thought process behind an exit strategy should exist, and simply become more refined the closer we come to the risk event, instead of scrambling to make one appear when it is clear we aren’t going to make it.
We’ve all been there. You work your butt off and you know your code is good, but you don’t know much about the database or the stability of the enterprise library you have to call. The app architects keep saying the interfaces aren’t going to change but … they’ve done nothing but change in the 4 weeks leading up to your launch. What is your exit strategy? It could be that your backup plan is to present a nice error message to the user rather than an ugly stack trace. Maybe you just disable that component or inform the user that the data is read-only for now.