It isn't clear if you asking a technical question or a social question. For the latter the usual problems are visibility and acknowledgement. Visibility means

It isn't clear if you asking a technical question or a social question. For the latter the usual problems are visibility and acknowledgement. Visibility means the client doesn't really know what is going on. Sure you can email a Word doc whenever it changes, but that is unsatisfying. If the client can go to a URL and see the live state of things, especially a prioritized list of outstanding work then they will have a far clearer picture of the current state, how it changes over time and the impact of their changes. Acknowledgement is how you deal with new requests. The client is being creative (in a good way) and have yet another idea of how to improve things. Saying "no" to them (it wasn't in the original requirements) is not something they want to hear. It is a good idea to always add new requests to the list as this acknowledges the client and makes them feel better. I always have a milestone/version/release called "Blue Sky" which is where most of these go. But if the client wants it elsewhere then they have to look at the list of outstanding requests and work out which ones get demoted. Be careful with the granularity of items in the list. Having one item be "Add LDAP" and another "Change title colour" when the former takes 4 weeks and the latter one hour may be apparent to you, but not to them. You can either break big ones down into pieces that are at most a few days, or change the title eg "Add LDAP (4 weeks)". Once you have visibility and acknowledgements it will become a lot clearer to both parties on the impact of change and what can be done about it (change priorities, spend more/less, reduce scope of items etc). And sometimes those Blue Sky items turn into gems.