title: Giving estimates for large scale projects in an Agile Environment
body: <p>My firm just got its first large-scale development project inquiry and I would like to use an Agile process. The client has a vision for the application but openly admits to having very few requirements and recognizes that we will have to charge by the hour. Because of this, I've all but sold him on an Agile approach.</p>
  
  <p>The problem is that he wants a figure to budget around. I've read a number of articles that pretty much advocate against giving up an estimate because the client will budget for that number and even as requirements change, the number in their head and in the books doesn't.</p>
  
  <p>I've read there are a number of ways to factor in pricing in the contract, but almost all of them (save one) incorporate an up-front number. This just seems to violate the entire set of principles of Agile development.</p>
  
  <p>So my question is, if you're an Agile shop, how do you manage to circumvent this Catch-22 of Agile development?</p>