MOSS Requirements Gathering
I'm engaged in a project with a customer that requires MOSS to be installed for Internet and Intranet. Unfortunately the client does not know what he wants. Is there a systematic appraoch usually used to gather MOSS requirement such as a set of questions usually business analysts ask to clear the direction and to manage the scope. Is there a referenced material that can help? what do you usually do in such cases?

In addition, during the gathering phase, we used to show the clinet 3 options as an image prototype that shows the look & feel, once he confirmed on one, we ask the MOSS designer to reflect the PSD files on a MOSS site for showing as a demo. Do you use another approach?

Thanks for help
MOSS Requirements Gathering
===

I'm engaged in a project with a customer that requires MOSS to be installed for Internet and Intranet. Unfortunately the client does not know what he wants. Is there a systematic appraoch usually used to gather MOSS requirement such as a set of questions usually business analysts ask to clear the direction and to manage the scope. Is there a referenced material that can help? what do you usually do in such cases?

In addition, during the gathering phase, we used to show the clinet 3 options as an image prototype that shows the look & feel, once he confirmed on one, we ask the MOSS designer to reflect the PSD files on a MOSS site for showing as a demo. Do you use another approach?

Thanks for help