Bonus link: "The bad news is that a strong culture of 'managing dependencies' will hinder the implementation of the fundamental solutions" https://www.scrum.org/resources/blog/eliminate-dependencies-dont-manage-them
Good reason: Your MVP has generated new learning, that the core value in this product is smaller and more concentrated than you first thought. Congratulations, you just avoided wasted work on features that turn out not to be needed
wrote this thread up as a post on my blog https://blog.mattedgar.com/2021/05/28/code-is-cheap-ignorance-is-costly/
@mattedgar nothing. As long as you can keep the pace of delivery and iteration
Bad reason: There was never really a commitment to build the strategic solution. Congratulations, you've just dodged the pain of being dependent on vapourware, and can now move forward by making your MVP more sustainable