An agile project is delivered to a client for a fixed price in cryptocurrency. Because of cryptocurrency volatility, both parties agree to adjust scope each iteration to the cryptocurrency value at the end of the iteration and stop the project when the agreed price is reached. Which approach should be used?

The correct answer is an iterative approach starting with the highest value epic. This scenario describes a fixed-price, variable-scope contract, which is best managed with an iterative approach. By starting with the highest-value epic, the project maximizes the delivered value early, ensuring that if the project stops prematurely due to cryptocurrency fluctuations, the client has received the most critical features. Iterative development allows for continuous adjustment of scope based on the remaining budget (cryptocurrency value) and delivered value. A flow-based approach (like Kanban) is good for continuous delivery but doesn't inherently prioritize value for fixed-price, variable-scope scenarios as effectively. A predictive approach is unsuitable for variable scope. An incremental approach with an MVP focuses on delivering usable increments but doesn't explicitly address the dynamic scope adjustment based on fluctuating budget in the same way an iterative, value-driven approach does.