My opinion is that the success of a project is not only in delivering the project as per the requirement of the customer. The real success of the project lies in the value we add for the customer via a particular project. When we ask the basic question of how we can add value to the customer, most of the answers will come to one (one among many) points, which is understanding what the customer want. Without mastering that, it will be tough for anyone to figure out what exactly is the problem the customer is facing and whether the customer’s understanding of the problem is correct. While navigating through many blogs related to requirement gathering and documentation for Dynamics 365 projects below posts felt like worth reading.
Its a combination of multiple posts that evolves from modeling the solution to the key questions we need to ask the customer while we are gathering the requirements. Sharing the reference to the original post to get the exact feel of what Dani meant.
- Model your dynamics 365 solution – Part 1
- Model your dynamics 365 Solution – Use Case Diagram Part 2
- Model your dynamics 365 Solution – Conceptual Diagram Part 3
- Elicit Dynamics 365 Requirements using Observation (Job Shadowing)
Another two posts related to dealing with the requirements are interesting as well.