Requirement gathering is a process designed to capture different types of requirements to implement Dynamics 365 CE or for solving issues in the existing Dynamics 365 CE implementation. Requirement gathering is done by a Business Analyst (BA). Before requirement gathering, it is critical to identify stakeholders and key users. It is important to involve stakeholders and key users from the start of requirement gathering, to avoid any kind of confusion or misunderstanding.

Requirement gathering involves multiple activities such as open discussions, storyboards, building prototypes, and discussing different scenarios. These techniques can be different from one implementation to another. While using these techniques, we should always first understand the requirements clearly and confirm with the team before suggesting any solution to them. Based on the experience of the BA in a specific domain, some assumptions can be made related to customer requirements, but it is always recommended to discuss those assumptions with the relevant teams and gain their approval to avoid any confusion. You can see this process in the following diagram: 

Requirement gathering can be done using the following different techniques:

• Interview
• Questionnaire
• Workshops
• Brainstorming
• Prototype

Let's discuss these techniques one by one, in detail.