Skip to main content

Gap Analysis for Dynamics 365 (CRM) Implementations



Gap analysis explores the differences between your software requirements and the as-is features of an off-the-shelf product such as Microsoft Dynamics 365. It is one of the most useful techniques in a customer relationship management implementation.

Determining software requirements is a challenging process, and requires guidance and facilitation to help end user identify their needs and priorities.  If you start virtually with a blank sheet of paper, as is typical in custom software development, it is hard to know where to begin.  Users can easily go astray in coming up with software requirements.

Gap analysis starts with a working system, and focuses on the changes that are necessary to make the system meet the functional and performance goals of users.  For instance, here are some gaps that we explore in implementing a sales force management solution with Microsoft Dynamics 365:

  1. Look at the account form.  Analyze each field and determine whether you track this information.  Are there missing fields?  For each missing field, determine its attributes such as field type and whether it is required.   
  2. Review the opportunities view.  How many views do you need?  Are any of the off-the-shelf views unnecessary?  Is the order of the fields optimal for your users?  What is the best sort order for the records in the view. 
  3. Check for fields to hide and missing fields in the opportunity form.  Would users benefit from having more than one form, such as a quick overview which shows only a few fields. 
  4. How many business processes do you have for an opportunity?  Do you use different processes for different types of opportunities?  For each business process, describe the steps and which data elements are related to the workflow.
  5. Do you need notifications for changes to the data?  Who should be alerted when a new opportunity is created, or when an opportunity is closed as a win or a loss?
The process of gap analysis provides hands-on experience with the system to all users who participate, and is a precursor to formal training.  It helps users see quick, tangible improvement to their system and understand the implications of changes to the data model, business processes, views, forms and other objects that make up a software solution.


Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ by James Townsend Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do