Fit Requirements into D365 Features, Not Features into Requirements

I would like to present my advance apologies if you disagree with me but give another thought about it. OK, let\’s start with the conclusion first and then we will discuss in detail.

Fit Requirements into D365 Features, Not Features into Requirements

For some time, I noticed that whenever Dynamics Product team release some new cool features into D365, we start talking about them and by all means we try to utilize these new features in our next implementation no matter whether requirements need these features or not. I\’m not saying don\’t use new features but here my point is to do proper Fit-Gap analysis and identify whether the new feature is needed in our next implementation or not. If requirements can easily be achieved by the features which are available from CRM 4.0/2011, then go ahead and design your system using those old features. There is no harm to use them, you don\’t need to impress someone who is sitting next to you. Take the accountability and trust your guts!

Example: Let me drag you into the Music industry and we will analyse through this example.

• Every day some new songs are coming, we start listening them dozens of times a week.
  • Why? because we love it at that moment, but it doesn\’t mean we will use this song for some special event or occasion.
• We still love to listen to the songs of 90\’s or older.
  • Why? because our mood wants to listen to them, even they are old but still we love it!

So, our mood and special event or occasion become our Requirements and Songs become our Features.

p.s. Ed Sheeran and Katy Perry are my recent favourites.