This question already has an answer here:

Your client/user declares he has absolutely no intention of being available frequently throughout a project, just enough to say "I want the application to do this" and answer a few questions every month or so. Also, the idea of having to define priorities story by story makes him scream...

Yet, on all the projects you have worked on with them so far, they come up with changes all throughout development and expect these to be implemented in the final version.

Is it possible to use Agile methodologies in such a context? Can some parts of Agile still have value or do they all require frequent user involvement?

marked as duplicate by gnat, M. Dudley, user53019, user40980, Sklivvz Sep 10 '14 at 13:59

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 1
    see also: How to sell Agile development to (waterfall) clients – gnat Sep 10 '14 at 12:13
  • This project is going to make everyone miserable, so just part as friends. – JeffO Sep 10 '14 at 14:31
  • @JeffO: cannot part with an internal client :) – leokhorn Sep 10 '14 at 14:49
  • Go for bug driven development. Give the customer an hello world application. He will complain that it doesn't do what he wants. Tell him that it is a bug. Ask him what he expected. If you get a short answer, develop something small and deliver it to him. He will tell you again that this doesn't do what he wants. Tell him that it is a bug. Ask him what he expected. Develop this. ... This goes on and on until he finally sees that you cannot develop without having good specifications and input from the customer. – user99561 Sep 11 '14 at 8:21
  • @user99561: Kind of what's happening already. Except we're responsible for not guessing right and all the data malformed by the missing rules is sent back to us for manual fixing. Not much fun. – leokhorn Sep 11 '14 at 15:14