Before understanding the requirement gathering process, let's first understand what a requirement is. A requirement is basically a request from a customer or an end user. This request may be for adding new functionality in the system or to modify the existing functionality of the system. Different terminologies are used to refer to requirements such as user stories, use cases, features, and so on, based on the project management methodology used.

We need requirements in order to design, develop, and test a Dynamics 365 CE implementation or any product. There is no doubt about the fact that requirements set up a foundation on which a new system is implemented or built. If requirements are not correct, it increases the risk of a Dynamics 365 CE implementation failure.

Requirements can be divided into the following different categories:

• Business requirements
• Functional requirements
• Non-functional requirements

Let's discuss these different categories of requirements.