While a decent sized inconvenience, David likely has little choice than to accommodate the executives request this late in the project. This will affect a lot of areas of the project, such as testing, the supply chain, as well as research. With a new burger type, the team will have to re-do the topping research and testing phase since the flavor will be different, as well as securing a reliable vendor for the newly needed ingredients. In all honesty by changing the base patty this new burger item will have to essentially go through all of the steps the others have, starting from square one. I think the best plan of action to take care of this is to launch the current burger line-up as is and start a new project for this vegetable patty burger, simply because none of the already done parts of the project will really help or affect it. It's better to treat this as an entirely new entity rather than tack it onto the current project plan. As far as the avocado risk goes, there are a few things that can be done. Firstly, the vendor tells them that the fluctuations are only temporary and will be resolved, and the team could just trust them, although if they do and said issues don't resolve that would cause a huge problem down the line, so that might be a bad idea. The team could also look into changing vendors to a new one who offers a more stable product, in quality and price, while this would be the most idea choice it's not always an option because your company might have already signed a contract with the current company, meaning you are stuck with them. Lastly, I could recommend finding an alternative to avocados, and just cutting out the irregular part entirely. The staff have 3 burger prototypes ready to go, so choosing one that doesn't use avocados could be a good choice to bypass the issues altogether