RE: Dynamics 365 Implementation Requirements Gathering
Hi,
It's dependent on your style implementation.
Assuming you have an understanding of D365 Implemention across various of it's modules/products and their integrations to existing system -
1. Typically, you can start with what is called as "discovery" wherein you understand what they have been using as their daily-driver for business and what systems are in place at the moment.
2. Next, you understand the "pain points" and translate those to Dynamics solutions for the same and how the users can streamline their processes and implementation
3. Next, based on the budget, you provide what all you can provide them in the implementation and how your "sprints" of implementation will be.
4. With regards to #3 above, you can then architect how the data from the old systems to the new ones will migrate.
5. Plan out the end-to-end implementation and how you will go-live with the client.
Typically, this is what most architects follow and can be said to be the standard way to undertaking a small to moderate-sized project.
But having said this, it's a subjective thing and differentiates largely based on how you work and what you provide to the client.
But then, what I mention is something you can see where it best suits your needs. Hope this helps!