Every requirement arrives wearing a disguise — someone has already turned a need into a feature and handed you the feature. The job of requirements engineering is to find the real need underneath. Here is how.
TAG ARCHIVE
the Handbook
You can’t design the To-Be until you’ve been honest about the As-Is
Designing the target architecture before you genuinely understand the current one is how programmes build something elegant that doesn’t fit. The As-Is is not a history lesson — it is the directive for everything that follows.
The nine pillars of a Power Platform architecture that survives production
There is no single design pattern for a good Power Platform solution. But there are nine principles that, applied consistently, separate an architecture that survives production from one that quietly falls apart after go-live.
Fit-gap analysis: the step most Dynamics 365 projects skip
Most Dynamics 365 programmes go from requirements straight into build. The step they skip — fit-gap analysis — is the one that decides whether you are configuring the platform or custom-building your way around it.