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

Power Apps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as Power Apps Portal and shifted to the Power Apps side of the Microsoft product family. Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users. The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription." Pricing starts at $200/mo

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ 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 not require advan

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet: ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience. You can also use ScreenMeet with other CRM products or even on its own without a CRM. Here is a short video demo of ScreenMeet with Dynamics integration: ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appea