Scrum pushes the fact that devs are bad at estimating, and instead of providing methods to help with this process, it asserts that you should simply explain that any estimate will be wrong, so we’re just going to work on the most important stuff 1st, and then when the client runs out of money, we’ll stop. How can this compete against competitors who give a price up front? Is there any guidance on how to sell this?
Scrum > How to sell the fact that Scrum does not allow for any time or cost estimates?